Bug#708416: Apache2 on 'older' kernels does not work in Debian stable
Package: apache2
Severity: grave
When upgrading to Debian stable (the one that is stable today, released
recently ;) and when one still has an older kernel (2.6.26-2-686,
linux-image-2.6.26-2-686 2.6.26-26lenny2) Apache fails to start
mysteriously with:
[Wed May 15 16:15:03 2013] [crit] (22)Invalid argument: alloc_listener:
failed to get a socket for (null)
Syntax error on line 9 of /etc/apache2/ports.conf:
Line 9 is simply the very good and old "Listen 80".
Please make Apache depend on a 'new' kernel. Apparently that is 2.6.30+
or better 3.2+ that provides a certain syscall that is being used.
By depending on it, one does not get to upgrade and then in being forced
to suddenly have to reboot a box which is just running fine:
Linux andromeda 2.6.26-2-686 #1 SMP Thu Sep 16 19:35:51 UTC 2010 i686
GNU/Linux
$ uptime
16:20:46 up 912 days, 3:38, 2 users, load average: 3.83, 2.59, 1.33
Oh yes, as you can see, it has load and is quite heavily used too even
though at the moment Apache is down, but all redirected with courtesy of
nginx. Will reboot tomorrow into a fresh 3.2 when people are on site to
peek at it.
For the record, this was the only issue that I had when upgrading that
box from the older stable to the current one, thus great works folks!
$ dpkg --list|grep apache
ii apache2 2.2.22-13
i386 Apache HTTP Server metapackage
ii apache2-mpm-prefork 2.2.22-13
i386 Apache HTTP Server - traditional non-threaded model
ii apache2-utils 2.2.22-13
i386 utility programs for webservers
ii apache2.2-bin 2.2.22-13
i386 Apache HTTP Server common binary files
ii apache2.2-common 2.2.22-13
i386 Apache HTTP Server common files
$ dpkg --list|grep linux-image
ii linux-image-2.6.26-2-686 2.6.26-26lenny2
i386 Linux 2.6.26 image on PPro/Celeron/PII/PIII/P4
ii linux-image-3.2.0-4-686-pae 3.2.41-2
i386 Linux 3.2 for modern PCs
ii linux-image-686 3.2+46
i386 Linux for modern PCs (dummy package)
ii linux-image-686-pae 3.2+46
i386 Linux for modern PCs (meta-package)
Yes, 3.2 is ready to be rebooted into, but rebooting is for wussies and
unstable things ;)
Greets,
Jeroen
Reply to: