[SERVER-3825] Segmentation fault on CentOS 5.6 Created: 13/Sep/11 Updated: 30/Mar/12 Resolved: 13/Sep/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Stability |
| Affects Version/s: | 2.0.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Stefan Huber | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | crash | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
CentOS 5.6 64bit |
||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
Made a clean install of mongodb 2.0.0 (e.g. removed all database files of an existing 1.8.3 installation prior try running the server). However the server instantly dies instantaneously Tue Sep 13 01:04:42 BackgroundJob starting: DataFileSync Tue Sep 13 01:04:42 [initandlisten] flushing directory /var/mongodb Tue Sep 13 01:04:42 Got signal: 11 (Segmentation fault). Tue Sep 13 01:04:42 Backtrace: Logstream::get called in uninitialized state I've attached the strace of running An 1.8.3 installation on the same server runs without any problems using the same configuration. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 13/Sep/11 ] |
|
great |
| Comment by Stefan Huber [ 13/Sep/11 ] |
|
just rebuild using a newer version of boost (namely 1.41) |
| Comment by Eliot Horowitz (Inactive) [ 13/Sep/11 ] |
|
That version of boost is known to have bugs, can you try updating? |
| Comment by Stefan Huber [ 13/Sep/11 ] |
|
BOOST_LIB_VERSION=1_33_1 Building is essentially done using these steps: |
| Comment by Eliot Horowitz (Inactive) [ 13/Sep/11 ] |
|
what version of boost do you have installed, and how did you compile? |
| Comment by Stefan Huber [ 13/Sep/11 ] |
|
The binary was build directly on the server the same way as various 1.8 builds before. |
| Comment by Eliot Horowitz (Inactive) [ 13/Sep/11 ] |
|
Where is this binary from? |
| Comment by Stefan Huber [ 13/Sep/11 ] |
|
I created the directory just for testing e.g. it was completely empty before running mongodb. [root@Jeeves ~]# ls -la /data/db |
| Comment by Eliot Horowitz (Inactive) [ 13/Sep/11 ] |
|
What's in /data/db/ |
| Comment by Stefan Huber [ 13/Sep/11 ] |
|
Still the same issue using an empty directory and without my mongod.conf file [root@Jeeves ~]# /opt/mongodb-2.0.0/bin/mongod -vvv Tue Sep 13 18:33:55 [initandlisten] flushing directory /data/db Tue Sep 13 18:33:55 Got signal: 11 (Segmentation fault). Tue Sep 13 18:33:55 Backtrace: Logstream::get called in uninitialized state Edited: Include right log message |
| Comment by Eliot Horowitz (Inactive) [ 13/Sep/11 ] |
|
Can you remove the old journal directory? |
| Comment by Stefan Huber [ 13/Sep/11 ] |
|
[root@Jeeves ~]# ls -la /var/mongodb/ I attached my config file which I forgot in the first place. |
| Comment by Eliot Horowitz (Inactive) [ 13/Sep/11 ] |
|
The 2.0 starts seems to be using /var/mongodb |