Hi I’ve been using mongoDB now for a short bit and after an scheduled reboot it will not start anymore. I’m using a cloud controller of Unify and there it was recommended to use MongoDB.
Current version;
db version v4.4.29
Build Info: {
"version": "4.4.29",
"gitVersion": "f4dda329a99811c707eb06d05ad023599f9be263",
"openSSLVersion": "OpenSSL 1.1.1f 31 Mar 2020",
"modules": [],
"allocator": "tcmalloc",
"environment": {
"distmod": "ubuntu1804",
"distarch": "x86_64",
"target_arch": "x86_64"
}
}
content of mongod.conf
# for documentation of all options, see:
# http://docs.mongodb.org/manual/reference/configuration-options/
# Where and how to store data.
storage:
dbPath: /var/lib/mongodb
journal:
enabled: true
# engine:
# mmapv1:
# wiredTiger:
# where to write logging data.
systemLog:
destination: file
logAppend: true
path: /var/log/mongodb/mongod.log
# network interfaces
net:
port: 27017
bindIp: 127.0.0.1
# how the process runs
processManagement:
timeZoneInfo: /usr/share/zoneinfo```
MongoDB.log content
2024-06-08T21:04:09.367+0000 I STORAGE [initandlisten] WiredTiger message [1717880649:367453][999656:0x733dd7ad8480], txn-recover: Main recovery loop: starting at 1/22528
2024-06-08T21:04:09.477+0000 I STORAGE [initandlisten] WiredTiger message [1717880649:477271][999656:0x733dd7ad8480], txn-recover: Recovering log 1 through 2
2024-06-08T21:04:09.552+0000 I STORAGE [initandlisten] WiredTiger message [1717880649:552097][999656:0x733dd7ad8480], txn-recover: Recovering log 2 through 2
2024-06-08T21:04:09.595+0000 I STORAGE [initandlisten] WiredTiger message [1717880649:595564][999656:0x733dd7ad8480], txn-recover: Set global recovery timestamp: 0
2024-06-08T21:04:09.823+0000 I CONTROL [initandlisten]
2024-06-08T21:04:09.823+0000 I CONTROL [initandlisten] ** WARNING: Access control is not enabled for the database.
2024-06-08T21:04:09.823+0000 I CONTROL [initandlisten] ** Read and write access to data and configuration is unrestricted.
2024-06-08T21:04:09.823+0000 I CONTROL [initandlisten]
2024-06-08T21:04:09.824+0000 I CONTROL [initandlisten]
2024-06-08T21:04:09.824+0000 I CONTROL [initandlisten] ** WARNING: You are running on a NUMA machine.
2024-06-08T21:04:09.824+0000 I CONTROL [initandlisten] ** We suggest launching mongod like this to avoid performance problems:
2024-06-08T21:04:09.824+0000 I CONTROL [initandlisten] ** numactl --interleave=all mongod [other options]
2024-06-08T21:04:09.827+0000 I CONTROL [initandlisten]
2024-06-08T21:04:09.889+0000 I FTDC [initandlisten] Initializing full-time diagnostic data capture with directory ‘/var/lib/mongodb/diagnostic.data’
2024-06-08T21:04:09.892+0000 I NETWORK [initandlisten] listening via socket bound to 127.0.0.1
2024-06-08T21:04:09.892+0000 I NETWORK [initandlisten] listening via socket bound to /tmp/mongodb-27017.sock
2024-06-08T21:04:09.892+0000 I NETWORK [initandlisten] waiting for connections on port 27017
2024-07-01T06:38:30.539+0000 I CONTROL [signalProcessingThread] got signal 15 (Terminated), will terminate after current cmd ends
2024-07-01T06:38:30.608+0000 I NETWORK [signalProcessingThread] shutdown: going to close listening sockets…
2024-07-01T06:38:30.609+0000 I NETWORK [signalProcessingThread] removing socket file: /tmp/mongodb-27017.sock
2024-07-01T06:38:30.617+0000 I FTDC [signalProcessingThread] Shutting down full-time diagnostic data capture
2024-07-01T06:38:30.644+0000 I STORAGE [signalProcessingThread] WiredTigerKVEngine shutting down
2024-07-01T06:38:30.872+0000 I STORAGE [signalProcessingThread] shutdown: removing fs lock…
2024-07-01T06:38:30.873+0000 I CONTROL [signalProcessingThread] now exiting
2024-07-01T06:38:30.873+0000 I CONTROL [signalProcessingThread] shutting down with code:0
If anyone has any clue on how to apporoach this issue so we are able to get the cloud portal webstite back up and running please let me know! All the help is greatly appreciated!!!!