[SERVER-35373] Regarding MongoDB Service logs Created: 04/Jun/18 Updated: 28/Jun/18 Resolved: 06/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | 3.4.0 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Sandeep [X] | Assignee: | Ramon Fernandez Marina |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Dear Team, One of our Customer has reported an issue that "MongoDB Service is stopped ". But We are unable to trace shutdown event like (SERVICE_CONTROL_STOP) from mongodb logs .[\data\log] Hence possibly we suspect that the mongoDB process might have been either killed or crashed Hence would like to know any option by which we can identify the reason for mongodb service shutdown like log of the stack trace, to locate the event trace for MONGODB[shutdown/kill/terminated ] service. Environment Details:
Thanks & Regards Sandeep KS |
| Comments |
| Comment by Ramon Fernandez Marina [ 06/Jun/18 ] | |||
|
Thanks for your report. A clean shutdown will have lines like the one below; if you don't see the last line before the SERVER RESTARTED marker then it is likely that mongod crashed or was killed by the OS.
Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources. Regards, | |||
| Comment by Sandeep [X] [ 06/Jun/18 ] | |||
|
Dear Team, May I request MongoDB Team to provide us an update for the above said Issue please...? Thanks & Regards Sandeep KS |