Error when upgrading from 2.0.7 to 2.2.1

[Teg]

I have a 32 bit Ubuntu 12.04 development machine running MongoDB 2.0.7 and installed "mongodb20-10gen" from the repositories at http://docs.mongodb.org/manual/tutorial/install-mongodb-on-ubuntu/. I have had no issues running it, using with the PECL PHP extension, and the RockMongo web interface. Recently when I wanted to upgrade to the 2.2.1 series, I stopped the process, ran "sudo apt-get remove mongodb20-10gen && sudo apt-get install mongodb-10gen" into the terminal to start the upgrade. For some reason the process would not start. In the terminal, did "sudo rm /var/lib/mongodb/mongod.lock" followed by "sudo -u mongodb mongod -f /etc/mongodb.conf --repair" followed by "sudo start mongodb" to try to start it again. Still wouldn't start. I even rebooted the computer with the same results. Here is my log file:



***** SERVER RESTARTED *****


Wed Oct 31 12:44:38
Wed Oct 31 12:44:38 warning: 32-bit servers don't have journaling enabled by default. Please use --journal if you want durability.
Wed Oct 31 12:44:38
Wed Oct 31 12:44:38 [initandlisten] MongoDB starting : pid=2542 port=27017 dbpath=/var/lib/mongodb 32-bit host=teg1
Wed Oct 31 12:44:38 [initandlisten]
Wed Oct 31 12:44:38 [initandlisten] ** NOTE: when using MongoDB 32 bit, you are limited to about 2 gigabytes of data
Wed Oct 31 12:44:38 [initandlisten] **       see http://blog.mongodb.org/post/137788967/32-bit-limitations
Wed Oct 31 12:44:38 [initandlisten] **       with --journal, the limit is lower
Wed Oct 31 12:44:38 [initandlisten]
Wed Oct 31 12:44:38 [initandlisten] db version v2.2.1, pdfile version 4.5
Wed Oct 31 12:44:38 [initandlisten] git version: d6764bf8dfe0685521b8bc7b98fd1fab8cfeb5ae
Wed Oct 31 12:44:38 [initandlisten] build info: Linux domU-12-31-39-01-70-B4 2.6.21.7-2.fc8xen #1 SMP Fri Feb 15 12:39:36 EST 2008 i686 BOOST_LIB_VERSION=1_49
Wed Oct 31 12:44:38 [initandlisten] options: { auth: "true", config: "/etc/mongodb.conf", dbpath: "/var/lib/mongodb", logappend: "true", logpath: "/var/log/mongodb/mongodb.log", repair: true }
Wed Oct 31 12:44:38 [initandlisten] Unable to check for journal files due to: boost::filesystem::basic_directory_iterator constructor: No such file or directory: "/var/lib/mongodb/journal"
Wed Oct 31 12:44:38 Invalid operation at address: 0x819b503 from thread: initandlisten

Wed Oct 31 12:44:38 Got signal: 4 (Illegal instruction).

Wed Oct 31 12:44:38 Backtrace:
0x875225a 0x816ffea 0x81706af 0x91040c 0x819b503 0x8547b04 0x8532581 0x8468514 0x83e05f1 0x83e3967 0x83e5694 0x81e8223 0x81b1d4b 0x83d83a7 0x81735c6 0x81742ad 0x8174c45 0x817cf7e 0x817e6a2 0x16c4d3
 mongod(_ZN5mongo15printStackTraceERSo+0x2a) [0x875225a]
 mongod(_ZN5mongo10abruptQuitEi+0x3ba) [0x816ffea]
 mongod(_ZN5mongo24abruptQuitWithAddrSignalEiP7siginfoPv+0x2af) [0x81706af]
 [0x91040c]
 mongod(_ZNK5mongo7BSONObj4copyEv+0x33) [0x819b503]
 mongod(_ZN5mongo11ParsedQuery4initERKNS_7BSONObjE+0x494) [0x8547b04]
 mongod(_ZN5mongo11ParsedQueryC1ERNS_12QueryMessageE+0x91) [0x8532581]
 mongod(_ZN5mongo8runQueryERNS_7MessageERNS_12QueryMessageERNS_5CurOpES1_+0x34) [0x8468514]
 mongod() [0x83e05f1]
 mongod(_ZN5mongo16assembleResponseERNS_7MessageERNS_10DbResponseERKNS_11HostAndPortE+0x3e7) [0x83e3967]
 mongod(_ZN5mongo14DBDirectClient4callERNS_7MessageES2_bPSs+0x84) [0x83e5694]
 mongod(_ZN5mongo14DBClientCursor4initEv+0xc3) [0x81e8223]
 mongod(_ZN5mongo12DBClientBase5queryERKSsNS_5QueryEiiPKNS_7BSONObjEii+0xbb) [0x81b1d4b]
 mongod(_ZN5mongo14DBDirectClient5queryERKSsNS_5QueryEiiPKNS_7BSONObjEii+0x77) [0x83d83a7]
 mongod(_ZN5mongo19clearTmpCollectionsEv+0x286) [0x81735c6]
 mongod(_ZN5mongo14_initAndListenEi+0x47d) [0x81742ad]
 mongod(_ZN5mongo13initAndListenEi+0x25) [0x8174c45]
 mongod() [0x817cf7e]
 mongod(main+0x32) [0x817e6a2]
 /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x16c4d3]

[Dwight Merriman]

is there a particular need to run repair?  during repair more memory will be mapped and with 32 bit binaries i wonder if you are hitting that limit

[Dwight Merriman]

can you post the first few lines of your old 2.0.7 log so i can see the build info there when it was working fine?

On Wednesday, October 31, 2012 1:03:14 PM UTC-4, Teg wrote: