[SERVER-11158] Crash on startup Created: 12/Oct/13 Updated: 11/Jul/16 Resolved: 04/Nov/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 2.4.4 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Dwayne Bull | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Ubuntu |
||
| Operating System: | ALL |
| Steps To Reproduce: | run |
| Participants: |
| Description |
|
New server build from an image of a working server. Attempted on several new servers with the same result. Only happens on mongod, mongos starts fine. /usr/bin/mongod -vvvvvvvvvvvv Sat Oct 12 15:33:41.507 Matcher::matches() { abcd: 3.1, abcdef: "123456789" }Sat Oct 12 15:33:41.507 Matcher::matches() { abcd: 3.1, abcdef: "123456789" }Sat Oct 12 15:33:41.507 Matcher::matches() { abcdef: "z23456789" }Sat Oct 12 15:33:41.507 Matcher::matches() { abcd: 3.1, abcdef: "123456789" }Sat Oct 12 15:33:41.507 Matcher::matches() { abcdef: "z23456789" }Sat Oct 12 15:33:41.506 BackgroundJob starting: DataFileSync Sat Oct 12 15:33:41.513 Got signal: 4 (Illegal instruction). Sat Oct 12 15:33:41.517 Backtrace: |
| Comments |
| Comment by Dwayne Bull [ 14/Oct/13 ] |
|
I have had info back from rackspace as its a concern about the hypervisors: "We have different hosts hardware and 2 different versions of hypervisors xensever 6.0 and xenserver 6.1. but when you build a vm it is choosen randomly for the best available on our system, we dont have specific servers for different flavors." Edit: We have confirmed that xenserver 6.1 is the issue, updates to the core Ubuntu packages fix the error. |
| Comment by Dwayne Bull [ 13/Oct/13 ] |
|
I've taken more images from working servers and I'm still getting this issue. Edit: After apt-get update & upgrade everything works fine, although I don't see what needs to be updated given the image is from a working server and just updating mongodb doesn't work. |
| Comment by Dwayne Bull [ 13/Oct/13 ] |
|
Turns out the processor isn't the issue, I just booted up a few servers till I hit on one with a AMD Opteron(tm) Processor 4332 HE. |
| Comment by Dwayne Bull [ 12/Oct/13 ] |
|
Md5 matched. root@nginx-dev-colonyattack:/var/mon/mongodb-linux-x86_64-2.4.6/bin# mongod -vvvvvvvvvv Sat Oct 12 20:12:16.418 Matcher::matches() { abcd: 3.1, abcdef: "123456789" }Sat Oct 12 20:12:16.418 Matcher::matches() { abcd: 3.1, abcdef: "123456789" }Sat Oct 12 20:12:16.418 Matcher::matches() { abcdef: "z23456789" }Sat Oct 12 20:12:16.418 Matcher::matches() { abcd: 3.1, abcdef: "123456789" }Sat Oct 12 20:12:16.418 Matcher::matches() { abcdef: "z23456789" }Sat Oct 12 20:12:16.425 Invalid operation at address: 0x7f0932695021 from thread: Sat Oct 12 20:12:16.425 Got signal: 4 (Illegal instruction). Sat Oct 12 20:12:16.429 Backtrace: |
| Comment by Eliot Horowitz (Inactive) [ 12/Oct/13 ] |
|
Can you try http://fastdl.mongodb.org/linux/mongodb-linux-x86_64-2.4.6.tgz |
| Comment by Dwayne Bull [ 12/Oct/13 ] |
|
It's version 2.4.4 from the ubuntu repo. I've tried with the latest version too but that had the same result. |
| Comment by Eliot Horowitz (Inactive) [ 12/Oct/13 ] |
|
Is this an official binary? The next thing to try would be compiling on that machine and seeing if it works. |
| Comment by Dwayne Bull [ 12/Oct/13 ] |
|
Here are the differences in the cpu flags ( removed common flags between working and not ) Not working servers have these flags: Working servers have these flags: I really don't know if this is anything to do with the issue, but if it helps.. |
| Comment by Dwayne Bull [ 12/Oct/13 ] |
|
If it helps I ran a few more cloud servers, here are the results: Working 30g server Not working 2g & 0.5g server Working 2g server |