package tomcat7 7.0.68-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Bug #1752226 reported by sashank on 2018-02-28
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tomcat7 (Ubuntu)
Undecided
Unassigned

Bug Description

none

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tomcat7 7.0.68-1ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Feb 23 09:24:17 2018
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-09-21 (159 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt 1.2.24
SourcePackage: tomcat7
Title: package tomcat7 7.0.68-1ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

sashank (krishna-sashank) wrote :
tags: removed: need-duplicate-check

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

Your logs indicate that your service is unable to start/restart due to local configuration changes.
A fresh install starts just fine and the logs do not show a reason to assume it is different.

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.

Changed in tomcat7 (Ubuntu):
status: New → Incomplete
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  Edit
Everyone can see this information.

Other bug subscribers