[SERVER-48686] MongoDB service has terminated due to an unexpected reason Created: 10/Jun/20 Updated: 15/Jun/20 Resolved: 15/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.6.17 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | mohan mohan | Assignee: | Carl Champain (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
Dear Team, We are using MongoDB as standalone server.
We have started MongoDB Server as windows service which is embedded in our application. For some reasons we had PC shutdown and then restated the PC again. After the PC restart MongoDB service should be started along with windows services. But the MongoDB service could not start aging. We observed that the log message "Detected unclean shutdown " in MongoDB logs. We would like to know the root cause for this issue. Please find the attached log files. SRDM2.2020-06-09T09-10-46.mdmp Thank you. Regards, Ram |
| Comments |
| Comment by Carl Champain (Inactive) [ 15/Jun/20 ] |
|
MongoDB couldn't shutdown cleanly because of the PC shutdown. Kind regards, Carl
|