Note that there are some explanatory texts on larger screens.

plurals
  1. POMongodb crashing all the time
    text
    copied!<p>I'm running a single instance mongodb, and the database is crashing all the time. Anyone knows if this problem is related with running in a single instance?</p> <p>Tue Aug 9 09:02:59 [initandlisten] connection accepted from 127.0.0.1:60194 #129526 Tue Aug 9 09:17:04 [initandlisten] MongoDB starting : pid=517 port=27017 dbpath=/var/lib/mongodb 32-bit </p> <p>** NOTE: when using MongoDB 32 bit, you are limited to about 2 gigabytes of data ** see <a href="http://blog.mongodb.org/post/137788967/32-bit-limitations" rel="nofollow">http://blog.mongodb.org/post/137788967/32-bit-limitations</a> ** with --dur, the limit is lower</p> <p>Tue Aug 9 09:17:04 [initandlisten] db version v1.8.2, pdfile version 4.5 Tue Aug 9 09:17:04 [initandlisten] git version: 433bbaa14aaba6860da15bd4de8edf600f56501b Tue Aug 9 09:17:04 [initandlisten] build sys info: Linux bs-linux32.10gen.cc 2.6.21.7-2.fc8xen #1 SMP Fri Feb 15 12:39:36 EST 2008 i686 BOOST_LIB_VERSION=1_37</p> <hr> <p>old lock file: /var/lib/mongodb/mongod.lock. probably means unclean shutdown recommend removing file and running --repair see: <a href="http://dochub.mongodb.org/core/repair" rel="nofollow">http://dochub.mongodb.org/core/repair</a> for more information</p> <hr> <p>Tue Aug 9 09:17:05 [initandlisten] exception in initAndListen std::exception: old lock file, terminating Tue Aug 9 09:17:05 dbexit: Tue Aug 9 09:17:05 [initandlisten] shutdown: going to close listening sockets... Tue Aug 9 09:17:05 [initandlisten] shutdown: going to flush diaglog... Tue Aug 9 09:17:05 [initandlisten] shutdown: going to close sockets... Tue Aug 9 09:17:05 [initandlisten] shutdown: waiting for fs preallocator... Tue Aug 9 09:17:05 [initandlisten] shutdown: closing all files... Tue Aug 9 09:17:05 closeAllFiles() finished Tue Aug 9 09:17:05 dbexit: really exiting now</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload