[SERVER-9578] mongos dies on SIGUSR1 instead of rotating logs Created: 03/May/13  Updated: 11/Jul/16  Resolved: 06/May/13

Status: Closed
Project: Core Server
Component/s: Logging, Sharding
Affects Version/s: 2.4.3
Fix Version/s: 2.2.5, 2.4.4, 2.5.0

Type: Bug Priority: Major - P3
Reporter: Michael Grundy Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: logrotate, mongos
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Linux, osx


Issue Links:
Depends
Related
related to SERVER-4739 Race condition in log rotation (was: ... Closed
Operating System: ALL
Steps To Reproduce:

Start up a sharded environment.
Start mongos, use --logpath or --syslog option
ps aux | grep mongos # mongos is running
killall -SIGUSR1 mongos
ps aux | grep mongos # mongos is no longer there

Participants:

 Description   

mongos will die on receiving a SIGUSR1 instead of rotating its log or, in the case where --syslog was specified, printing the message "LoggingManager not enabled"



 Comments   
Comment by auto [ 10/May/13 ]

Author:

{u'date': u'2013-05-06T18:33:17Z', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-9578 install mongos signal handler for SIGUSR1 before spawning any threads

Conflicts:
src/mongo/s/server.cpp
Branch: v2.2
https://github.com/mongodb/mongo/commit/ae626614e5ee0de1724fbeaf07c862d6e566d745

Comment by auto [ 08/May/13 ]

Author:

{u'date': u'2013-05-06T18:33:17Z', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-9578 install mongos signal handler for SIGUSR1 before spawning any threads
Branch: v2.4
https://github.com/mongodb/mongo/commit/84d9196c884edc26f49524c180aa05a6688852b2

Comment by auto [ 06/May/13 ]

Author:

{u'date': u'2013-05-06T18:33:17Z', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-9578 install mongos signal handler for SIGUSR1 before spawning any threads
Branch: master
https://github.com/mongodb/mongo/commit/40faa8d4027af5ccee00705eb2ac6b92bb44f182

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