mongod --dbpath /some/dir --logpath /other/mng.log
and make sure that your mongodb works by connecting to it with just:
mongo
Verify the version. Then you can start playing with more complex setups & options.
sudo chmod 0755/media/sf_Server/data/db sudo chown mongod:mongod/media/sf_Server/data/db
then :
sudo service mongod start
Hi Aaron,
VirtualBox shared folders do not support fsync on directories, so your dbpath needs to live on a non-shared directory within the VM.
To confirm if your dbpath is on a supported filesystem format, you could try running ‘mongod’ directly on a shell first.
mongod --dpath /media/sf_Server/data/db
A VirtualBox shared folder will currently produce an error message (and a backtrace) containing :
[initandlisten] WARNING: This file system is not supported. For further information see:
[initandlisten] http://dochub.mongodb.org/core/unsupported-filesystems
[initandlisten] Please notify MongoDB, Inc. if an unlisted filesystem generated this warning.
OR if you are using WiredTiger storage engine:
[initandlisten] WiredTiger (22) ... fsync: Invalid argument
[initandlisten] Fatal Assertion 28561
Regards,
Wan