Tragic update failure

I tried to update our repository and apparently did something wrong. Rolled back the old repo and mongod is not wanting to run. I’ve changed the db path several times but it doesn’t seem to stick. The following is the output:

/Volumes/ArtsRAID/Deadline/mongo/application/bin/mongod --help for help and startup options
2015-08-25T14:10:50.463-0700 [initandlisten] MongoDB starting : pid=47146 port=27017 dbpath=/data/db 64-bit host=dnhs-arts.pusd.dom
2015-08-25T14:10:50.464-0700 [initandlisten]
2015-08-25T14:10:50.464-0700 [initandlisten] ** WARNING: soft rlimits too low. Number of files is 256, should be at least 1000
2015-08-25T14:10:50.464-0700 [initandlisten] db version v2.6.3
2015-08-25T14:10:50.464-0700 [initandlisten] git version: 255f67a66f9603c59380b2a389e386910bbb52cb
2015-08-25T14:10:50.464-0700 [initandlisten] build info: Darwin mci-osx108-3.build.10gen.cc 12.3.0 Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64 x86_64 BOOST_LIB_VERSION=1_49
2015-08-25T14:10:50.464-0700 [initandlisten] allocator: system
2015-08-25T14:10:50.464-0700 [initandlisten] options: {}
2015-08-25T14:10:50.464-0700 [initandlisten] exception in initAndListen: 10296


ERROR: dbpath (/data/db) does not exist.
Create this directory or give existing directory in --dbpath.
See dochub.mongodb.org/core/startingandstoppingmongo


, terminating
2015-08-25T14:10:50.464-0700 [initandlisten] dbexit:
2015-08-25T14:10:50.464-0700 [initandlisten] shutdown: going to close listening sockets…
2015-08-25T14:10:50.464-0700 [initandlisten] shutdown: going to flush diaglog…
2015-08-25T14:10:50.464-0700 [initandlisten] shutdown: going to close sockets…
2015-08-25T14:10:50.464-0700 [initandlisten] shutdown: waiting for fs preallocator…
2015-08-25T14:10:50.464-0700 [initandlisten] shutdown: lock for final commit…
2015-08-25T14:10:50.464-0700 [initandlisten] shutdown: final commit…
2015-08-25T14:10:50.464-0700 [initandlisten] shutdown: closing all files…
2015-08-25T14:10:50.464-0700 [initandlisten] closeAllFiles() finished
2015-08-25T14:10:50.464-0700 [initandlisten] dbexit: really exiting now

When I attempt to change the directory with --dbpath I get the following error:
2015-08-26T12:49:39.088-0700 [initandlisten] exception in initAndListen: 10310 Unable to lock file: /Volumes/ArtsRAID/Deadline/mongo/data/mongod.lock. Is a mongod instance already running?, terminating

Any instructions on how to update the repository would be great. Thanks, Brad
Edit: Process found running. Still doesn’t work.
Screen Shot 2015-08-25 at 2.17.13 PM.png

I suspect your command is part of the issue here. Can you try running this:

“/Volumes/ArtsRAID/Deadline/mongo/application/bin/mongod” --config “/Volumes/ArtsRAID/Deadline/mongo/application/bin/mongod/data/config.conf”

dnhs-arts:~ administrator$ /Volumes/ArtsRAID/Deadline/mongo/application/bin/mongod --config /Volumes/ArtsRAID/Deadline/mongo/application/bin/mongod/data/config.conf
Error reading config file: Not a directory
try ‘/Volumes/ArtsRAID/Deadline/mongo/application/bin/mongod --help’ for more information

Said config file is somewhere else. Command run with new location:
dnhs-arts:~ administrator$ /Volumes/ArtsRAID/Deadline/mongo/application/bin/mongod --config /Volumes/ArtsRAID/Deadline/mongo/data/config.conf
2015-08-27T12:49:46.680-0700 log file “/Volumes/ArtsRAID/Deadline/mongo/data/logs/log.txt” exists; moved to “/Volumes/ArtsRAID/Deadline/mongo/data/logs/log.txt.2015-08-27T19-49-46”.

Ahh yeah, that was my error for forgetting to properly edit the command. It looks like it’s running now, though!

I haven’t been able to check and see if it’s working. The A/C unit in our server room failed about a week ago and we just discovered it. The RAID that the repository is stored on shut down because it overheated which caused us to investigate. Upon entering the server room yesterday, the temperature was at least 100 Fº in that room so we had to shut everything down and wait for maintenance to show up to repair the A/C unit. I should be able to check tomorrow.

mongod is still not wanting to work. Same error as before.

After a reinstall, everything seems to be good.

Just as a thought, the thermal shutdown feature might be helpful in trying to prevent hardware issues in a situation like that.