I am running Privoxy on a box with Squid (SuSE 8.2).
Every so often for some unknown reason, Privoxy dies.
Squid is still running because I get an error message
from Squid that a URL is inaccessible. Restarting
Privoxy always fixes the problem. However, I would like
to find the cause of the problem. Just before Privoxy
dies, the system logfile says
"TCP connection to 10.1.1.61/8118 failed
last message repeated 9 times
detected DEAD parent 10.1.1.61/8118/7"
There is no error entry in the Privoxy logfile. Anyone
have any ideas what could be causing Privoxy to die? Is
there anywhere else that I can look to get a clue as to
what is going on? Any help will be greatly appreciated!
Logged In: NO
I've been looking for a bug report with a situation similar to what I see, and yours is it. :-)
My scenario is as follows:
I browse the web on my notebook (Windows 2000 SP4) and Opera (8.50 and 9.0 preview). Opera is configured to use Privoxy 3.0.3 on a FreeBSD box (FreeBSD 5.4). Privoxy then hands the request off to Squid (2.5 Stable3) on the same FreeBSD box. All my computers share a home network. with all the computers on the home network using Privoxy and squid on the FreeBSD box.
Normally I have no problems. However, when I browse Yahoo message boards, Privoxy will eventually become unresponsive. Stopping and starting Privoxy will get things going again.
The only sites where I see this problem are Yahoo sites. I have not seen the problem anywhere else.
I don't see the TCP connection message in my system log file, though. In fact, the log files show nothing odd.
Logged In: YES
user_id=875547
Please try Privoxy 3.0.5 beta to see if the problem
still exists.
Logged In: YES
user_id=1312539
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).