Your message dated Sun, 15 Feb 2009 12:56:33 +0100
with message-id <[email protected]>
and subject line Re: Bug#443808: Error: could not resolve & broken pipe (closed
bug 335660)
has caused the Debian Bug report #443808,
regarding Error: could not resolve & broken pipe (closed bug 335660)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
443808: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443808
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
System Information:
-------------------
Linux 2.6.17.11 #1 Mon Feb 19 09:38:09 CET 2007 i686 GNU/Linux
privoxy: 3.0.6-3
libc6: 2.6.1-5
libpcre3: 6.7-1
logrotate: 3.7.1-3
adduser: 3.102
---------------------------------
TIA.
--- End Message ---
--- Begin Message ---
> 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.
So I close this bug report now.
Tschoeeee
Roland
--- End Message ---
