Howdy. I'm getting a lot of lines like this:
Dec 6 23:31:11 slurm pound: (28401590) e500 response error read from 10.0.0.4:80/GET /about-us HTTP/1.1: Unknown error: 0 (0.003 secs) Dec 6 23:32:35 slurm pound: (284016a0) e500 response error read from 10.0.0.4:80/GET /sys/pic.php?w=45&h=45&crop&cache&img=../UserFiles/gallery/GetAttachment[2].jpg HTTP/1.1: Unknown error: 0 (0.006 secs) Dec 6 23:32:18 slurm pound: (28401f20) e500 response error read from 10.0.0.4:80/GET /wpad.dat HTTP/1.1: Unknown error: 0 (0.001 secs) Dec 6 23:40:51 slurm pound: (28402140) e500 response error read from 1.0.0.4:80/POST /oms.php HTTP/1.0: Unknown error: 0 (0.001 secs) Oddly, things work *most* of the time, This is an HTTP-only server (no HTTPS). The errors happen with both HTTP/1.0 and HTTP/1.1 requests. Server load is very low. Nothing shows up on the http server's log when the errors happen. It's happening on about 5% of all requests. It's occurring across multiple IPs that Pound listens on. There's only one back end, and it's *possible* there's a problem there, but I can't figure out how to narrow things down to confirm. I see from digging through list archives that similar errors come up relating to HTTPS, which as I said is not a factor here. A couple of years ago Robert suggesting increasing the Client timeout if this came up, but that's not a factor; the errors happen immediately when the HTTP request happens. Any idea what this is, or how I can diagnose it further? -- Paul Chvostek <[email protected]> -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
