package tomcat8 8.0.32-1ubuntu1.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tomcat8 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
failed to install tomcat 8
var/lib/dpkg/ error 1
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tomcat8 8.0.32-1ubuntu1.5
ProcVersionSign
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Feb 23 01:31:52 2018
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-12-30 (54 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitec
RelatedPackageV
dpkg 1.18.4ubuntu1.3
apt 1.2.25
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)
tags: | removed: need-duplicate-check |
Hi,
Thank you for taking the time to report this bug and helping to make Ubuntu better.
I tried to install as well but it worked fine for me.
We need to find what is special for your case.
From the log: d/tomcat8; bad; vendor preset: enabled) sysv-generator( 8) /etc/init. d/tomcat8 start [0;1;31m( code=exited, status=1/FAILURE) 8.service: Control process exit...=1 8.service: Unit entered failed ... 8.service: Failed with result '...'.
Job for tomcat8.service failed because the control process exited with error code. See "systemctl status tomcat8.service" and "journalctl -xe" for details.
invoke-rc.d: initscript tomcat8, action "start" failed.
[0;1;31m●[0m tomcat8.service - LSB: Start Tomcat.
Loaded: loaded (/etc/init.
Active: [0;1;31mfailed[0m (Result: exit-code) since Fri 2018-02-23 01:31:52 +06; 7ms ago
Docs: man:systemd-
Process: 4400 ExecStart=
Feb 23 01:31:47 mtr-tesla systemd[1]: Starting LSB: Start Tomcat....
Feb 23 01:31:47 mtr-tesla tomcat8[4400]: * Starting Tomcat servlet engine t...8
Feb 23 01:31:52 mtr-tesla tomcat8[4400]: ...fail!
Feb 23 01:31:52 mtr-tesla systemd[1]: [0;1;39mtomcat
Feb 23 01:31:52 mtr-tesla systemd[1]: [0;1;31mFailed to start LSB: Start Tomcat..
Feb 23 01:31:52 mtr-tesla systemd[1]: [0;1;39mtomcat
Feb 23 01:31:52 mtr-tesla systemd[1]: [0;1;39mtomcat
As well as:
Feb 23 01:31:52 hostname systemd[1]: Failed to start LSB: Start Tomcat..
Feb 23 01:31:52 hostname systemd[1]: tomcat8.service: Failed with result 'exit-code'.
Unfortunately nothing points to the actual issue.
I'd recommend to start with the statement already recommended by the error message.
$ journalctl -xe
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.
There isn't really enough information here for a developer to confirm this issue is a bug, or to begin working on it.
Further 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 sys...