[SERVER-68963] immediate exit due to unhandled exception Created: 18/Aug/22  Updated: 20/Sep/22  Resolved: 20/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 5.0.7
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: David Weiler-Thiessen Assignee: Yuan Fang
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive Suncor-20220815.zip    
Issue Links:
Related
related to SERVER-61680 *** immediate exit due to unhandled e... Closed
related to SERVER-69473 immediate exit due to unhandled excep... Closed
related to SERVER-54786 How to avoid this error “terminate() ... Closed
Operating System: ALL
Participants:

 Description   

Had a recent crash of MongoDB and logs contain message: immediate exit due to unhandled exception.

 

Have attached a zip with the log containing error message, and the mdmp file created.



 Comments   
Comment by Yuan Fang [ 20/Sep/22 ]

Hi weiler-thiessen.david@spartancontrols.com ,

We haven’t heard back from you for some time, so I’m going to close this ticket. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Regards,

Yuan

Comment by Yuan Fang [ 29/Aug/22 ]

Hi weiler-thiessen.david@spartancontrols.com,

Thank you for providing the backtrace records. This backtrace looks similar to what we see in SERVER-54786, which could be caused by the mongod missing the necessary permissions to rename files in its dbpath. Can you help us confirm this problem by archiving (tar or zip) the complete mongod.log files generated for the crash and uploading them to the support uploader location?

Files uploaded to this portal are visible only to MongoDB employees and are routinely deleted after some time.

Thanks,

Yuan

Generated at Thu Feb 08 06:12:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.