[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: File SRDM2.2020-06-09T09-10-46.mdmp     Zip Archive diagnostic.data.zip     Zip Archive log.zip    
Participants:

 Description   

Dear Team,

We are using MongoDB as standalone server.

  1. OS: Windows 7, architecture: "x64", 
  2. Platform: "Java/AdoptOpenJDK/11.0.6"
  3. mongodb Journals are enabled by default
  4. Mongod server version: db version v3.6.17

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.

log.zip diagnostic.data.zip

SRDM2.2020-06-09T09-10-46.mdmp

log.zip

Thank you.

Regards,

Ram



 Comments   
Comment by Carl Champain (Inactive) [ 15/Jun/20 ]

Hi ram.pamudurthi@gmail.com,

MongoDB couldn't shutdown cleanly because of the PC shutdown.
That said, the SERVER project is for bugs and feature suggestions for the MongoDB server. As this ticket does not appear to be a bug, I will now close it. If you need further assistance troubleshooting, I encourage you to ask our community by posting on the MongoDB Community Forums or on Stack Overflow with the mongodb tag.

Kind regards,

Carl

 

Generated at Thu Feb 08 05:17:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.