Landy Landy wrote:
Hello.
Once again my 3.0.STABLE20 server on Lenny has stalled. This is the error:
2010/01/31 13:33:20| WARNING: redirector #2 (FD 808) exited
2010/01/31 13:33:20| Too few redirector processes are running
2010/01/31 13:33:20| Starting new helpers
2010/01/31 13:33:20| helperOpenServers: Starting 6/10 'python' processes
2010/01/31 13:33:21| WARNING: redirector #3 (FD 809) exited
2010/01/31 13:33:37| WARNING: redirector #4 (FD 810) exited
There is something wrong with your redirector helpers.
You need to find out what that is and stop it from happening.
2010/01/31 13:35:18| clientParseRequestMethod: Unsupported method attempted by 172.16.100.56: This is not a bug. see squid.conf extension_methods
2010/01/31 13:35:18| clientParseRequestMethod: Unsupported method in request '<_____g_g?^=__ k____w@_M_L_Q_m___Da_c7y________X_______3h_______"__~_;P__P_&'_
\________!hn\_O_____X'
2010/01/31 13:35:18| clientProcessRequest: Invalid Request
The machine at 172.16.100.56 is broken and pushing garbage into Squid
instead of HTTP.
This is not fatal for you or Squid, but may cause the person who uses
that machine to have a very bad web experience.
2010/01/31 13:38:55| client_side.cc(2843) WARNING! Your cache is running out of filedescriptors
Debian default is 1024 FD available per process. This seems not to be
enough for your Squid. alter the /etc/default/squid config file to set a
new limit.
If that still fails, you may need to rebuild the package with ulimit
setting FD to something high before ./configure is run.
...
2010/01/31 13:45:56| clientNatLookup: NF getsockopt(SO_ORIGINAL_DST) failed: (2) No such file or directory
NAT failed to locate the real origin address for a client.
Perhapse the port used for NAT interception 'transparent-proxy' requests
is receiving direct forward-proxy requests.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE7 or 3.0.STABLE21
Current Beta Squid 3.1.0.15
