Hi Roland!

Roland Rosenfeld escribió:
Hi Daniel!

On Mon, 24 Sep 2007, Daniel Moreda wrote:

package: privoxy
Version: 3.0.6-2
Severity: normal

I'm using Privoxy 3.0.6 on a Debian 3.1 box (privoxy/stable uptodate
3.0.6-2).

I'm getting these errors constantly:

Sep 17 08:41:16 Privoxy(-1218339920) Error: could not resolve hostname
aaa.bbb.ccc

Sep 17 08:41:16 Privoxy(-1218339920) Error: write to: aaa.bbb.ccc
failed: Broken pipe

I've tried building from sources, but I'm still getting the same errors.
I've updated to "sid" too (privoxy/sid uptodate 3.0.6-3), but nothing
changes...

I saw this bug reported and closed as 335660, but I'm still getting this
error.

It sounds like a broken DNS server.  Did you check it?  Do all the
servers configured in /etc/resolv.conf respond correctly and quickly?
Do they work correct and without unusual delay, if you access
aaa.bbb.ccc directly?

Tschoeeee

        Roland




I'm sorry for the invonvenience. Of course, it was an ISP DNS problem. I was working a lot of time in this problem, and at last, they (ISP) recognize their problem.

I'm using Squid + Privoxy. When I found this problem I deactivated Privoxy, but the problem still occurred in Squid.

Now I'm waiting a few days and it seems to be stable (Squid). I will activate again Privoxy and I will close this bug.

Thank you very much!

Best Regards,

Daniel Moreda García





Reply via email to