-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.4.6
-
Environment:Running mongo 2.4.6 across the deployment
Shard Nodes (mongod):
Based on base AMI: amzn-ami-minimal-pv-2013.03.0.x86_64-ebs (ami-febe2ace)
Amazon Linux AMI x86_64 EBS
Instance Type: m2.4xlarge
Linux version 3.4.37-40.44.amzn1.x86_64 (mockbuild@gobi-build-31005) (gcc version 4.6.3 20120306 (Red Hat 4.6.3-2) (GCC) ) #1 SMP Thu Mar 21 01:17:08 UTC 2013
Config Nodes:
Same AMI and Linux info as Shard nodes
Instance Type: m1.large
App Nodes (mongos):
Linux version 2.6.21.7-2.fc8xen (mockbuild@xenbuilder4.fedora.phx.redhat.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Fri Feb 15 12:34:28 EST 2008
Instance Type: m1.large
Running mongo 2.4.6 across the deployment Shard Nodes (mongod): Based on base AMI: amzn-ami-minimal-pv-2013.03.0.x86_64-ebs (ami-febe2ace) Amazon Linux AMI x86_64 EBS Instance Type: m2.4xlarge Linux version 3.4.37-40.44.amzn1.x86_64 ( mockbuild@gobi-build-31005 ) (gcc version 4.6.3 20120306 (Red Hat 4.6.3-2) (GCC) ) #1 SMP Thu Mar 21 01:17:08 UTC 2013 Config Nodes: Same AMI and Linux info as Shard nodes Instance Type: m1.large App Nodes (mongos): Linux version 2.6.21.7-2.fc8xen ( mockbuild@xenbuilder4.fedora.phx.redhat.com ) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-33)) #1 SMP Fri Feb 15 12:34:28 EST 2008 Instance Type: m1.large
-
Server Security
-
Security 2020-04-20, Security 2020-05-04, Security 2020-06-01, Security 2020-06-15, Security 2020-07-27, Security 2021-01-11, Security 2021-02-22, Security 2021-03-08, Security 2021-03-22, Security 2021-04-05
While implementing a log rotate script we found that if the script would move the mongo*.log file to a new location BEFORE sending the SIGUSER signal to the daemon triggering the daemon's own rotate functionality, a fatal assertion is thrown
Stack Trace:
Tue Oct 8 07:00:56.966 [Balancer] distributed lock 'balancer/ip-10-0-0-91:27017:1381230304:1804289383' unlocked.
Tue Oct 8 07:01:01.357 ERROR: failed to rename '/var/log/mongo/mongos.log' to '/var/log/mongo/mongos.log.2013-10-08T14-01-01': errno:2 N
o such file or directory
Tue Oct 8 07:01:01.371 Fatal Assertion 16780
0xa897d1 0xa4daf3 0x65ace5 0xad14c9 0x2aaaaacce617 0x2aaaab951c2d
/usr/bin/mongos(_ZN5mongo15printStackTraceERSo+0x21) [0xa897d1]
/usr/bin/mongos(_ZN5mongo13fassertFailedEi+0xa3) [0xa4daf3]
/usr/bin/mongos(_ZN5mongo22signalProcessingThreadEv+0x55) [0x65ace5]
/usr/bin/mongos [0xad14c9]
/lib64/libpthread.so.0 [0x2aaaaacce617]
/lib64/libc.so.6(clone+0x6d) [0x2aaaab951c2d]
Tue Oct 8 07:01:01.373
- is duplicated by
-
SERVER-11438 server aborts if original log file is moved before rotating log
- Closed
-
SERVER-11719 Mongos crash when log rotating
- Closed
-
SERVER-15643 mongod aborts on log file rotation when log file is missing
- Closed
-
SERVER-27247 mongod crash after SIGUSR1 signal, if not finds mongod.log
- Closed
-
SERVER-34161 mongod crashes after renaming logfile and sending -SIGUSR1 to reopen
- Closed
- is related to
-
SERVER-4905 logRotate should conform to standard log rotation mechanisms
- Closed