[SERVER-15643] mongod aborts on log file rotation when log file is missing Created: 14/Oct/14 Updated: 30/Nov/14 Resolved: 30/Nov/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | 2.6.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Laurent Glayal | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: |
|
||||||||
| Participants: | |||||||||
| Description |
|
Hi, 2014-10-14T11:36:43.188+0200 [clientcursormon] connections:2 ***aborting after fassert() failure 2014-10-14T11:38:45.802+0200 [signalProcessingThread] SEVERE: Got signal: 6 (Aborted).
IMHO : even if original ile is missing the server should not terminate. Previously I used mongo 2.4.6 from centos repositories with logrotate and had no trouble, I switched to mongo 2.6.4 from mongodb repositories and reused previous logrotate configuration, ad now my servers are crashing at log rotation. Regards. |
| Comments |
| Comment by Ramon Fernandez Marina [ 30/Nov/14 ] |
|
lglayal, this issue was reported before in SERVER-11087, so I'm marking this ticket as a duplicate. Please feel free to watch and vote for SERVER-11087. You may also be interested in Regards, |
| Comment by Laurent Glayal [ 14/Oct/14 ] |
|
Would it be possible to replace case SIGUSR1: with something like case SIGUSR1: else { checkAnMayBeReopenLogFile(); logWarningOnLogrotate("Unable to rotate initial log file"); }break; |