[SERVER-9607] One of our secondaries crashed Created: 07/May/13 Updated: 10/Dec/14 Resolved: 15/May/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 2.2.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jerry Hoffmeister | Assignee: | Unassigned |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | Linux |
| Participants: |
| Description |
|
One of our secondaries crashed on Saturday and here's the log from the event: Sat May 4 23:35:04 [initandlisten] connection accepted from 10.50.233.182:53504 #1002184 (39 connections now open) ntoreturn:1 keyUpdates:0 reslen:44 300000ms ntoreturn:1 keyUpdates:0 reslen:44 300000ms Sat May 4 23:35:42 Got signal: 7 (Bus error). Sat May 4 23:35:43 Backtrace: |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 15/May/13 ] |
|
That indeed looks like a hardware issue. If anything else comes up, please let us know. |
| Comment by Jerry Hoffmeister [ 13/May/13 ] |
|
looks like this is a hardware issue... happened again and from the syslog: 200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 >/dev/null; fi) |
| Comment by Jerry Hoffmeister [ 07/May/13 ] |
|
I should also add that I've restarted mongod and it appears to be re-syncing just fine. |