[SERVER-16463] From unknown reason, server reported Got signal: 7 (Bus error). Created: 08/Dec/14 Updated: 22/Jan/15 Resolved: 22/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 2.4.11 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jakub ?erny | Assignee: | Ramon Fernandez Marina |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
Mon Dec 8 18:00:08.241 [rsHealthPoll] replset info ec2-54-74-234-239.eu-west-1.compute.amazonaws.com:27017 heartbeat failed, retrying Mon Dec 8 18:00:09.954 Got signal: 7 (Bus error). Mon Dec 8 18:00:10.166 Backtrace: |
| Comments |
| Comment by Ramon Fernandez Marina [ 22/Jan/15 ] |
|
kuba@persoo.cz, we haven't heard back from you for a while so we're closing this ticket. If this is still an issue for you please re-open it and provide the additional information requested above. Thanks, |
| Comment by Ramon Fernandez Marina [ 09/Dec/14 ] |
|
kuba@persoo.cz, can you upload the full logs of the failing server? The system logs from around that time should help confirm/reject my hypothesis: the system did try to re-start mongod, but since the previous instance crashed without removing the mongod.lock file the restart failed a few times, and then upstart gave up (we should see a "respawning too fast" or similar message in the system logs). |
| Comment by Jakub ?erny [ 09/Dec/14 ] |
|
Aha, you were right. [ 20.104384] init: plymouth-upstart-bridge main process ended, respawning How is it with upstrart script in *.deb package? Why it does not have respawn? I.e. it do not start again after having fatal error? |
| Comment by Ramon Fernandez Marina [ 09/Dec/14 ] |
|
kuba@persoo.cz, a "Got signal: 7 (Bus error)... Invalid access at address" message can appear when there is I/O problems or filesystem corruption. Could you please check you dmesg output for I/O errors on your drives? Have you run an fsck on the volume that the dbpath is on? |