Additionally we get sometimes this message: [Fri Jul 25 12:52:18.203975 2014] [proxy_http:error] [pid 13256:tid 47012293342976] (28)No space left on device: [client 172.31.0.224:20507] AH01110: error reading response
And there is plenty of room in all filesystems. So maybe this is misleading and we have some issues with shared memory too small ? (just my wild guess) Uli Von: Herbst, Ulrich Gesendet: Freitag, 25. Juli 2014 12:37 An: users@httpd.apache.org Betreff: [users@httpd] [proxy_http:error] [pid 13256:tid 47013272524544] (11)Resource temporarily unavailable: [client 172.31.0.142:21815] AH01110: error reading response Hi, we have apaches as reverse proxies for some tomcat and wso2-application servers. We get this error message on a high-load-webserver: [proxy_http:error] [pid 13256:tid 47013272524544] (11)Resource temporarily unavailable: [client 172.31.0.142:21815] AH01110: error reading response And we have no clue, which resource is unavailable and what to do against it. Apache-2.4.10 / apr-1.5.1 Ulimit of apache-user: core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 46666 max locked memory (kbytes, -l) 655360 max memory size (kbytes, -m) unlimited open files (-n) 655360 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) unlimited cpu time (seconds, -t) unlimited max user processes (-u) 655360 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited $ cat /proc/sys/kernel/threads-max 2065067 * So, I don't see any visible shortage of anything. Any ideas how to find the reason for this error ? Uli
