I have seen these issues being reported across various minor versions now.
I guess the requested status and journal will match what we see in the logs.
e.g.
[0;1;31m●[0m tomcat7.service - LSB: Start Tomcat.
Loaded: loaded (/etc/init.d/tomcat7; generated; vendor preset: enabled)
Active: [0;1;31mfailed[0m (Result: exit-code) since to 2016-12-15 21:22:55
EET; 20ms ago
Docs: man:systemd-sysv-generator(8)
Process: 8317 ExecStart=/etc/init.d/tomcat7 start [0;1;31m(code=exited,
status=1/FAILURE)[0m
The question is "why".
Especially since many of us tried to recreate when triaging the bugs and it
just worked all the time. We have to identify what in all these setups is the
common issue that prevents the default tomcat to start/restart.
And that seems neither in journal nor in the service status.
I'm dupping a few more bug I think that are all the same case to get more
people onto this one and hopefully more data reported.
Maybe checking the tomcat log itself - which I think should be
/var/log/tomcat7/catalina.out in these cases - might help. Anybody able
to share his?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643182
Title:
package tomcat7 7.0.68-1ubuntu0.1 failed to install/upgrade: sub-
processo script post-installation instalado retornou estado de saída
de erro 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1643182/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
