Hallo Roland!
> Strange. I use the same configuration on my home system, but never
> got this error message. Neither with 3.0.12 nor with 3.0.13.
I downgraded to 3.0.12. This version works fine.
After a subsequent upgrade to 3.0.13 I could reproduce the same error:
/var/log/privoxy/logfile:
Fatal error: can't bind to INADDR_ANY:8118: The hostname is not resolvable
> Maybe its a sid issue (I personally usually use lenny).
I use unstable but it is only a problem with 3.0.13 as mentioned above.
> do you use some special architecture (I only use i386 and amd64)?
i386
> Where does this "INADDR_ANY" come from? Did you enter it to the
> config file or is it only the output in the log?
It is only in the log file.
> The correct configuration to listen on all interfaces is
> listen-address :8118
As I wrote in the subject :-)
> Could you please give me more information, how to reproduce this
> problem?
I did further testings and noticed following facts:
1. "listen-address 127.0.0.1:8118" works EVERY time
2. "listen-address :8118" FIRST startup attempt after boot: fails
3. "listen-address :8118" second and further startups work fine
4. "listen-address localhost:8118" FIRST startup attempt after boot: fails
5. "listen-address localhost:8118" second and further startups work fine
Output of test case 2 in /var/log/privoxy/logfile:
Fatal error: can't bind to INADDR_ANY:8118: The hostname is not resolvable
Output of test case 4 in /var/log/privoxy/logfile:
Fatal error: can't bind to localhost:8118: The hostname is not resolvable
It seems that there is a problem in the name resolution
("The hostname is not resolvable").
Gruß
Markus
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
