Hi @sam_ames,
Stop the service and do the following command:
chown -R mongodb:mongodb /data/var/lib/mongodb
And try to start the mongod service again.
If It doesn’ t work, paste the status of service and the logs.
Regards
sysadmin@server:~$ chown -R mongodb:mongodb /data/var/lib/mongodb
chown: cannot read directory '/data/var/lib/mongodb': Permission denied
sysadmin@server:~$ sudo chown -R mongodb:mongodb /data/var/lib/mongodb
[sudo] password for sysadmin:
sysadmin@server:~$ sudo systerctl start mongod
sudo: systerctl: command not found
sysadmin@server:~$ sudo systemctl start mongod
sysadmin@server:~$ sudo systemctl status mongod
× mongod.service - MongoDB Database Server
Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2023-08-11 07:44:29 UTC; 10s ago
Docs: https://docs.mongodb.org/manual
Process: 85895 ExecStart=/usr/bin/mongod --config /etc/mongod.conf (code=exited, status=100)
Main PID: 85895 (code=exited, status=100)
CPU: 31ms
Aug 11 07:44:29 server systemd[1]: Started MongoDB Database Server.
Aug 11 07:44:29 server mongod[85895]: {"t":{"$date":"2023-08-11T07:44:29.870Z"},"s":"I", "c":"CONTROL", "id":7484500, "ctx":"-","msg":"Environment variable MONGODB_CONFIG_OVERRIDE_NOFORK == 1, overriding \"processManagement.fo>
Aug 11 07:44:29 server systemd[1]: mongod.service: Main process exited, code=exited, status=100/n/a
Aug 11 07:44:29 server systemd[1]: mongod.service: Failed with result 'exit-code'.
lines 1-12/12 (END)
sysadmin@server:~$ sudo tail -f /var/log/mongodb/mongod.log
{"t":{"$date":"2023-08-11T07:44:29.880+00:00"},"s":"I", "c":"ASIO", "id":22582, "ctx":"MigrationUtil-TaskExecutor","msg":"Killing all outstanding egress activity."}
{"t":{"$date":"2023-08-11T07:44:29.880+00:00"},"s":"I", "c":"COMMAND", "id":4784923, "ctx":"initandlisten","msg":"Shutting down the ServiceEntryPoint"}
{"t":{"$date":"2023-08-11T07:44:29.880+00:00"},"s":"I", "c":"CONTROL", "id":4784925, "ctx":"initandlisten","msg":"Shutting down free monitoring"}
{"t":{"$date":"2023-08-11T07:44:29.880+00:00"},"s":"I", "c":"CONTROL", "id":4784927, "ctx":"initandlisten","msg":"Shutting down the HealthLog"}
{"t":{"$date":"2023-08-11T07:44:29.880+00:00"},"s":"I", "c":"CONTROL", "id":4784928, "ctx":"initandlisten","msg":"Shutting down the TTL monitor"}
{"t":{"$date":"2023-08-11T07:44:29.880+00:00"},"s":"I", "c":"CONTROL", "id":6278511, "ctx":"initandlisten","msg":"Shutting down the Change Stream Expired Pre-images Remover"}
{"t":{"$date":"2023-08-11T07:44:29.880+00:00"},"s":"I", "c":"CONTROL", "id":4784929, "ctx":"initandlisten","msg":"Acquiring the global lock for shutdown"}
{"t":{"$date":"2023-08-11T07:44:29.880+00:00"},"s":"I", "c":"-", "id":4784931, "ctx":"initandlisten","msg":"Dropping the scope cache for shutdown"}
{"t":{"$date":"2023-08-11T07:44:29.880+00:00"},"s":"I", "c":"CONTROL", "id":20565, "ctx":"initandlisten","msg":"Now exiting"}
{"t":{"$date":"2023-08-11T07:44:29.880+00:00"},"s":"I", "c":"CONTROL", "id":23138, "ctx":"initandlisten","msg":"Shutting down","attr":{"exitCode":100}}
Frustrating…
But thanks for your support 
Hi @sam_ames
Here is your error.
I would delete this environment variable and check if it starts running
Regards
This is the error
Do the chown using sudo.
I really must improve my reading skills. B-)
~~ /) ~~
I commented out the var.
Now I have:
sysadmin@soft-serve:~$ sudo nano /usr/lib/systemd/system/mongod.service
sysadmin@soft-serve:~$ sudo systemctl start mongod
Warning: The unit file, source configuration file or drop-ins of mongod.service changed on disk. Run 'systemctl daemon-reload' to reload units.
sysadmin@soft-serve:~$ sudo systemctl daemon-reload
sysadmin@soft-serve:~$ sudo systemctl start mongod
sysadmin@soft-serve:~$ sudo systemctl status mongod
× mongod.service - MongoDB Database Server
Loaded: loaded (/lib/systemd/system/mongod.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2023-08-11 15:33:50 UTC; 14s ago
Docs: https://docs.mongodb.org/manual
Process: 88421 ExecStart=/usr/bin/mongod --config /etc/mongod.conf (code=exited, status=100)
Main PID: 88421 (code=exited, status=100)
CPU: 39ms
Aug 11 15:33:50 soft-serve systemd[1]: Started MongoDB Database Server.
Aug 11 15:33:50 soft-serve systemd[1]: mongod.service: Main process exited, code=exited, status=100/n/a
Aug 11 15:33:50 soft-serve systemd[1]: mongod.service: Failed with result 'exit-code'.
Log:
{"t":{"$date":"2023-08-11T15:33:50.795+00:00"},"s":"I", "c":"CONTROL", "id":20698, "ctx":"-","msg":"***** SERVER RESTARTED *****"}
{"t":{"$date":"2023-08-11T15:33:50.797+00:00"},"s":"I", "c":"NETWORK", "id":4915701, "ctx":"main","msg":"Initialized wire specification","attr":{"spec":{"incomingExternalClient":{"minWireVersion":0,"maxWireVersion":17},"incomingIn>
{"t":{"$date":"2023-08-11T15:33:50.797+00:00"},"s":"I", "c":"CONTROL", "id":23285, "ctx":"main","msg":"Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'"}
{"t":{"$date":"2023-08-11T15:33:50.797+00:00"},"s":"I", "c":"NETWORK", "id":4648601, "ctx":"main","msg":"Implicit TCP FastOpen unavailable. If TCP FastOpen is required, set tcpFastOpenServer, tcpFastOpenClient, and tcpFastOpenQueu>
{"t":{"$date":"2023-08-11T15:33:50.805+00:00"},"s":"I", "c":"REPL", "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationDonorService","namespace":"config.tenantMigrati>
{"t":{"$date":"2023-08-11T15:33:50.805+00:00"},"s":"I", "c":"REPL", "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"TenantMigrationRecipientService","namespace":"config.tenantMig>
{"t":{"$date":"2023-08-11T15:33:50.805+00:00"},"s":"I", "c":"REPL", "id":5123008, "ctx":"main","msg":"Successfully registered PrimaryOnlyService","attr":{"service":"ShardSplitDonorService","namespace":"config.tenantSplitDonors">
{"t":{"$date":"2023-08-11T15:33:50.805+00:00"},"s":"I", "c":"CONTROL", "id":5945603, "ctx":"main","msg":"Multi threading initialized"}
{"t":{"$date":"2023-08-11T15:33:50.805+00:00"},"s":"I", "c":"CONTROL", "id":4615611, "ctx":"initandlisten","msg":"MongoDB starting","attr":{"pid":88421,"port":27017,"dbPath":"/data/var/lib/mongodb","architecture":"64-bit","host":">
{"t":{"$date":"2023-08-11T15:33:50.805+00:00"},"s":"I", "c":"CONTROL", "id":23403, "ctx":"initandlisten","msg":"Build Info","attr":{"buildInfo":{"version":"6.0.8","gitVersion":"3d84c0dd4e5d99be0d69003652313e7eaf4cdd74","openSSLV>
{"t":{"$date":"2023-08-11T15:33:50.805+00:00"},"s":"I", "c":"CONTROL", "id":51765, "ctx":"initandlisten","msg":"Operating System","attr":{"os":{"name":"Ubuntu","version":"22.04"}}}
{"t":{"$date":"2023-08-11T15:33:50.805+00:00"},"s":"I", "c":"CONTROL", "id":21951, "ctx":"initandlisten","msg":"Options set by command line","attr":{"options":{"config":"/etc/mongod.conf","net":{"bindIp":"127.0.0.1","port":27017>
{"t":{"$date":"2023-08-11T15:33:50.806+00:00"},"s":"E", "c":"CONTROL", "id":20557, "ctx":"initandlisten","msg":"DBException in initAndListen, terminating","attr":{"error":"Location28596: Unable to determine status of lock file i>
{"t":{"$date":"2023-08-11T15:33:50.806+00:00"},"s":"I", "c":"REPL", "id":4784900, "ctx":"initandlisten","msg":"Stepping down the ReplicationCoordinator for shutdown","attr":{"waitTimeMillis":15000}}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"REPL", "id":4794602, "ctx":"initandlisten","msg":"Attempting to enter quiesce mode"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"-", "id":6371601, "ctx":"initandlisten","msg":"Shutting down the FLE Crud thread pool"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"COMMAND", "id":4784901, "ctx":"initandlisten","msg":"Shutting down the MirrorMaestro"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"SHARDING", "id":4784902, "ctx":"initandlisten","msg":"Shutting down the WaitForMajorityService"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"NETWORK", "id":20562, "ctx":"initandlisten","msg":"Shutdown: going to close listening sockets"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"NETWORK", "id":4784905, "ctx":"initandlisten","msg":"Shutting down the global connection pool"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"CONTROL", "id":4784906, "ctx":"initandlisten","msg":"Shutting down the FlowControlTicketholder"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"-", "id":20520, "ctx":"initandlisten","msg":"Stopping further Flow Control ticket acquisitions."}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"NETWORK", "id":4784918, "ctx":"initandlisten","msg":"Shutting down the ReplicaSetMonitor"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"SHARDING", "id":4784921, "ctx":"initandlisten","msg":"Shutting down the MigrationUtilExecutor"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"ASIO", "id":22582, "ctx":"MigrationUtil-TaskExecutor","msg":"Killing all outstanding egress activity."}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"COMMAND", "id":4784923, "ctx":"initandlisten","msg":"Shutting down the ServiceEntryPoint"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"CONTROL", "id":4784925, "ctx":"initandlisten","msg":"Shutting down free monitoring"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"CONTROL", "id":4784927, "ctx":"initandlisten","msg":"Shutting down the HealthLog"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"CONTROL", "id":4784928, "ctx":"initandlisten","msg":"Shutting down the TTL monitor"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"CONTROL", "id":6278511, "ctx":"initandlisten","msg":"Shutting down the Change Stream Expired Pre-images Remover"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"CONTROL", "id":4784929, "ctx":"initandlisten","msg":"Acquiring the global lock for shutdown"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"-", "id":4784931, "ctx":"initandlisten","msg":"Dropping the scope cache for shutdown"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"CONTROL", "id":20565, "ctx":"initandlisten","msg":"Now exiting"}
{"t":{"$date":"2023-08-11T15:33:50.807+00:00"},"s":"I", "c":"CONTROL", "id":23138, "ctx":"initandlisten","msg":"Shutting down","attr":{"exitCode":100}}
Would you consider downgrading, if in this situation yourself?.. As suggested in this post?
Thanks for your support
Sam
Hi @sam_ames,
Is selinux disabled?
The error now Is changed:
In the extreme case, I would attempt to remove the files under the path /data/var/lib/mongodb (if you haven’ t collection populated with document in your istance) because seems corrupted the lock file or as you’ve suggested, try a downgrade or update.
Regards
It is a difficult install, I don’t even know what is se Linux is to be perfectly honest
Thanks,
Sam
I will try your suggestions on Monday morning, many thanks
Default install of Ubuntu **
sysadmin@soft-serve:~$ sudo cat /etc/selinux/config
[sudo] password for sysadmin:
cat: /etc/selinux/config: No such file or directory
It seems like your suspicions were correct.
Please suggest how I can resolve this. I did not delete selinux and am not sure why it’s missing.
Thanks for the support,
Sam
Hi @sam_ames,
Another way to get selinux status Is toselinux status with the command
getenforce or cat /etc/sysconfig/selinux.
If the getenforce command results in output of the type enforcing or permissive, use the following command:
setenforce 0.
But as suggested in a previous post, i think is better to clean your data directory or do and update for resolve the problem
Regards
Please see the following output.
sysadmin@soft-serve:~$ cat /etc/sysconfig/selinux
cat: /etc/sysconfig/selinux: No such file or directory
sysadmin@soft-serve:~$ getenforce
Command 'getenforce' not found, but can be installed with:
sudo apt install selinux-utils
sysadmin@soft-serve:~$ sudo getenforce
[sudo] password for sysadmin:
sudo: getenforce: command not found
sysadmin@soft-serve:~$
Do I need to install selinux tools?
Thanks,
Sam
Hi @sam_ames,
In theory no, it should be present by default in the os.
Try the solutions discussed last time and let me know if they work
Regards
I can’t swipe the data volume because it is part of a raid partition and it was very complicated to set up.
However, I can delete everything in the directory that I have personally added. Is this worth doing?
You previously mentioned a downgrade, which version should I consider? I think I am currently using the latest release of version six. The post I shared, which mentioned downgrading was quite an old one so I assume the recommended version is no no longer the optimal solution.
Thank you,
Sam
All I’ve done is done is changed the directory. I’m amazed that this is so complicated…
Thanks for supporting me, Fabio
1 Like
Sorry, I wasn’t clear. The problem is not resolved, I was just complaining about how complicated this issue is to resolve.