package apache2 2.4.12-2ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apache2 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I attach the crash file with a lot of (I hope) helpful information, due to apache
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: apache2 2.4.12-2ubuntu2.1
ProcVersionSign
Uname: Linux 4.2.0-42-generic x86_64
Apache2ConfdDir
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
Date: Tue Aug 2 10:10:57 2016
DuplicateSignature: package:
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2016-01-30 (184 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
RelatedPackageV
dpkg 1.18.2ubuntu5.1
apt 1.0.10.2ubuntu3
SourcePackage: apache2
Title: package apache2 2.4.12-2ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
error.log:
[Tue Aug 02 10:04:53.456735 2016] [mpm_prefork:
[Tue Aug 02 10:04:53.456756 2016] [core:notice] [pid 1654] AH00094: Command line: '/usr/sbin/apache2'
modified.
mtime.conffile.
tags: | removed: need-duplicate-check |
Thank you for taking the time to report this bug and helping to make Ubuntu better.
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.