I have additionally verified the issue in the current Ubuntu development branch (26.10 “stonking”) using the corresponding package version `9.4.58-2`.
The packaging change between `9.4.58-1` and `9.4.58-2` replaces the previous postinst-based directory ownership handling with systemd tmpfiles: ``` /usr/lib/tmpfiles.d/jetty9.conf d /var/log/jetty9 0750 jetty adm Z /var/log/jetty9 - jetty adm ``` The service unit still defines: ``` LogsDirectory=jetty9 User=jetty Group=jetty ``` According to `systemd.exec(5)`, `LogsDirectory=` ensures the directory is created and its ownership is adjusted to match the service `User=` and `Group=`. As a result, `/var/log/jetty9` becomes owned by `jetty:jetty`. At the same time, rsyslog runs as the `syslog` user and attempts to write: ``` /var/log/jetty9/jetty-console.log ``` This results in: ``` openat(...) = -1 EACCES (Permission denied) ``` The behavior is identical in Ubuntu 26.10 “stonking”, meaning the issue is not specific to the postinst-based implementation in older releases, but persists under the tmpfiles-based packaging as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2158988 Title: jetty9: LogsDirectory ownership prevents rsyslog from creating jetty- console.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jetty9/+bug/2158988/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
