Backendless Standalone v3.x - MongoDB startup error

General
1

On a reboot of my linux backendless v3.0.0-8 standalone server, I am getting the following error when starting the MongoDB:

2016-01-15T08:01:47.000-0500 ***** SERVER RESTARTED *****
2016-01-15T08:01:47.007-0500 [initandlisten] MongoDB starting : pid=6047 port=27017 dbpath=/opt/backendless-3.0.0-8/mongodb/data/db 32-bit host=Arapahoe.com
2016-01-15T08:01:47.007-0500 [initandlisten]
2016-01-15T08:01:47.007-0500 [initandlisten] ** NOTE: This is a 32 bit MongoDB binary.
2016-01-15T08:01:47.007-0500 [initandlisten] ** 32 bit builds are limited to less than 2GB of data (or less with --journal).
2016-01-15T08:01:47.007-0500 [initandlisten] ** See http://dochub.mongodb.org/core/32bit
2016-01-15T08:01:47.007-0500 [initandlisten]
2016-01-15T08:01:47.007-0500 [initandlisten] db version v2.6.11
2016-01-15T08:01:47.007-0500 [initandlisten] git version: d00c1735675c457f75a12d530bee85421f0c5548
2016-01-15T08:01:47.007-0500 [initandlisten] build info: Linux ip-10-93-139-4 2.6.18-194.el5xen #1 SMP Tue Mar 16 22:08:06 EDT 2010 i686 BOOST_LIB_VERSION=1_49
2016-01-15T08:01:47.007-0500 [initandlisten] allocator: system
2016-01-15T08:01:47.007-0500 [initandlisten] options: { config: “/opt/backendless-3.0.0-8/mongodb/mongodb.conf”, net: { bindIp: “127.0.0.1”, port: 27017, unixDomainSocket: { pathPrefix: “/opt/backendless-3.0.0-8/mongodb/tmp” } }, processManagement: { fork: true, pidFilePath: “/opt/backendless-3.0.0-8/mongodb/tmp/mongodb.pid” }, security: { authorization: “enabled” }, setParameter: { enableLocalhostAuthBypass: “0” }, storage: { dbPath: “/opt/backendless-3.0.0-8/mongodb/data/db”, journal: { enabled: true } }, systemLog: { destination: “file”, logAppend: true, path: “/opt/backendless-3.0.0-8/mongodb/log/mongodb.log” } }
2016-01-15T08:01:47.008-0500 [initandlisten] exception in initAndListen: 12596 old lock file, terminating
2016-01-15T08:01:47.008-0500 [initandlisten] dbexit:
2016-01-15T08:01:47.008-0500 [initandlisten] shutdown: going to close listening sockets…
2016-01-15T08:01:47.008-0500 [initandlisten] shutdown: going to flush diaglog…
2016-01-15T08:01:47.008-0500 [initandlisten] shutdown: going to close sockets…
2016-01-15T08:01:47.008-0500 [initandlisten] shutdown: waiting for fs preallocator…
2016-01-15T08:01:47.008-0500 [initandlisten] shutdown: lock for final commit…
2016-01-15T08:01:47.008-0500 [initandlisten] shutdown: final commit…
2016-01-15T08:01:47.008-0500 [initandlisten] shutdown: closing all files…
2016-01-15T08:01:47.008-0500 [initandlisten] closeAllFiles() finished
2016-01-15T08:01:47.008-0500 [initandlisten] dbexit: really exiting now
ERROR: child process failed, exited with error number 100

2

NOTE: on the Manage Servers tab the mongodb server is “red” even though I can still access via my application and through the console.

3

Hi Roy,

Was it sort of uncontrolled reboot or you rebooted manually?
There is a similar discussion on StackOverflow about “old lock file”.

4

It was a manual reboot.

5

I removed the lock file at: /opt/backendless-3.0.0-8/mongodb/data/db\mongod.lock and started the mongoDB.
Now it is working.

6

Maybe you rebooted your machine without stopping the services?
Please send the logs from /tmp/bitrock_installer_xxxx (if exists) and from backendless-3.0.0-x/apps/backendless/logs to my email: sergey.chupov@themidnightcoders.com.
We shall try to investigate what caused the error.

7

Although my problem wasn’t exactly the same:

Starting mongodb…
Exit code: 3
Stdout:
/Applications/backendless-3.0.0-24/mongodb/scripts/ctl.sh : mongodb could not be started
Stderr:
child process exited abnormally

It was solved by deleting:
/Applications/backendless-3.0.0-24/mongodb/data/db/mongod.lock