package tomcat8 8.0.32-1ubuntu1.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Birender Singh]

tomcat re-installation error

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tomcat8 8.0.32-1ubuntu1.5
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
AptOrdering:
 tomcat8: Install
 authbind: Install
 tomcat8: Configure
 authbind: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Sun Jan 28 19:48:13 2018
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2018-01-19 (8 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt 1.2.24
SourcePackage: tomcat8
Title: package tomcat8 8.0.32-1ubuntu1.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[Christian Ehrhardt  (paelzer)]

All I can find in your logs is:
  tomcat8.service: Failed with result 'exit-code'.

Most of the times these errors are due to modified local configuration that makes the server fail to 8re)start.

For tomcat I'd recommend to check catalina.out (the log file) what error actually happens and then fix up your config accordingly.

[Christian Ehrhardt  (paelzer)]

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 what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state.

Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart.
Therefore the update of that package has to consider itself incomplete.

Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting the service will work.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

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

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. 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.

[Launchpad Janitor (janitor)]

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