[SERVER-8698] Invalid access at address: 0 from thread "command: { serverStatus: 1 }" Got signal: 7 (Bus error). Created: 25/Feb/13 Updated: 19/Mar/13 Resolved: 12/Mar/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 2.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | nosqldb | Assignee: | Andre de Frere |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
centos 6.2 final ,kernel 2.6.32 |
||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
... ntoreturn:1 keyUpdates:0 locks(micros) r:38 reslen:2633 601ms Mon Feb 25 03:37:46 Invalid access at address: 0 from thread: conn25391 Mon Feb 25 03:37:46 Backtrace: |
| Comments |
| Comment by Andre de Frere [ 12/Mar/13 ] |
|
Hi, I'm closing this ticket for now, as it appears it may be caused by something else. Please do not hesitate to reopen the case if there is anything further, or if you have a way of reproducing the issue. |
| Comment by nosqldb [ 11/Mar/13 ] |
|
dmesg is normal.I think it's an accidental case instead of a bug.Thanks. |
| Comment by Andre de Frere [ 07/Mar/13 ] |
|
One of the common causes for a Signal 7 (Bus Error) is IO problems or corruption on the filesystem. Could you check your dmesg output and ensure there are no filesystem or IO problems detected? Can you fsck the volume that the dbpath is on? |
| Comment by nosqldb [ 28/Feb/13 ] |
|
I attached the log,but it's hard to reproduce the problem.Thank you. |
| Comment by James Wahlin [ 27/Feb/13 ] |
|
Can you provide:
Also, our latest stable release of MongoDB 2.2 is 2.2.3. I would recommend upgrading to take advantage of bug fixes and improvements made. |