[SERVER-12849] mongod got signal 7 (Bus error) Created: 23/Feb/14 Updated: 10/Dec/14 Resolved: 07/Apr/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.4.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Taha Jahangir | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Participants: |
| Description |
|
One of our mongod servers suddenly existed with this backtrace:
|
| Comments |
| Comment by Thomas Rueckstiess [ 07/Apr/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Taha, I noticed this ticket is still unresolved and we haven't heard back from you for a while. As we don't have enough information to continue the diagnosis, we have to assume that the hard drive failure is the source of the problem. You would have to fix the hardware issue and resync the node from a healthy source. I'll go ahead and close this ticket now. If you would like to follow up feel free to re-open it and provide additional information. Thanks, | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Stennie Steneker (Inactive) [ 17/Mar/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi Taha, Were you able to run fsck on all the drives? Can you confirm the current status of this issue? It would also be helpful to run smartctl (part of smartmontools) to check for SMART hardware errors:
Thanks, | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Eliot Horowitz (Inactive) [ 10/Mar/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
Can you run an fsck on all the drives? | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Taha Jahangir [ 24/Feb/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
The root mongo data directory (journal + lock file) is on sda, and db directories (`local` db and our db) is on sdb (`directoryperdb` is enabled) | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Eliot Horowitz (Inactive) [ 24/Feb/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
Is sdb where the mongo data lives? | ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Taha Jahangir [ 24/Feb/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
What you mean from history? This is a dedicated server runs a mongod instance. logs in /var/log/messages:
mongo log does not contain anything more related to this errror, the four lines before the error is:
| ||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Eliot Horowitz (Inactive) [ 24/Feb/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||
|
Hi, What's the history of this machine? Can you check /var/log/messages for any i/o errors? Can you send the full mongod log? |