Details
-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
None
-
High
Description
The problem is the following:
+++
[Wed Oct 27 11:33:30 2010] [error] ajp_cping_cpong: apr_socket_recv failed
[Wed Oct 27 11:33:30 2010] [debug] mod_proxy_cluster.c(1213): ajp_cping_cpong: Done
[Wed Oct 27 11:33:30 2010] [debug] proxy_util.c(2029): proxy: ajp: has released connection for (127.0.0.1)
+++
and later:
+++
[Wed Oct 27 11:33:55 2010] [debug] mod_proxy_ajp.c(265): proxy: APR_BUCKET_IS_EOS
[Wed Oct 27 11:33:55 2010] [debug] mod_proxy_ajp.c(270): proxy: data to read (max 8186 at 4)
[Wed Oct 27 11:33:55 2010] [debug] mod_proxy_ajp.c(285): proxy: got 0 bytes of data
[Wed Oct 27 11:33:55 2010] [debug] ajp_header.c(687): ajp_read_header: ajp_ilink_received 09
[Wed Oct 27 11:33:55 2010] [debug] ajp_header.c(697): ajp_parse_type: got 09
[Wed Oct 27 11:33:55 2010] [debug] mod_proxy_ajp.c(543): proxy: Processing of request failed backend: 1, output: 0
[Wed Oct 27 11:33:55 2010] [error] proxy: dialog to 127.0.0.1:8009 (127.0.0.1) failed
+++
And the node is marked broken for a while, until:
+++
Wed Oct 27 11:35:00 2010] [debug] proxy_util.c(1955): proxy: ajp: worker for (127.0.0.1) has been marked for retry
+++
The STATUS should be able to restore the node and may be the answer 09 should not be taken as broken node error: it is just a broken socket error.
