[SERVER-15520] Logging with --syslog results in less accuracy due to lack of mongodb timestamp Created: 03/Oct/14  Updated: 19/May/15  Resolved: 15/Jan/15

Status: Closed
Project: Core Server
Component/s: Logging
Affects Version/s: 2.6.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: James O'Leary Assignee: Matt Kangas
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

*nix


Issue Links:
Depends
Related
Operating System: ALL
Steps To Reproduce:

run mongod --syslog

Participants:

 Description   

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



 Comments   
Comment by Matt Kangas [ 15/Jan/15 ]

When logging with --syslog, the timestamp is created by the syslog daemon. mongod cannot configure it.

We are not going to add an separate timestamp generated by mongod to syslog output.

Generated at Thu Feb 08 03:38:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.