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

Logging with --syslog results in less accuracy due to lack of mongodb timestamp

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 2.6.4
    • Component/s: Logging
    • Labels:
      None
    • Environment:
      *nix
    • ALL
    • Hide

      run mongod --syslog

      Show
      run mongod --syslog

      MongoDb 2.6.0 - 2.6.4 logging seems to have removed the timestamp from the syslog message.

      As a result the default syslog using RFC3339 loses granularity on time stamps :

      MongoDB 2.4.10
      Oct  3 15:10:32 jimoleary.local mongod.27017[56077]: Fri Oct  3 15:10:32.309 [initandlisten] ERROR: listen(): bind() failed errno:48 Address already in use for socket: 0.0.0.0:27017
Oct  3 15:10:32 jimoleary.local mongod.27017[56077]: Fri Oct  3 15:10:32.309 [websvr] ERROR: listen(): bind() failed errno:48 Address already in use for socket: 0.0.0.0:28017
Oct  3 15:10:32 jimoleary.local mongod.27017[56077]: Fri Oct  3 15:10:32.310 [websvr] ERROR:   addr already in use
Oct  3 15:10:32 jimoleary.local mongod.27017[56077]: Fri Oct  3 15:10:32.310 [initandlisten] ERROR:   addr already in use
      MongoDB 2.6.0
      Oct  3 15:12:50 jimoleary.local mongod.27017[56182]: [initandlisten] listen(): bind() failed errno:48 Address already in use for socket: 0.0.0.0:27017
Oct  3 15:12:50 jimoleary.local mongod.27017[56182]: [initandlisten]   addr already in use

            Assignee:
            matt.kangas Matt Kangas
            Reporter:
            jim.oleary@mongodb.com James O'Leary
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: