package apache2 2.4.7-1ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed)

Bug #1371935 reported by Oscar Tiderman
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

upgraded from 12.04

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: apache2 2.4.7-1ubuntu4.1
ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60
Uname: Linux 3.2.0-67-generic x86_64
Apache2ConfdDirListing: ['munin', 'phpmyadmin.conf']
Apache2Modules:
 Error: command ['/usr/sbin/apachectl', '-D DUMP_MODULES'] failed with exit code 1: [Sat Sep 20 15:32:19.651952 2014] [so:warn] [pid 28186] AH01574: module security2_module is already loaded, skipping
 apache2: Syntax error on line 237 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/sites-enabled/000-default: No such file or directory
 Action '-D DUMP_MODULES' failed.
 The Apache error log may have more information.
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
Date: Sat Sep 20 15:29:02 2014
DuplicateSignature: package:apache2:2.4.7-1ubuntu4.1:subprocess installed post-installation script was killed by signal (Killed)
ErrorMessage: subprocess installed post-installation script was killed by signal (Killed)
InstallationDate: Installed on 2014-01-30 (233 days ago)
InstallationMedia:

SourcePackage: apache2
Title: package apache2 2.4.7-1ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Killed)
UpgradeStatus: Upgraded to trusty on 2014-09-20 (0 days ago)
modified.conffile..etc.apache2.apache2.conf: [modified]
modified.conffile..etc.apache2.conf.available.security.conf: [modified]
modified.conffile..etc.apache2.ports.conf: [modified]
mtime.conffile..etc.apache2.apache2.conf: 2014-02-03T09:15:28.195841
mtime.conffile..etc.apache2.conf.available.security.conf: 2014-02-11T06:26:10.673500
mtime.conffile..etc.apache2.ports.conf: 2014-04-23T20:19:34.454777

Revision history for this message
Oscar Tiderman (oscar-tiderman) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi,
I found various statements like this in the logs:

The Apache error log may have more information.
apache2_reload: Your configuration is broken. Not reloading Apache 2

That indicates some kind of custom config might be in place that isn't compatible with the new release.
Please check your logs as indicated.
Often the README files provided by the package help on common on-upgrade-changes that one has to be aware of.

Further down in other attached logs I found:
[Sat Sep 20 15:14:57 2014] [notice] Apache/2.2.22 (Ubuntu) DAV/2 mod_ssl/2.2.22 OpenSSL/1.0.1 mod_fcgid/2.3.6 mod_perl/2.0.5 Perl/v5.14.2 configured -- resuming normal operations
Failed loading /usr/lib/php5/20090626/xcache.so: /usr/lib/php5/20090626/xcache.so: cannot open shared object file: No such file or directory
[Sat Sep 20 15:16:00 2014] [notice] caught SIGTERM, shutting down

So it might be a php5-xcache setup issue on your system.
I checked what I got on a 12.04 -> 14.04 upgrade and I ended up with
php5-xcache 3.1.0-2
/usr/lib/php5/20121212/xcache.so

The one your log is referring to is still the precise version.

I hope this might help you to find your setup issue, it is hard to do more remotely.
Please come back and reopen the bug if it still applies - in that case please add all the info you found while trying to resolve the suggested configuration issue.

Changed in apache2 (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in apache2 (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.