can't install apache2.2-common (2.2.14-5ubuntu8)

Bug #576255 reported by serggt1
76
This bug affects 13 people
Affects Status Importance Assigned to Milestone
apache2 (Ubuntu)
Low
Unassigned

Bug Description

Binary package hint: apache2.2-common

Ubuntu 10.04 LTS

Package apache2.2-common (2.2.14-5ubuntu8)

When installing apache by typing
"sudo aptitude install apache2"

it outputs when configuring apache2.2-common:
"...
ERROR: Module reqtimeout does not exist!
..."

Revision history for this message
Chuck Short (zulcss) wrote :

Can you please make sure that you have apache2-2-bin installed?

chuck

Changed in apache2 (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
serggt1 (serggt1) wrote :

apache2-2-bin installs successfully, but when installing apache2.2-common I got the same error. I did clean apt cache and aptitude downloaded the latest package files.

I've updated from Kubuntu 9.10 i386, php did not work, tried to reinstall, purge and install again all apache and php packages. Apache doesn't want to be installed.

Revision history for this message
serggt1 (serggt1) wrote :

Also i've removed /etc/apache2 directory

Revision history for this message
Graham Perry (misc-noisp) wrote :

I get this too. Also removed the /etc/apache2 directory as I wanted a clean install. Fails to configure anything after the reqtimeout module fails.

Tried purging with apt-get, but that fails too. Tried purging with aptitude which seems to work, but it still fails to reinstall.

Revision history for this message
Graham Perry (misc-noisp) wrote :

Replaced the etc/apache2 folder from a backup and renamed the conf and site files to .bak and the installation got past the module dependency, but failed to generate new conf files.

Surely this isn't how it should install? The package should come with all necessary modules and generate all necessary config files on install, and not rely on pre-existing files.

Revision history for this message
serggt1 (serggt1) wrote :

The problem was solved by running "sudo dpkg --purge --force-remove-reinstreq apache2.2-common" which completelly deletes all package configuration files and removing /var/www directory. After apache2 installed successfully.

May be removing /var/www directory is not necessary, i've done this just in case.

Revision history for this message
Ganton (ganton) wrote :

> was solved by running "sudo dpkg --purge --force-remove-reinstreq apache2.2-common" which completelly deletes all package configuration files
Thank you! This "ERROR: Module reqtimeout does not exist!" problem affected me, too. You have saved us from headaches and system reinstallations, God bless you :-)

> May be removing /var/www directory is not necessary
If this information can be useful: this was not necessary for me.

Revision history for this message
Adam Conrad (adconrad) wrote :

A package failing to find conffiles after you delete them is exactly how they're meant to behave. If you delete a dpkg conffile, "deleted" is considered a valid "user requested state", and they won't be replaced unless you reinstall with --force-confmiss.

This isn't apache-specific, though it seems that apache users seem to be one of the larger groups of people who think that deleting conffiles will improve their lives somehow. Not really sure how to curb that, but not with bugs in apache.

Changed in apache2 (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
tropa (iskritsky) wrote :

After "sudo dpkg --purge --force-remove-reinstreq apache2.2-common" run "sudo apt-get -f install" as you see it, without package name. Synaptic will fix the dependencies problems and automatically install and run apache2. Enjoy )

Revision history for this message
yxb_1024@sina.com (yxb-1024) wrote :

Yes,Apache2 want not to install and the show me the error "Module reqtimeout does not exist! "
            I removed Apache2 and Cleaned the Directory before. O, I just clear the packge with the support, apt-cache depends apache2
          So,I can not to install the apache2 again. I just want to know the method for the error.

Revision history for this message
pamindic (pam-indicia) wrote :

Adam Conrad - "This isn't apache-specific, though it seems that apache users seem to be one of the larger groups of people who think that deleting conffiles will improve their lives somehow. Not really sure how to curb that, but not with bugs in apache."

You won't curb it by making sarky comments. If it works for a handful of congnoscenti like your goodself, but fails for the great unwashed, then it probably isn't very usefully organised. No-one's asking for 'bugs in apache'. It seems to me reasonable enough to be able to dump the config files and expect a reinstall to reload them load them with the binaries.

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

