On 5/08/2012 4:07 p.m., Chen Bangzhong wrote:
We have 7 squids in use. 3 of them are squid 3.1.11, 4 of them are
3.1.12. The squids often crash.
The following is cited from the cache.log of squid 3.1.11
2012/07/28 11:28:54| Starting Squid Cache version 3.1.11 for
x86_64-koji-linux-gnu...
2012/07/28 13:08:03| Starting Squid Cache version 3.1.11 for
x86_64-koji-linux-gnu...
2012/07/28 14:47:05| Starting Squid Cache version 3.1.11 for
x86_64-koji-linux-gnu...
2012/07/29 13:37:34| Starting Squid Cache version 3.1.11 for
x86_64-koji-linux-gnu...
2012/07/29 15:19:55| Starting Squid Cache version 3.1.11 for
x86_64-koji-linux-gnu...
2012/07/29 16:26:18| Starting Squid Cache version 3.1.11 for
x86_64-koji-linux-gnu...
2012/07/30 13:07:23| Starting Squid Cache version 3.1.11 for
x86_64-koji-linux-gnu...
The active connections on squid are about 2000.
We have upgraded one 3.1.12 to 3.1.20, but the problem still exists.
2012/07/28 09:50:37| Starting Squid Cache version 3.1.20 for
x86_64-redhat-linux-gnu...
2012/07/28 09:50:54| Starting Squid Cache version 3.1.20 for
x86_64-redhat-linux-gnu...
2012/07/30 11:27:04| Starting Squid Cache version 3.1.20 for
x86_64-redhat-linux-gnu...
2012/07/30 11:27:11| Starting Squid Cache version 3.1.20 for
x86_64-redhat-linux-gnu...
How can I find out the reason ? It seems there is no clue in the cache.log
2012/07/31 11:23:55| WARNING: unparseable HTTP header field {: 211.137.119.10}
2012/07/31 11:23:55| WARNING: unparseable HTTP header field {: 211.137.119.10}
2012/07/31 11:26:46| WARNING: HTTP: Invalid Response: No object data
received for http://mydomain.com/ajax/book.getUserBookFans
Score.do AKA mydomain.com/ajax/book.getUserBookFansScore.do
2012/07/31 11:28:15| WARNING: HTTP: Invalid Response: No object data
received for http://mydomain.com/ajax/book.getUserBookFans
Score.do AKA mydomain.com/ajax/book.getUserBookFansScore.do
2012/07/31 11:43:10| NETDB state saved; 0 entries, 0 msec
2012/07/31 11:49:09| Starting Squid Cache version 3.1.20 for
x86_64-redhat-linux-gnu...
2012/07/31 11:49:09| Process ID 19635
For debugging a proxy during live traffic:
http://wiki.squid-cache.org/SquidFaq/BugReporting#Using_gdb_debugger_on_a_live_proxy_.28with_minimal_downtime.29
Please keep the 3.1.20 in use, and run this debugging on it. Any patches
you get as a fix will likely be3.1.20. designed fro use on 3.1.20.
You can also try the 3.2.0.19 package and set "debug_options 11,2" to
get a trace of the HTTP traffic going through and find out what those
"unparseable HTTP header field" are from.
Amos
