Hi,
On Tue, Apr 10, 2012 at 1:23 PM, Roland Rosenfeld >> And one more
think: process use lots of ram. It's grow up to 3580mb
>> and more. But process never hit 5G ram before fail.
>
> Uh, that's really much. Mine takes 200MB and I think this is much
> (after running for some weeks). Maybe you configured some special
> filters? These could trigger memory leaks...
My filters:
bozy@teredo:/etc/privoxy$ md5sum *filter*
36e1e07ba3fa3fbbb978332a8c797ab2 default.filter
bozy@teredo:/etc/privoxy$
My config:
bozy@teredo:/etc/privoxy$ egrep -v '^#' config
user-manual /usr/share/doc/privoxy/user-manual
confdir /etc/privoxy
logdir /var/log/privoxy
actionsfile match-all.action # Actions that are applied to all sites
and maybe overruled later on.
actionsfile default.action # Main actions file
actionsfile user.action # User customizations
filterfile default.filter
logfile logfile
debug 1 # Log the destination for each request Privoxy let through.
debug 1024 # Log the destination for requests Privoxy didn't let
through, and the reason why.
debug 4096 # Startup banner and warnings
debug 8192 # Non-fatal errors
listen-address localhost:8118
listen-address 1.2.3.4:8118
toggle 0
enable-remote-toggle 0
enable-remote-http-toggle 0
enable-edit-actions 0
enforce-blocks 0
buffer-limit 4096
forward-socks5 / 127.0.0.1:9050 .
forwarded-connect-retries 0
accept-intercepted-requests 0
allow-cgi-request-crunching 0
split-large-forms 0
keep-alive-timeout 5
socket-timeout 300
handle-as-empty-doc-returns-ok 1
forward localhost/ .
forward domain.eu/ .
forward domain.pl/ .
forward 127.0.0.1/ .
bozy@teredo:/etc/privoxy$
-------------
>
>> >> Is this problem reproducible?
>> >
>> > yes.
>> > root@teredo:~# egrep 'privoxy' /var/log/all.log|egrep '^Apr 10' |wc -l
>> > 27
>
> Do you mean, that it crashed 27 times only today and grow up to the
> above size in between?
27 crash from 00:01.
> Do you use it on a one user system or is this
> a proxy for several users (only to understand how much load it has to
> handle)?
this proxy is used for tor network. Im not sure how many clients but
it's look like few bilion of connections per month.
>
> BTW: Did the problem start today or with some update or do you notice
> it for a longer time?
Problem start from beginning (6mc) but i was focused on something different.
>> > define 'special' url? I find in logs connection to site + google
>> > analytics + some adv. sites + some gifs, java-scripts etc. nothink
>> > special.
>
> I could imagine that it segfaults every time you enter
> http://www.foo.bar/baz or go to a special site or something like this.
ah... it's be hard. I use workaround for rerun privoxy after crash:
while [ true ]; do ./privoxy ... ; done
>
>> >> Without more input I can only reply that privoxy never run into a
>> >> segfault on my x86_64 squeeze box...
>> >
>> > just tell me what you want and i will find it and give you what i get.
>
> I till tap around in the dark and hope to find an idea, what goes
> wrong on your system...
i can send You core file :-)
>
> Tschoeeee
>
> Roland
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
