Syslog adds extra timestamp, sends to incorrect loglevel, should add process PID and log to console in case of errors in sending

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.5.1
    • Affects Version/s: 2.2.0-rc0
    • Component/s: Logging
    • None
    • Fully Compatible
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Starting mongod with --syslog generates the following.

      Aug 3 13:14:55 grapevine mongod.27017: Fri Aug 3 13:14:55 [initandlisten] recover : no journal files present, no recovery needed
      Aug 3 13:14:55 grapevine mongod.27017: Fri Aug 3 13:14:55 [initandlisten] waiting for connections on port 27017
      Aug 3 13:14:55 grapevine mongod.27017: Fri Aug 3 13:14:55 [websvr] admin web console waiting for connections on port 28017

      • prepending timestamp should be disabled if mongod is started with --syslog
      • LL_SEVERE should probably map to LOG_EMERG instead of LOG_CRIT ..???
      • should log process PID and should log to console if logging to syslogd fails

              Assignee:
              Andy Schwerin
              Reporter:
              Akshay Kumar
              Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: