Dear Maintainer,
I just noticed that in the systemd logs of jetty12 there is:
/usr/libexec/jetty12/jetty-start.sh: 15: cd: can't cd to /var/lib/jetty
Log snippet:
Feb 27 07:57:35 ci-058-e8bb2f4d systemd[1]: Started jetty12.service - Jetty 12 Web Application Server.
Feb 27 07:57:35 ci-058-e8bb2f4d jetty12[3822]: /usr/libexec/jetty12/jetty-start.sh: 15: cd: can't cd to /var/lib/jetty
Feb 27 07:57:37 ci-058-e8bb2f4d jetty12[3825]: WARN : Use of both ${jetty.base}/start.d and ${jetty.base}/start.ini is deprecated
I guess the dir should be /var/lib/jetty12 instead of /var/lib/jetty. Maybe it has something to do with this line?
https://sources.debian.org/src/jetty12/12.0.32-2/debian/sysusers/jetty12.conf?hl=7#L7
BTW, I noticed that /usr/libexec/jetty12/jetty-start.sh references TOMCAT & CATALINA... Is this normal?
Fab
Le 27/02/2026 à 09:12, Fab Stz a écrit : I'm not sure to understand what is causing this error. The jetty user has the /var/lib/jetty directory as home, which is normal since the user is shared between different versions of Jetty. But the jetty-start.sh script has a cd command to the $JETTY_BASE directory, which is initialized to /var/lib/jetty12 in the service file, and may be overridden in /etc/default/jetty12 (I checked on my system, the variable is not overridden and I still get the error in the log). What mechanism sets JETTY_BASE to /var/lib/jetty instead of /var/lib/jetty12? This is fixed in jetty12/12.0.33-1 Emmanuel Bourg
Hi
026-03-13T16:42:17.210762Z 01O Mar 13 16:42:13 ci-072-e8f9dc27 systemd[1]: Started jetty12.service - Jetty 12 Web Application Server.
2026-03-13T16:42:17.210878Z 01O Mar 13 16:42:15 ci-072-e8f9dc27 jetty12[3510]: WARN : Use of both ${jetty.base}/start.d and ${jetty.base}/start.ini is deprecated
2026-03-13T16:42:17.210879Z 01O Mar 13 16:42:15 ci-072-e8f9dc27 jetty12[3510]: 2026-03-13 16:42:15.766:INFO :oe.jetty:main: Console stderr/stdout captured to|
It is likely that the fix of #1129201 fixed this is one as well. Because line 15 was the line that wanted to load tomcat...
Thanks! Maybe this bug is just a side effect of #1129201. Since 1129201 is now fixed, likely this one if fixed as well.
Regards
Fab