-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.0.0
-
Component/s: Stability
-
Environment:Ubuntu 10.04.3 LTS on an 8GB single core VM
Linux utrin 2.6.32-33-server #72-Ubuntu SMP Fri Jul 29 21:21:55 UTC 2011 x86_64 GNU/Linux
db version v2.0.0, pdfile version 4.5
Fri Nov 11 16:41:29 git version: 695c67dff0ffc361b8568a13366f027caa406222
Single mongod stand-alone, no replica sets or sharding, running a Foswiki installation using the perl MongoDB driver.Ubuntu 10.04.3 LTS on an 8GB single core VM Linux utrin 2.6.32-33-server #72-Ubuntu SMP Fri Jul 29 21:21:55 UTC 2011 x86_64 GNU/Linux db version v2.0.0, pdfile version 4.5 Fri Nov 11 16:41:29 git version: 695c67dff0ffc361b8568a13366f027caa406222 Single mongod stand-alone, no replica sets or sharding, running a Foswiki installation using the perl MongoDB driver.
-
Linux
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
-
None
mongod segfaulted apparently for no reason (unable to correlate this with anything remarkable in the application logs).
For some reason it was building indexes just before the crash. Not sure why it was doing that (nothing in the application's log suggested an action that would have triggered this).
As you can see from the logs, there are some truly nasty queries, a lot of suboptimal stuff going on. I've got some big improvements in the pipeline but they're not deployed yet.
As a result of this crash I've upgraded to mongod 2.0.1 and am now setting up MMS.