[SERVER-36365] MongoDB 4.0 Crashed Multiple Times During Insert Operations Created: 30/Jul/18 Updated: 04/Nov/18 Resolved: 01/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | WiredTiger |
| Affects Version/s: | 4.0.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kelvin Lu | Assignee: | Nick Brewer |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
|||
| Operating System: | ALL | |||
| Steps To Reproduce: |
|
|||
| Participants: |
| Description |
|
Hello Team, I am testing MongoDB 4.0 on my local Ubuntu 18.04.1 and mongoDB crashed when I insert document with following error. Log file attached
|
| Comments |
| Comment by Nick Brewer [ 01/Oct/18 ] | ||||||||||||||||||||||||||
|
kelvinl Since there's been no activity on this ticket in some time, I'm going to close it. Feel free to update this ticket with the requested information, and we'll reopen it for you. Thanks, | ||||||||||||||||||||||||||
| Comment by Nick Brewer [ 20/Aug/18 ] | ||||||||||||||||||||||||||
|
kelvinl Could provide the following information, if possible:
If you'd prefer to keep any of this information private, we can generate a secure upload portal for you. One other thing I would note: as I mentioned previously, mongod needs to be able to perform fsync on directories - I would be curious to know if you can recreate this behavior when not using a shared drive for your dbpath | ||||||||||||||||||||||||||
| Comment by Kelvin Lu [ 20/Aug/18 ] | ||||||||||||||||||||||||||
|
Nick, I was out for vacation and did not reply your comment. I re-installed MongoDB with most recent version 4.01 and reload data. I do not see that bug again. However, I experienced following error from time to time with
| ||||||||||||||||||||||||||
| Comment by Nick Brewer [ 20/Aug/18 ] | ||||||||||||||||||||||||||
|
kelvinl Since we haven't heard back from you, I'm going to close this issue for now. One thing I'll note is that it's possible you were running into an fsync issue due to the use of the shared Virtualbox drive. -Nick | ||||||||||||||||||||||||||
| Comment by Nick Brewer [ 01/Aug/18 ] | ||||||||||||||||||||||||||
|
kelvinl Thanks for the info. We'll await your results. -Nick | ||||||||||||||||||||||||||
| Comment by Kelvin Lu [ 31/Jul/18 ] | ||||||||||||||||||||||||||
|
I use Ubuntu 18.04 on Oracle Virtual Box and dbpath point to /mnt is just another mount point from different logic drive file.
I will use your latest binary to build a new mongoDB 4.0 Server with Ubuntu 18.04 and start over again and will let you know if I run to any issues later
| ||||||||||||||||||||||||||
| Comment by Nick Brewer [ 31/Jul/18 ] | ||||||||||||||||||||||||||
|
kelvinl Sorry, this is the correct set of binaries to use for your testing. From your log, I noticed that the dbpath is pointing to a directory with /mnt - is this an external device? And if so, what kind? It would be helpful to get the device's corresponding entry in /etc/fstab, if it has one. Thanks, | ||||||||||||||||||||||||||
| Comment by Nick Brewer [ 31/Jul/18 ] | ||||||||||||||||||||||||||
|
kelvinl MongoDB 4.0.0 is not officially supported on Ubuntu 18.04 - were you using a binary for an older release? An 18.04 binary is available for our current development release, which you can find here. Could you try recreating this on the latest version? Note that you'll need to test on a new database (starting over from a clean dbpath). Thanks, |