I am getting this error while installing the mongodb on my windows7 system.
C:>mongodb\bin\mongo.exe
MongoDB shell version: 2.4.3
connecting to: test
Server has startup warnings:
Sun May 12 16:19:51.162 [initandlisten]
Sun May 12 16:19:51.162 [initandlisten] ** NOTE: This is a 32 bit MongoDB binary
.
Sun May 12 16:19:51.163 [initandlisten] ** 32 bit builds are limited to le
ss than 2GB of data (or less with --journal).
Sun May 12 16:19:51.163 [initandlisten] ** Note that journaling defaults t
o off for 32 bit and is currently off.
Sun May 12 16:19:51.163 [initandlisten] ** See http://dochub.mongodb.org/core/32bit
Sun May 12 16:19:51.164 [initandlisten]
I didn't find any solution for this. Any help? Thank you
Where is your error?It's just a warning that you shouldn't use Mongo on 32-bit machines because then the limit of storage size is 2 GB. Just read the article in the link you already have.
Related
The mongod command gets stuck after the following line. I haven't changed any setting. I also encountered the problem saying "/data/db", solved it by creating the directory. Restarting doesn't have any changes.
**mongod --help for help and startup options
32-bit servers don't have journaling enabled by default. Please use --journal if you want durability.
pid=5517 port=27017 dbpath=/data/db/ 32-bit host=nxtgplus-test
[initandlisten]
[initandlisten] ** NOTE: This is a 32 bit MongoDB binary.
[initandlisten] ** 32 bit builds are limited to less than 2GB of data (or less with --journal).
[initandlisten] ** Note that journaling defaults to off for 32 bit and is currently off.
[initandlisten] ** See http://dochub.mongodb.org/core/32bit
[initandlisten]
[initandlisten] db version v2.4.14
[initandlisten] git version: nogitversion
[initandlisten] build info: Linux buildvm-03.phx2.fedoraproject.org 3.19.5-200.fc21.x86_64 #1 SMP Mon
Apr 20 19:51:56 UTC 2015 i686 BOOST_LIB_VERSION=1_41
[initandlisten] allocator: system
[initandlisten] options: {}
[initandlisten] waiting for connections on port 27017
[websvr] admin web console waiting for connections on port
I am working on CentOS release 6.7 (Final) server. Please help me solve the above issue.
I am using 32 bit windows machine and using 32 bit mongodb. I noticed my database is not starting and it says
** WARNING: This 32-bit MongoDB binary is deprecated
2016-01-03T16:53:03.720+0100 I CONTROL [initandlisten]
2016-01-03T16:53:03.725+0100 I CONTROL [initandlisten]
2016-01-03T16:53:03.732+0100 I CONTROL [initandlisten] ** NOTE: This is a 32 bit MongoDB binary.
2016-01-03T16:53:03.740+0100 I CONTROL [initandlisten] ** 32 bit builds are limited to less than 2GB of data (or less with --journal).
2016-01-03T16:53:03.754+0100 I CONTROL [initandlisten] ** Note that journaling defaults to off for 32 bit and is currently off.
2016-01-03T16:53:03.761+0100 I CONTROL [initandlisten] ** See http://dochub.mongodb.org/core/32bit
2016-01-03T16:53:03.771+0100 I CONTROL [initandlisten]
My database size is 2.03gb. Now, I want to delete some unnecessary collections.
But without even starting the mongoDB server how can I delete some collections?
in 32-bit version of mongodb there is a limit of file size with 2gb , tou can try --smallfiles in mongod which will create a 512mb data files rather 2 gb, and more over it is a warning.
thanks,
Darshan J
The process of adding a mongoDb (2.4) cartridge to my OpenShift application seems to work fine but ends up with an error and no cartridge is added. It looks like a disk space problem (I have already mysql in the same application), but I freed plenty of space and, strangely enough, the problem only appears at the very end of setup. Here is the log (hiding login details):
Starting MongoDB cartridge
note: noprealloc may hurt performance in many applications
Sat May 3 19:38:54.847 [initandlisten] MongoDB starting : pid=389973 port=2701
dbpath=/var/lib/openshift/5c0013917b4d45c68fddbb75e082a35a/mongodb/data/ 64-bit host=ex-std-node94.prod.rhcloud.com
Sat May 3 19:38:54.848 [initandlisten] db version v2.4.6
Sat May 3 19:38:54.848 [initandlisten] git version: nogitversion
Sat May 3 19:38:54.848 [initandlisten] build info: Linux x86-023.build.eng.bos.redhat.com 2.6.18-371.el5 #1 SMP Thu Sep 5 21:21:44 EDT 2013 x86_64 BOOST_LIB_VERSION=1_41
Sat May 3 19:38:54.849 [initandlisten] allocator: tcmalloc
Sat May 3 19:38:54.849 [initandlisten] options: { auth: true, bind_ip: "127.2.148.131", config: "/tmp/mongodb.repair.conf", dbpath: "/var/lib/openshift/5c0013917b4d45c68fddbb75e082a35a/mongodb/data/", nohttpinterface: "true", noprealloc: "true", pidfilepath: "/var/lib/openshift/5c0013917b4d45c68fddbb75e082a35a/mongodb/pid/mongodb.pid", quiet: "true", repair: true, smallfiles: "true" }
**************
You specified --repair but there are dirty journal files. Please
restart without --repair to allow the journal files to be replayed.
If you wish to repair all databases, please shutdown cleanly and
run with --repair again.
**************
Sat May 3 19:38:54.865 [initandlisten] exception in initAndListen: 12596 old lock file, terminating
Sat May 3 19:38:54.866 dbexit:
Sat May 3 19:38:54.866 [initandlisten] shutdown: going to close listening sockets...
Sat May 3 19:38:54.866 [initandlisten] shutdown: going to flush diaglog...
Sat May 3 19:38:54.867 [initandlisten] shutdown: going to close sockets...
Sat May 3 19:38:54.867 [initandlisten] shutdown: waiting for fs preallocator...
Sat May 3 19:38:54.867 [initandlisten] shutdown: closing all files...
Sat May 3 19:38:54.867 [initandlisten] closeAllFiles() finished
Sat May 3 19:38:54.868 dbexit: really exiting now
Warning: Gear 5c0013917b4d45c68fddbb75e082a35a is using 98.9% of disk quota
Warning: Gear 5c0013917b4d45c68fddbb75e082a35a is using 97.3% of disk quota
Attempting to repair MongoDB ...
MongoDB 2.4 database added. Please make note of these credentials:
Root User: ------------
Root Password: ------------
Database Name: ------------
Connection URL: mongodb://$OPENSHIFT_MONGODB_DB_HOST:$OPENSHIFT_MONGODB_DB_PORT/
Failed to execute: 'control start' for /var/lib/openshift/5c0013917b4d45c68fddbb75e082a35a/mongodb
Any idea on how to solve it? Thank you
Yes, as per the logs it looks like you have consumed most of your 1GB disk space. The 1 GB disk space is consumed by all your application cartridges and storage.Which web cartridge are you using? Can you check the disk space usage using quota -s command. SSH into the application gear and run quota -s command. Or if you have rhc command-line installed then you can use rhc ssh --app <app_name> --command 'quota -s'. You can clean up disk space using rhc tidy --app <app_name> command. After cleaning up, try running rhc cartridge command again. You can create a scalable application and that would allow every cartridge to be installed on a different gear. This would allow each cartridge more disk space.
I am running solaris 10.
I downloaded the 2.4.1 driver from mongodb.org
Here are the logs:
foo $ ./mongod --dbpath /dpool/mongodb/data --pidfilepath /dpool/mongodb/run/mongod.pid
Wed Apr 10 21:19:54.832 [initandlisten] MongoDB starting : pid=25116 port=27017 dbpath=/dpool/mongodb/data 64-bit host=foo.example.net
Wed Apr 10 21:19:54.833 [initandlisten]
Wed Apr 10 21:19:54.833 [initandlisten] ** NOTE: your operating system version does not support the method that MongoDB
Wed Apr 10 21:19:54.833 [initandlisten] ** uses to detect impending page faults.
Wed Apr 10 21:19:54.833 [initandlisten] ** This may result in slower performance for certain use cases
Wed Apr 10 21:19:54.833 [initandlisten]
Wed Apr 10 21:19:54.833 [initandlisten] db version v2.4.1
Wed Apr 10 21:19:54.833 [initandlisten] git version: 1560959e9ce11a693be8b4d0d160d633eee75110
Wed Apr 10 21:19:54.833 [initandlisten] build info: SunOS bs-smartos-x86-64-1.10gen.cc 5.11 joyent_20120424T232010Z i86pc BOOST_LIB_VERSION=1_49
Wed Apr 10 21:19:54.833 [initandlisten] allocator: system
Wed Apr 10 21:19:54.833 [initandlisten] options: { dbpath: "/dpool/mongodb/data", pidfilepath: "/dpool/mongodb/run/mongod.pid" }
Segmentation Fault
foo $ echo $LD_LIBRARY_PATH
/usr/local/mongodb/lib
foo $ ls -lt /usr/local/mongodb/lib
total 6152
-rwxr-xr-x 1 mongo 255312 Oct 26 2009 libgcc_s.so.1
-rwxr-xr-x 1 mongo 5900688 Oct 26 2009 libstdc++.so.6
Any ideas? I used to run version 2.0.3 with no issues....
The MongoDB 2.4.1 build is currently done on SmartOS (which is based on OpenSolaris/Solaris 11), and there are some known issues on Solaris 10.
Your problem may be related to SERVER-7404 in the MongoDB Jira but there could be other issues.
One of the community suggestions on SERVER-7404 may be useful:
After downloading and installing libstdc++6-4.7.2\,REV\=2013.03.28-SunOS5.10-i386-CSW.pkg from opencsw it starts as usual
If you do get this working it would be helpful to comment on the Jira issue so other users know the fix.
This binary looks like to have been tuned for a SunOS 5.11 kernel. You might want to try it under either Solaris 11 or an Illumos based OS to avoid this warning message.
I'm running an Ubuntu 12.04 server instance on VirtualBox on a OS X 10.7 host (MacBook Air 13"). The instance is configured with 512mb ram. The disk image is set to 8GB (dynamically allocated if that makes any difference) and is using 2.6GB.
I've just installed MongoDB from the 10gen repo as described here: http://docs.mongodb.org/manual/tutorial/install-mongodb-on-debian-or-ubuntu-linux/
I haven't changed any of the default settings as yet.
The mongod process is now running at 15-20% cpu constantly, before I've connected anything to it. I wouldn't normally have checked but it's now causing the fans to stay on whenever the VM is running.
Restarting mongodb makes no difference. Restarting the VM makes no difference.
The log is as follows:
Thu Jun 21 16:52:14 [initandlisten] MongoDB starting : pid=1737 port=27017 dbpath=/var/lib/mongodb 64-bit host=devbox
Thu Jun 21 16:52:14 [initandlisten] db version v2.0.6, pdfile version 4.5
Thu Jun 21 16:52:14 [initandlisten] git version: e1c0cbc25863f6356aa4e31375add7bb49fb05bc
Thu Jun 21 16:52:14 [initandlisten] build info: Linux ip-10-110-9-236 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_41
Thu Jun 21 16:52:14 [initandlisten] options: { config: "/etc/mongodb.conf", dbpath: "/var/lib/mongodb", logappend: "true", logpath: "/var/log/mongodb/mongodb.log" }
Thu Jun 21 16:52:14 [initandlisten] journal dir=/var/lib/mongodb/journal
Thu Jun 21 16:52:14 [initandlisten] recover : no journal files present, no recovery needed
Thu Jun 21 16:52:14 [initandlisten] waiting for connections on port 27017
Thu Jun 21 16:52:14 [websvr] admin web console waiting for connections on port 28017
I'm assuming 15-20% cpu usage at idle isn't normal, so I'd like to know if anyone has any suggestions on what to try to fix it?
edit
I've now converted the disk image to a fixed size VDI and it's made no difference, still at 15-20% CPU usage on the guest.
This is a bug in VirtualBox on OSX as far as I can tell, I switched to Parallels and haven't had an issue since.