Menu
▾
▴
#563 privoxy crashes
Version : privoxy-suse-3.0.3-1 (own rebuild from src.rpm)
OS : SuSE Linux 9.0 (i586)
Browser : Mozilla 1.7.5. @ Windows XP SP1
System : Privoxy lies in my own intranet (192.168.*)
with its own IP and goes to the internet straight
without any outside proxies. Any machine in intranet is
allowed to make connection.
Today I noticed unexplained privoxy "crashing" with
these announcements:
Feb 19 01:54:44 Privoxy(-1221476350) Info: exiting by
signal 6 .. bye
Feb 19 02:04:36 Privoxy(2015234) Info: exiting by
signal 6 .. bye
After a little study I found the reason from this website:
http://www.loria.fr/~zimmerma/records/ecmnet.html
especially that line:
"9 July 2004: ECMNet master server now at 62.236.152.54
port 8194, check its status here."
It connect other website with port 8194 (actually link
goes to the port 8195 :)
After privoxy tries to make connection it will fail and
"falls" with those log-markings.
Because I haven´t got any other proxies I can´t control
which destination ports are allowed.
Toni Ahokas, Finland
( trahokas@st.jyu.fi )
Logged In: YES
user_id=1103981
pobably a http header parsing problem:
Feb 20 11:23:49 angelika squid[3234]: ctx: enter level 0: 'http://62.236.152.54:8195/query.cgi'
Feb 20 11:23:49 angelika squid[3234]: httpProcessReplyHeader: Too large reply header
Feb 20 11:23:49 angelika squid[3234]: ctx: exit level 0
Feb 20 11:23:49 angelika squid[3234]: WARNING: http.c:678: HTTP header too large
Logged In: YES
user_id=875547
Can you reproduce the problem with Privoxy 3.0.5 beta?
The link works for me, but the content probably has
changed.
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).