Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-11087

mongod/mongos fatally asserts when rotating logs and log isn't in original location

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.4.6
    • Component/s: Admin, Logging, Security, Stability
    • Environment:
    • 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

            Assignee:
            backlog-server-security [DO NOT USE] Backlog - Security Team
            Reporter:
            hoffman@adobe.com Noah Hoffman
            Votes:
            6 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated: