Hello Roland,
first of all: today, after some more tests, I realized that I can't
myself reproduce this issue anymore. Privoxy starts fine at every boot
even with the default configuration. Something has been probably changed
in the meanwhile, even if I really can't figure out what.
I think you can close this bug if nobody else experiences the same issue.
Il 21/02/2009 13:12, Roland Rosenfeld ha scritto:
> Very strange. Maybe a wrong boot order, which first starts privoxy
> and after this it initializes the loopback interfaces with the
> localhost IP?
I'm quite sure the loopback interface is (and was) already up: ifupdown
has already been started in rcS.d, while privoxy starts as S20 in rc2.d
> 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?
yes, there is (and was!) the lo stanza, and it's set to auto.
> Could you send my the output of
> ls -l /etc/rc?.d/*ifupdown /etc/rc?.d/*privoxy
> [...]
m...@tuxie:~$ ls -l /etc/rc?.d/*ifupdown /etc/rc?.d/*privoxy
lrwxrwxrwx 1 root root 17 4 mar 2005 /etc/rc0.d/K20privoxy ->
../init.d/privoxy
lrwxrwxrwx 1 root root 17 4 mar 2005 /etc/rc1.d/K20privoxy ->
../init.d/privoxy
lrwxrwxrwx 1 root root 17 5 lug 2007 /etc/rc2.d/S20privoxy ->
../init.d/privoxy
lrwxrwxrwx 1 root root 17 5 lug 2007 /etc/rc3.d/S20privoxy ->
../init.d/privoxy
lrwxrwxrwx 1 root root 17 5 lug 2007 /etc/rc4.d/S20privoxy ->
../init.d/privoxy
lrwxrwxrwx 1 root root 17 5 lug 2007 /etc/rc5.d/S20privoxy ->
../init.d/privoxy
lrwxrwxrwx 1 root root 17 4 mar 2005 /etc/rc6.d/K20privoxy ->
../init.d/privoxy
lrwxrwxrwx 1 root root 18 3 mar 2005 /etc/rcS.d/S39ifupdown ->
../init.d/ifupdown
> [...]
> 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
> [...]
No, I have an identical hosts line as yours in /etc/nsswitch.conf
>> 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
Thank you
Mau
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
