MongoDB 5.0.15 is out and is ready for production deployment. This release contains only fixes since 5.0.14, and is a recommended upgrade for all 5.0 users.
Fixed in this release:
SERVER-54900 Blocking networking calls can delay
sync-source resolution indefinitely
would help the start up following an update. These are for new install of for installations that were tempered with. If you are updating then your directories and the permissions should already be there and correct.
I would say yes since an update might need to setup new directories, new resources or even have new dependencies from other services… I keep my /etc under git so I know and document what is happening.
Like I mentioned I do not know about PermissionsStartOnly, PIDFile and Type but I do not see how the following would stop an update to restart.
but I have an error mesage when trying to start the service
Job for mongod.service failed because the control process exited with error code. See “systemctl status mongod.service” and “journalctl -xe” for details.
mongod[14313]: about to fork child process, waiting until server is ready for connections.
mongod[14313]: forked process: 14316
mongod[14313]: ERROR: child process failed, exited with 14
mongod[14313]: To see additional information in this output, start without the “–fork” option.
systemd[1]: mongod.service: control process exited, code=exited status=14
systemd[1]: Failed to start MongoDB Database Server.
– Subject: Unit mongod.service has failed
– Defined-By: systemd
– Support: systemd-devel Info Page