On Thu, 19 Feb 2009, Mau wrote:
> Package: privoxy
> Version: 3.0.10-2
> Severity: important
> Privoxy fails to start at boot if listen-address is set at
> localhost:8118 or 127.0.0.1:8118; setting listen-address to
> [::1]:8118 allowed me to bypass this issue.
>
> The weird thing is that if I try to start Privoxy by its initscript
> after the boot (by su-ing to root), it will start fine also with the
> default configuration.
Very strange. Maybe a wrong boot order, which first starts privoxy
and after this it initializes the loopback interfaces with the
localhost IP?
Could you please have a look into your /etc/network/interfaces. How
is your loopback interface ("lo") configured? Is there a "auto lo"
entry in this file?
Could you send my the output of
ls -l /etc/rc?.d/*ifupdown /etc/rc?.d/*privoxy
or (if you are using file-rc) the output of
egrep 'privoxy|ifupdown' /etc/runlevel.conf
> In /var/log/privoxy/logfile I found these messages:
> [...]
> Feb 19 18:00:59.713 Privoxy(b7dd96b0) Fatal error: can't bind to
> localhost:8118: The hostname is not resolvable
> Feb 19 20:01:13.748 Privoxy(b7e816b0) Fatal error: can't bind to
> 127.0.0.1:8118: The hostname is not resolvable
> [...]
Hmmm, okay, a missing interface lo seems to give a different error:
Feb 21 13:07:52.147 Privoxy(7fe1d79346e0) Info: Listening on port 8118 on IP
address localhost
Feb 21 13:07:52.148 Privoxy(7fe1d79346e0) Fatal error: can't bind to
localhost:8118: because Cannot assign requested address
So maybe there's a problem with your host name resolving at all.
Could you please have a look at the "hosts" entry in your
/etc/nsswitch.conf? Mine says:
hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4
So it first looks into files and on dns after this. Maybe yours uses
a different order and tries to start privoxy at boot before a
nameserver is started, while /etc/hosts is ignored or tried later?
> My hosts file contents:
>
> 127.0.0.1 localhost
> 127.0.1.1 tuxie.local tuxie
Very strange. The hostname localhost should be resolvable via your
hosts file. 127.0.0.1 should not be resolved,
Tschoeeee
Roland
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
