Olaf van der Spek wrote:
Lighttpd actually sets v6only = 1 itself (AFAIK) now.
Hmm, right (r2758: bind to IPV6-only if ipv6 address was specified).
Could you try with a clean conf and post a strace of the error?
$ ltrace lighttpd -f /etc/lighttpd/lighttpd.conf
...
memcpy(0x081319b0, :80,
notfound 564556 lighttpd/1.4.25-2
fixed 564556 lighttpd/1.4.25-2
close 564556
quit
Olaf van der Spek wrote:
Eh, netstat -nlp | grep 80?
Sigh. Sorry to waste your time.
# killall apache2
# dpkg --configure -a
Setting up lighttpd (1.4.28-1) ...
Starting web server: lighttpd.
# echo $?
0
I had
Olaf van der Spek wrote:
Eh, netstat -nlp | grep 80?
Forgot to say: thank you! (for the fix and the debugging help)
You have been very patient.
*shuffles off to sleep*
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Thu, Sep 2, 2010 at 2:13 PM, Jonathan Nieder jrnie...@gmail.com wrote:
# killall apache2
# dpkg --configure -a
Setting up lighttpd (1.4.28-1) ...
Starting web server: lighttpd.
# echo $?
0
I had uninstalled but not purged apache and clearly I do not know
how to use netstat. :(
You're
Olaf van der Spek wrote:
I guess uninstalling didn't succeed either.
Right, I removed the apache2 package but not the daemon (apache2-mpm-worker)
itself.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Wed, Sep 1, 2010 at 3:29 AM, Jonathan Nieder jrnie...@gmail.com wrote:
net.ipv6.bindv6only = 1
Wait, wasn't that changed back in netbase? Well, yes, for _new_
installs, but this is a conffile so it keeps the existing value
for existing installations.
That sucks, IMO it should've been
Hi,
not sure if it is relevant at all anymore but I hit this too in the
following environment:
* debian stable
* custom kernel with CONFIG_IPV6=y
* debian unstable chroot for testing unstable packages
Obviously /proc/sys/net/ipv6/bindv6only is false since it is not set
by the debian stable
2010/5/23 Stefan Bühler stbueh...@lighttpd.net:
I think i already wrote this: I don't think it is a good idea to
automatically enable ipv6: it neither works with the wrong bindv6only
nor with server.port != 80.
Dropping the script would fix these issues; providing a simple example line
in
On 05/23/2010 11:26 AM, Olaf van der Spek wrote:
http://wiki.debian.org/ReleaseGoals/FullIPv6Support
Debian's goal is to have out-of-the-box IPv6 support in all daemons.
Not enabling IPv6 is not a solution.
Olaf
I think there is a difference between supporting something and enabling
it by
2010/5/23 Stefan Bühler stbueh...@lighttpd.net:
On 05/23/2010 11:26 AM, Olaf van der Spek wrote:
http://wiki.debian.org/ReleaseGoals/FullIPv6Support
Debian's goal is to have out-of-the-box IPv6 support in all daemons.
Not enabling IPv6 is not a solution.
Olaf
I think there is a
On Sat, May 22, 2010 at 9:51 PM, Jonathan Nieder jrnie...@gmail.com wrote:
Olaf van der Spek wrote:
I think the problem was that I compiled Linux with CONFIG_IPV6=m.
So this is no longer a problem?
I’m using a Debian kernel now; I’ll try rebuilding a kernel with ipv6
disabled and get back
Olaf van der Spek wrote:
I thought the problem was caused by your kernel option.
bindv6only is now enabled by default in netbase AFAIK.
Maybe it could be considered a kernel bug: if ipv6 support is disabled
(because built as a module) at the time the netbase init script runs,
then it cannot
On Sat, May 22, 2010 at 10:09 PM, Jonathan Nieder jrnie...@gmail.com wrote:
Olaf van der Spek wrote:
I thought the problem was caused by your kernel option.
bindv6only is now enabled by default in netbase AFAIK.
Maybe it could be considered a kernel bug: if ipv6 support is disabled
(because
13 matches
Mail list logo
