[SERVER-71274] mongod process crash with fatal error Created: 11/Nov/22 Updated: 09/Feb/23 Resolved: 22/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Hidemi Ta | Assignee: | Erwin Pe |
| Resolution: | Done | Votes: | 0 |
| Labels: | ftdc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Security 2022-11-28 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
mongod process crash every several hour following message ~ {"t":\{"$date":"2022-05-24T20:10:58.013+09:00"},"s":"F", "c":"CONTROL", "id":4757800, "ctx":"ftdc","msg":"Writing fatal message","attr":{"message":"terminate() called. An exception is active; attempting to gather more information"}} {"t": {"$date":"2022-05-24T20:10:58.013+09:00"},"s":"F", "c":"CONTROL", "id":4757800, "ctx":"ftdc","msg":"Writing fatal message","attr":{"message":"DBException::toString(): FileRenameFailed: \ufffdv\ufffd\ufffd\ufffdZ\ufffdX\ufffd̓t\ufffd@\ufffdC\ufffd\ufffd\ufffdɃA\ufffdN\ufffdZ\ufffdX\ufffdł\ufffd\ufffd܂\ufffd\ufffd\ufffd\ufffdB\ufffdʂ̃v\ufffd\ufffd\ufffdZ\ufffdX\ufffd\ufffd\ufffdg\ufffdp\ufffd\ufffd\ufffdł\ufffd\ufffdB\nActual exception type: class mongo::error_details::ExceptionForImpl<37,class mongo::AssertionException>\n"}}~
This issue probably comming from following ec.message() returns non utf-8 character.
"\ufffd" is unicode replacement character for unknown or unrepresentable in Unicode.
~https://stackoverflow.com/questions/18489893/what-is-the-encoding-used-by-boost-asio-error-messages~ |
| Comments |
| Comment by Jatin Tanwar [ 09/Feb/23 ] |
|
how can i get the solution of mongod command error or crasehes when ever i executing mongod command ?
|
| Comment by Erwin Pe [ 22/Nov/22 ] |
|
Since the process crash does not appear to be caused by a bug, I will now close this ticket. |
| Comment by Erwin Pe [ 18/Nov/22 ] |
|
The issue with the error message is indeed due to the system's locale being set to a code page that is not compatible with UTF-8, and hence the presence of replacement characters in the log output. As a workaround, you can temporarily set the locale or the system language to English, or enable the "Use Unicode UTF-8 for worldwide language support" setting, to get a readable error message. The cause of the process crash itself is likely due to permissions error when renaming the metrics.interim.temp file to metrics.interim. Please make sure that no other processes are reading or writing the metrics.interim file. |
| Comment by Chris Kelly [ 11/Nov/22 ] |
|
Just adding that there has been further discussion of this on the community forums here: https://www.mongodb.com/community/forums/t/mongo-process-crashed-every-few-days-on-windows/129625 I agree that this looks like it may be an issue. Thanks for putting up the SERVER ticket, x22t33c81@gmail.com! I'll pass this on to the relevant team to take a look. |
| Comment by Hidemi Ta [ 11/Nov/22 ] |
|
Sorry, lack of information OS: Windows10 Version: MongoDB 5.0.3.0 |