[Expired for tomcat8 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: tomcat8 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There must be more output to that when not wrapped.
It seems it complains about a bad Restart setting and therefor it gets into
"Loaded: error (Reason: Invalid argument)"
Now the tomcat8 in Xenial doesn't even have a service file that could be broken.
It still uses a sysV init file and systemd
When I run
pramod@darkc0de:~$ systemctl tomcat8
Unknown operation tomcat8.
pramod@darkc0de:~$ systemctl status tomcat8
● tomcat8.service - Tomcat8 script that runs a shell script at boot
Loaded: error (Reason: Invalid argument)
Active: inactive (dead)
Jan 19 00:32:39 darkc0de
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with
the formerly working configuration.
But most of the time
Hi,
you reported this on tomcat8 8.0.32-1ubuntu1.4 on Xenial.
But on Xenial this is using not a systemd service but a generated from init
script.
Therefore the file /etc/systemd/system/tomcat8.service does not exist there.
But it does in your case, here from your error log:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740424
Title:
package tomcat8 8.0.32-1ubuntu1.4 failed to install/upgrade:
subprocess installed
