[SERVER-33416] Mongod service keeps restarting and now it crashes without logging why Created: 21/Feb/18 Updated: 23/Apr/18 Resolved: 18/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Logging |
| Affects Version/s: | 3.6.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Robin [X] | Assignee: | Dmitry Agranat |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||
| Steps To Reproduce: | After 10 minutes the Windows Service crashes. I use the following MongoDB.conf:
|
||||||||||||||||||||||||
| Participants: |
| Description |
|
I'm running Mongod as a Windows service. But it logs that it keeps restarting.
|
| Comments |
| Comment by Dmitry Agranat [ 18/Mar/18 ] | ||
|
Hi StuiterSlurf, We haven’t heard back from you for some time, so I’m going to mark this ticket as resolved. If this is still an issue for you, please provide additional information and we will reopen the ticket. Regards, | ||
| Comment by Kelsey Schubert [ 09/Mar/18 ] | ||
|
Hi StuiterSlurf, We still need additional information to diagnose the problem. If this is still an issue for you, would you please upload the files Dima requested to the portal I created? Thank you, | ||
| Comment by Kelsey Schubert [ 01/Mar/18 ] | ||
|
Hi StuiterSlurf, I've created an upload portal which has a much higher file size limit for your convenience going forward. Thanks, | ||
| Comment by Robin [X] [ 28/Feb/18 ] | ||
|
Dear Dima, There where to many files that I could upload. That's why they are all here one by one. But I will upload the logs tomorrow. The system has indeed 4 gb of RAM. But I can limit MongoDB to 1gb according to the specs. If it needs more memory it should not crash? Or am I seeing it wrong. Also the logging just quits at that time it crashes. But with what program are you reading those diagnostic files? | ||
| Comment by Dmitry Agranat [ 28/Feb/18 ] | ||
|
Hi StuiterSlurf, Thank you for providing the requesting information. The diagnostic.data does indicate that there is a memory pressure on your 4GB RAM server. From the log I've noticed:
Can you use the SetSystemFileCacheSize to limit the amount of memory that the file system cache can use and report back if this improves the situation? If the issue reoccurs after limiting the file system cache please provide:
In the meantime:
Thanks, | ||
| Comment by Robin [X] [ 27/Feb/18 ] | ||
|
Do you got an estimate when you can get back to me on this Kelsey? | ||
| Comment by Ramon Fernandez Marina [ 21/Feb/18 ] | ||
|
StuiterSlurf, when a ***** SERVER RESTARTED ***** line appears suddenly in the logs it's an indication that the operating system killed the mongod process abruptly, often because it was consuming too much memory. This by itself is not an indication of a bug in the server, but we'll be able to know for sure if you can upload the contents of the diagnostic.data directory from your dbpath. Chances are you need a machine with more memory. Regards, | ||
| Comment by Robin [X] [ 21/Feb/18 ] | ||
|
This is also for the 3.4 versions. |