systemd (241-7~deb10u5) + tomcat9 (9.0.39-1~bpo10+1) + override.conf on a Buster 10.7
Hi,
Before turning mad, any help would be welcome!
On a Buster system, I have created a
/etc/systemd/system/tomcat9.service.d/override.conf file to set a
value for ReadWritePaths.
Using a value such as /home or /src/backup/shared, tomcat9 is starting
fine and using /src/scratch/shared it does not (see the error messages
below).
Here are the commands to check each case:
systemctl daemon-reload
systemctl restart tomcat9
Here are the 'ls' outputs:
$ ls -ld /home /srv/backup /srv/backup/shared /srv/scratch /srv/scratch/shared
drwxr-xr-x 32 root root 4096 déc. 10 14:32 /home
drwxr-xr-x 9 root root 136 déc. 8 22:53 /srv/backup
drwxr-xr-x 13 ligmdb ligmusers 240 juin 28 16:51 /srv/backup/shared
drwxr-xr-x 5 root root 66 oct. 22 13:28 /srv/scratch
drwxr-xr-x 10 ligmdb ligmusers 173 juin 28 16:51 /srv/scratch/shared
Here are the 'mount' for those:
imgt2:/srv/data/home on /home type nfs4
(rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=193.50.6.90,local_lock=none,addr=193.50.6.94)
imgt2:/srv/data/backup2/scratch on /srv/scratch type nfs4
(rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=193.50.6.90,local_lock=none,addr=193.50.6.94)
imgt2:/srv/data/backup2 on /srv/backup type nfs4
(rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=193.50.6.90,local_lock=none,addr=193.50.6.94)
Thanks,
Patrice
déc. 10 21:20:02 omega systemd[1]: Reloading.
déc. 10 21:20:11 omega systemd[1]: Starting Apache Tomcat 9 Web
Application Server...
-- Subject: L'unité (unit) tomcat9.service a commencé à démarrer
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- L'unité (unit) tomcat9.service a commencé à démarrer.
déc. 10 21:20:11 omega systemd[39264]: tomcat9.service: Failed to set
up mount namespacing: No such file or directory
déc. 10 21:20:11 omega systemd[39264]: tomcat9.service: Failed at step
NAMESPACE spawning /usr/libexec/tomcat9/tomcat-update-policy.sh: No
such file or directory
-- Subject: Le processus /usr/libexec/tomcat9/tomcat-update-policy.sh
n'a pas pu être exécuté
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Le processus /usr/libexec/tomcat9/tomcat-update-policy.sh n'a pas
pu être exécuté, et a donc échoué.
--
-- Le code d'erreur renvoyé est ERRNO.
déc. 10 21:20:11 omega systemd[1]: tomcat9.service: Control process
exited, code=exited, status=226/NAMESPACE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStartPre= process belonging to unit tomcat9.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 226.
déc. 10 21:20:11 omega systemd[1]: tomcat9.service: Failed with result
'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit tomcat9.service has entered the 'failed' state with result
'exit-code'.
déc. 10 21:20:11 omega systemd[1]: Failed to start Apache Tomcat 9 Web
Application Server.
-- Subject: L'unité (unit) tomcat9.service a échoué
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- L'unité (unit) tomcat9.service a échoué, avec le résultat failed.
Reply to: