Ubuntu
apache2 package

package apache2.2-common 2.2.14-5ubuntu8.2 failed to install/upgrade when using mpm-itk

Bug #621038 reported by Jonni on 2010-08-20

This bug report is a duplicate of: Bug #576255: can't install apache2.2-common (2.2.14-5ubuntu8). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	apache2 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: apache2

I'm using apache2-mpm-itk and apache failed to upgrade.

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: apache2.2-common 2.2.14-5ubuntu8.2
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
Architecture: amd64
Date: Fri Aug 20 10:10:31 2010
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
SourcePackage: apache2
Title: package apache2.2-common 2.2.14-5ubuntu8.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Tags:

Revision history for this message

Jonni (jonni-egarden) wrote on 2010-08-20:

AptOrdering.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.6 KiB, text/plain; charset="utf-8")
Df.txt Edit (602 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (166.7 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (63.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Clint Byrum (clint-fewbar) wrote on 2010-08-21:

Hi Jonni, thanks for filing this bug report and working with us to make Ubuntu better!

Based on the error messages in DpkgTerminalLog.txt

Setting up apache2.2-common (2.2.14-5ubuntu8.2) ...
ERROR: Module reqtimeout does not exist!
dpkg: error processing apache2.2-common (--configure):
subprocess installed post-installation script returned error exit status 1

I believe this is a duplicate of bug #576255

https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/576255

Marking as such. Please see the comments in that bug for information on how to correct the problem. If you feel that those solutions do not work, please return to this bug and add a comment.