* Solution possibility 1: As the issue is because of the difference of the user that `rsyslogd` runs as between Debian and Ubuntu. One solution would be running `rsyslogd` as root user same as in Debian. This automatically fix everything for the foreseeable future as the Debian `tomcat` package would work fine without any modifications.
* Solution possibility 2: modify /etc/logrotate.d/tomcat and replace `su tomcat adm` with `su syslog adm`. Update `/etc/syslog.d/tomcat9.conf` and replace `fileOwner="tomcat"` with `fileOwner="syslog"` This fix should be applied to every time `tomcat` is imported from upstream Debian.
Ideas on possible fixes:
In Ubuntu 20.04
* Perhaps the log directory fix can be backported, in addition this require solution 2 from below. If solution 1 is applied from below, there would be no need to backport the fix from the newer package. /bugs.launchpad .net/ubuntu/ +source/ tomcat9/ +bug/1861881/ comments/ 4
https:/
In Ubuntu 21.10/22.04
* Solution possibility 1: As the issue is because of the difference of the user that `rsyslogd` runs as between Debian and Ubuntu. One solution would be running `rsyslogd` as root user same as in Debian. This automatically fix everything for the foreseeable future as the Debian `tomcat` package would work fine without any modifications.
* Solution possibility 2: modify /etc/logrotate. d/tomcat and replace `su tomcat adm` with `su syslog adm`. Update `/etc/syslog. d/tomcat9. conf` and replace `fileOwner= "tomcat" ` with `fileOwner= "syslog" ` This fix should be applied to every time `tomcat` is imported from upstream Debian.
* Solution possibility 3: Any ideas?