Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
2.6.4
-
None
-
*nix
-
ALL
-
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
|