[SERVER-8604] replica set member down, Got signal: 7 (Bus error). Created: 18/Feb/13 Updated: 03/Feb/16 Resolved: 13/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Performance |
| Affects Version/s: | 2.2.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | michael cao | Assignee: | Andre de Frere |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux is13084905-0050 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux |
||
| Operating System: | ALL |
| Participants: |
| Description |
|
Mon Feb 4 14:47:04 [conn26] Setting temporary authorization to: { local: { __system: 2 } } } } } } ntoreturn:1 keyUpdates:0 reslen:155 0ms Mon Feb 4 14:47:05 Got signal: 7 (Bus error). Mon Feb 4 14:47:05 [conn3] runQuery called admin.$cmd { ismaster: 1 }Mon Feb 4 14:47:05 [conn3] run command admin.$cmd { ismaster: 1 }Mon Feb 4 14:47:05 [conn3] command admin.$cmd command: { ismaster: 1 } ntoreturn:1 keyUpdates:0 reslen:283 0ms to 192.168.161.134:27010 with $auth: { local: { __system: 2 } } to 192.168.161.134:27011 with $auth: { local: { __system: 2 } } } } } } } } } } } ntoreturn:1 keyUpdates:0 reslen:155 0ms |
| Comments |
| Comment by Ramon Fernandez Marina [ 03/Feb/16 ] |
|
vionemc, please note that MongoDB 2.2 is no longer supported. If you're having issues with a recent version of MongoDB please open a new ticket. Thanks, |
| Comment by Aminah Nuraini [ 19/Jan/16 ] |
|
Currently, there is an unofficial recovery method written in this article https://www.compose.io/articles/shipwrecked-a-mongodb-data-recovery-tale/ This is the script https://github.com/MongoHQ/purplebeard Can you please make the official one? |
| Comment by Aminah Nuraini [ 19/Jan/16 ] |
|
I also got this error. It was caused by hardware failure. There is a huge probability it will be hard to recover the data. |
| Comment by Andre de Frere [ 13/Mar/13 ] |
|
Hi, I'm setting this ticket to resolved as we have not heard back from you in a while. Please do not hesitate to reopen the case if you have anything further to share, or if you would like to discuss this ticket further. Regards, |
| Comment by Andre de Frere [ 03/Mar/13 ] |
|
Hi, Just checking in with you on this issue. Have you had a chance to check the filesystem for corruption, or have you found any related errors in dmesg or system logs? |
| Comment by Andre de Frere [ 20/Feb/13 ] |
|
A "Got signal: 7 (Bus error)." message can appear (along with the "Invalid access at address" message) when there is IO problems or filesystem corruption. Could you please check you dmesg output for errors, especially to do with IO. Have you run an fsck on the volume that the dbpath is on? |