-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: 1.8.1
-
Component/s: JavaScript
-
None
-
Environment:Ubuntu 10.04.2 LTS, 4GB RAM VMWare instance with one CPU core (Intel(R) Xeon(R) CPU X5680 @ 3.33GHz)
Three member replica set, running as follows:
mongod --pidfilepath /var/lib/mongodb/seta.pid --config /etc/mongodb/seta.conf --replSet seta --dbpath /var/lib/mongodb/seta -vvvvv --port 27017 --logpath /var/log/mongodb/seta.log
/etc/mongodb/seta.conf:
logappend=true
noprealloc = true
smallfiles = true
directoryperdb = true
We were crashing with 1.8.1 from the 10gben deb repo, and we just got another segfault today running mongod --version
db version v1.8.2-rc1, pdfile version 4.5
Mon May 23 17:18:45 git version: da537eae3ec18611424dabb63a202d4940059be4
Members are running *only* MongoDB, and nothing else
This is the same setup which was discussed at http://groups.google.com/group/mongodb-user/browse_thread/thread/35efda30f3aeff35Ubuntu 10.04.2 LTS, 4GB RAM VMWare instance with one CPU core (Intel(R) Xeon(R) CPU X5680 @ 3.33GHz) Three member replica set, running as follows: mongod --pidfilepath /var/lib/mongodb/seta.pid --config /etc/mongodb/seta.conf --replSet seta --dbpath /var/lib/mongodb/seta -vvvvv --port 27017 --logpath /var/log/mongodb/seta.log /etc/mongodb/seta.conf: logappend=true noprealloc = true smallfiles = true directoryperdb = true We were crashing with 1.8.1 from the 10gben deb repo, and we just got another segfault today running mongod --version db version v1.8.2-rc1, pdfile version 4.5 Mon May 23 17:18:45 git version: da537eae3ec18611424dabb63a202d4940059be4 Members are running *only* MongoDB, and nothing else This is the same setup which was discussed at http://groups.google.com/group/mongodb-user/browse_thread/thread/35efda30f3aeff35
-
Linux
Full details are at http://foswiki.org/Tasks/Item10672?section=mongodb-user2#Crash_5 (and even more details at http://foswiki.org/Tasks/Item10672).
We tested for two weeks before putting into production, a new version of our application (Foswiki) using MongoDB 1.8.1 as a query-cache/accelerator. There were no unexplained instabilities. In production now though, we can run the site for a couple of days, but at least twice a week we are getting segfaults in whichever mongod happens to be the primary.
It's not a sudden thing - we get these spurious JS Error: out of memory and Assertion: 10432:JS_NewObject failed for global warnings in the log, for an hour or two, before the mongod process segfaults.
The problem is extremely hard to reproduce; we haven't been able to reproduce ourselves, in our test environment, using artificial loads (our production site is public to the Internet).
seta.log.022c is a snippet leading up to the latest segfault.
seta.log.022b is a snippet leading up to and including the first few minutes of problems after running fine for a couple of days.
Both are using -vvvvv verbosity, which generates ~10GB/day of log files (extremely burdensome), so I've filtered them using grep -v ^checking