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

Bug #1643182 reported by Francisco de Assis
44
This bug affects 7 people
Affects Status Importance Assigned to Milestone
tomcat7 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Creating config file /etc/default/tomcat7 with new version
Adicionando usuário de sistema 'tomcat7' (UID 122) ...
Adicionando novo usuário `tomcat7' (UID 122) ao grupo `tomcat7' ...
Sem criar diretório pessoal `/usr/share/tomcat7'.

Creating config file /etc/logrotate.d/tomcat7 with new version
Job for tomcat7.service failed because the control process exited with error code. See "systemctl status tomcat7.service" and "journalctl -xe" for details.
invoke-rc.d: initscript tomcat7, action "start" failed.
dpkg: erro ao processar o pacote tomcat7 (--configure):
 sub-processo script post-installation instalado retornou estado de saída de erro 1
A processar 'triggers' para systemd (229-4ubuntu12) ...
A processar 'triggers' para ureadahead (0.100.0-19) ...
Erros foram encontrados durante o processamento de:
 tomcat7
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tomcat7 7.0.68-1ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sat Nov 19 10:53:17 2016
ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 1
InstallationDate: Installed on 2016-11-19 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.2.15
SourcePackage: tomcat7
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
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Francisco de Assis (assismaxwell) wrote :
Revision history for this message
Joshua Powers (powersj) wrote :

From log:

See "systemctl status tomcat7.service" and "journalctl -xe" for details.

Revision history for this message
Joshua Powers (powersj) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Can you get the output from the commands above?

Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Changed in tomcat7 (Ubuntu):
status: New → Incomplete
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

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.
● tomcat7.service - LSB: Start Tomcat.
   Loaded: loaded (/etc/init.d/tomcat7; generated; vendor preset: enabled)
   Active: failed (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 (code=exited, status=1/FAILURE)

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?

Revision history for this message
Kari Pietarinen (kej-pietarinen) wrote :
Download full text (11.5 KiB)

Please see Tomcat7 log "/var/log/tomcat7/catalina.out":

root@Newton:/home/user# cat /var/log/tomcat7/catalina.out
Dec 16, 2016 2:58:44 PM org.apache.catalina.startup.ClassLoaderFactory validateFile
WARNING: Problem with directory [/usr/share/tomcat7/common/classes], exists: [false], isDirectory: [false], canRead: [false]
Dec 16, 2016 2:58:44 PM org.apache.catalina.startup.ClassLoaderFactory validateFile
WARNING: Problem with directory [/usr/share/tomcat7/common], exists: [false], isDirectory: [false], canRead: [false]
Dec 16, 2016 2:58:44 PM org.apache.catalina.startup.ClassLoaderFactory validateFile
WARNING: Problem with directory [/usr/share/tomcat7/server/classes], exists: [false], isDirectory: [false], canRead: [false]
Dec 16, 2016 2:58:44 PM org.apache.catalina.startup.ClassLoaderFactory validateFile
WARNING: Problem with directory [/usr/share/tomcat7/server], exists: [false], isDirectory: [false], canRead: [false]
Dec 16, 2016 2:58:44 PM org.apache.catalina.startup.ClassLoaderFactory validateFile
WARNING: Problem with directory [/usr/share/tomcat7/shared/classes], exists: [false], isDirectory: [false], canRead: [false]
Dec 16, 2016 2:58:44 PM org.apache.catalina.startup.ClassLoaderFactory validateFile
WARNING: Problem with directory [/usr/share/tomcat7/shared], exists: [false], isDirectory: [false], canRead: [false]
Dec 16, 2016 2:58:46 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server version: Apache Tomcat/7.0.72 (Ubuntu)
Dec 16, 2016 2:58:46 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server built: Sep 20 2016 11:28:54 UTC
Dec 16, 2016 2:58:46 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Server number: 7.0.72.0
Dec 16, 2016 2:58:46 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Name: Linux
Dec 16, 2016 2:58:46 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: OS Version: 4.8.0-30-generic
Dec 16, 2016 2:58:46 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Architecture: amd64
Dec 16, 2016 2:58:46 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Java Home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Dec 16, 2016 2:58:46 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Version: 1.8.0_111-8u111-b14-2ubuntu0.16.10.2-b14
Dec 16, 2016 2:58:46 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: JVM Vendor: Oracle Corporation
Dec 16, 2016 2:58:46 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_BASE: /var/lib/tomcat7
Dec 16, 2016 2:58:46 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: CATALINA_HOME: /usr/share/tomcat7
Dec 16, 2016 2:58:46 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.util.logging.config.file=/var/lib/tomcat7/conf/logging.properties
Dec 16, 2016 2:58:46 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
Dec 16, 2016 2:58:46 PM org.apache.catalina.startup.VersionLoggerListener log
INFO: Command line ...

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for tomcat7 (Ubuntu) because there has been no activity for 60 days.]

Changed in tomcat7 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.