This sounds like something to bring forward as a bug in dpkg... in fact, I've gone ahead and filed it as a feature request:

https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/622885

There may not be an obvious way to do this, so I think we're just going to have to deal with the occasional confused user filing bug reports like this until there's a better solution.

Revision history for this message
Adam Conrad (adconrad) wrote :

Having conffiles be deletable is a feature. Yes, it would be nice if dpkg was move verbose about it (perhaps listing every deleted conffile with a "not reinstating deleted conffile /path/to/file" during installation?), but changing the behaviour to silently restore deleted files breaks some pretty fundamental assumptions about dpkg conffile handling.

"Not there" is a valid user-defined state, just as "changed" is, and you certainly wouldn't want us overwriting changed files randomly.

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Agreed on all points.

I suggest you read the dpkg bug report. To summarize, I'm suggesting that conffile changes be listed and the user offered a chance to resolve them as if the upstream confffiles were changed in the new release, but only when maintainer scripts fail.

This is purely a selfish interest, as I see a lot of bug reports to handle related to maintainer scripts failing because the service is somewhat broken (possibly unbeknownst to the user) at upgrade time.

Revision history for this message
Thomas Antepoth (ta-ubuntu-antepoth) wrote :

Patched my /var/lib/dpkg/info/apache2.2-common.postinst at line 77 in this way:

# Note, this line catches new installs as well as upgrades
if dpkg --compare-versions "$2" lt 2.2.15-1~0; then
        a2enmod -q reqtimeout
fi

to:
# Note, this line catches new installs as well as upgrades
if dpkg --compare-versions "$2" lt 2.2.15-1~0; then
        echo "a2enmod -q reqtimeout"
fi

After that I ran:

apt-get install
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut
Status-Informationen einlesen... Fertig
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
3 nicht vollständig installiert oder entfernt.
Nach dieser Operation werden 0B Plattenplatz zusätzlich benutzt.
Richte apache2.2-common ein (2.2.14-5ubuntu8.2) ...
a2enmod -q reqtimeout

Richte apache2-mpm-prefork ein (2.2.14-5ubuntu8.2) ...
 * Starting web server apache2 apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1 for ServerName
[Tue Aug 24 06:12:39 2010] [warn] NameVirtualHost *:80 has no VirtualHosts
httpd (pid 2199) already running
                                                                                                                                                                                                   [ OK ]

Richte apache2 ein (2.2.14-5ubuntu8.2) ...

and was up and running again.

Revision history for this message
Pablo Cocko (pcocko) wrote :

It worked for me. But it didn't remove theses directories:

dpkg: aviso: al eliminar apache2.2-common, el directorio «/var/www» no estaba vacío. No ha sido eliminado.
dpkg: aviso: al eliminar apache2.2-common, el directorio «/var/log/apache2» no estaba vacío. No ha sido eliminado.

Revision history for this message
HonoredMule (honoredmule) wrote :

Adam Conrad - "This isn't apache-specific, though it seems that apache users seem to be one of the larger groups of people who think that deleting conffiles will improve their lives somehow. Not really sure how to curb that, but not with bugs in apache."

I didn't delete any config files, yet I also have this problem. And if apache upgrades break without faulty user intervertion, then it is most definitely a packaging bug. Locate reqtimeout returns only "/usr/lib/apache2/modules/mod_reqtimeout.so" but there has never been any matching set of .conf and .load files in /etc/apache2/mods-available, as verified by perusing full system backups dating back to 2010-07-31. The problem just occurred for me a couple weeks ago after no modification to the system--other than upgrades--since install at 2010-04-13. If I had to make a guess, it would be that dpkg is currently expecting a file that it didn't previously provide and then assuming its absence implicates manual deletion, which is obviously a problem for anyone who expects server upgrades between untampered states to be reliable. Shouldn't they?

I'm not convinced that manual deletion should be allowed to interfere either. Non-stock configuration (particularly living in /etc) is sysadmin domain and none of dpkg's concern unless --purge --reinstall is explicitly requested. If user action has broken something, fine. Let user deal with it instead of taking down a service that might have been working anyway (as it was). All dpkg should be doing is reporting /changes/ in requirements, in which case it should be supplying them.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers