Re: [privoxy-users] Forwarding failed

[Redback <bar...@gm...>]

G'day Fabian

Thanks for the info, with regards too the issue. The Maverick has a set 
limit on the file descriptors, you can see in the maxproc/maxfiles from 
below they are hard set, trying too change this, is very different too 
the old version of OSX. The problem for that site dailymail is 
repeatable with same outcome, I have only one tor running at any given 
time. I did increase max-client-connections too the max of 256 too no 
avail. So I did a test with and with tor and too my surprise, the issue 
disappears when tor is removed from privoxy setting but add tor to the 
config then the problem is back.
I'll take this up further with the Tor developers, tor might seem too be 
the cause of the issue.

Maverick:~ Redback$ launchctl limit
	cpu         unlimited      unlimited
	filesize    unlimited      unlimited
	data        unlimited      unlimited
	stack       8388608        67104768
	core        0              unlimited
	rss         unlimited      unlimited
	memlock     unlimited      unlimited
	maxproc     709            1064
	maxfiles    256            unlimited


Cheers
Redback

On 11/08/2014 9:29 pm, Fabian Keil wrote:
> Redback <bar...@gm...> wrote:
>
>> I have never see this error before and was wondering what can be done ?
>>
>> This is just a sample for this website, I don't seem too suffer from
>> other sites with these types of errors.I'm running this through a
>> Tor browser + privoxy with no issue as whole.
>
> The failure reason "Too many open files" suggests that Privoxy is
> hitting a per-process or global file descriptor limit enforced
> by the operating system.
>
> A single browser with a default configuration is unlikely to cause
> Privoxy itself to reach the per process limit, especially if you are
> using the max-client-connections default 128, which should be below
> the system's per-process limit:
> http://www.privoxy.org/user-manual/config.html#MAX-CLIENT-CONNECTIONS
>
> If you can reproduce the problem, you should check how many file descriptors
> are open at the time and which program opened them. On FreeBSD, one way to do
> this would be "procstat -f -a", your system should have an equivalent
> command.
>
>> P.S could this issue be a result of overwhelming the tor connection?
>
> That could be part of the problem, if for some reason there are more than
> one Tor process running that wouldn't help either.
>
> Fabian
>
>
>
> ------------------------------------------------------------------------------
>
>
>
> _______________________________________________
> Ijbswa-users mailing list
> Ijb...@li...
> https://lists.sourceforge.net/lists/listinfo/ijbswa-users
>