use-ipv6.pl has hardcoded port 80

[fh]

Binary package hint: lighttpd

I am running lighttpd on port 82 behind varnish on port 80. After the last update of the lighttpd package, lighttpd refuses to start with 2010-04-07 10:35:33: (network.c.345) can't bind to port: :: 80 Address already in use
which puzzled me because no configuration script whatsoever uses port 80.

After some digging and a lighttpd -p -f /etc/lighttpd/lighttpd.conf|grep 80 I figured that the use-ipv6.pl apparently adds $SERVER["socket"] == "[::]:80" { } to the config, which of course then causes lighttpd to fail the start because port 80 is already in use.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: lighttpd 1.4.26-1.1ubuntu3 [modified: usr/share/lighttpd/use-ipv6.pl]
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic-pae
Uname: Linux 2.6.32-16-generic-pae i686
Architecture: i386
Date: Wed Apr 7 10:43:14 2010
ProcEnviron: SHELL=/bin/bash
SourcePackage: lighttpd

[matt (bussonniermatthias)]

find references in debian bug tracker here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572279

[andy4us (andy-prestonmedina)]

Since I don't use IPV6 at all, I just commented out the include_shell line in my lighttpd.conf file for the use-ipv6.pl file
which seems to work fine.

[Stefan Bühler (stbuehler)]

And if you want to use ipv6 later just add the correct socket conditional yourself.
There is no good way for the use-ipv6.pl script to guess your port.

[fh (fholzhauer)]

Just as follow up: This &"§$ bug just stopped lighttpd once again after doing a version update to 1.4.26-1.1ubuntu3.1. Apparently, the bug still exists and overwrote my modified use-ipv6.pl.
Hence I would now strongly recommend the solution by andy4us to remove the use-ipv6.pl file from lighttpd.conf, not to patch in the file as I stated above.