Greetings,
We are currently doing a test deployment of M/Monit 3.4.1 and Monit 5.13. In what conditions would "HTTP 408 Request Timeout” appear in the M/Monit log? For example: 2015-04-03 13:21:04 [client 10.0.0.222] HTTP 408 Request Timeout 2015-04-03 13:21:09 [client 10.0.0.222] HTTP 408 Request Timeout 2015-04-03 13:21:09 [client 10.0.2.33] HTTP 408 Request Timeout 2015-04-03 13:21:14 [client 10.0.0.222] HTTP 408 Request Timeout 2015-04-03 13:21:19 [client 10.0.2.33] HTTP 408 Request Timeout 2015-04-03 13:21:19 [client 10.0.2.33] HTTP 408 Request Timeout 2015-04-03 13:21:24 [client 10.0.0.222] HTTP 408 Request Timeout 2015-04-03 13:21:24 [client 10.0.0.222] HTTP 408 Request Timeout 2015-04-03 13:21:33 [client 10.0.0.222] HTTP 408 Request Timeout 2015-04-03 13:21:33 [client 10.0.2.33] HTTP 408 Request Timeout 2015-04-03 13:21:33 [client 10.0.2.33] HTTP 408 Request Timeout 2015-04-03 13:21:34 [client 10.0.0.222] HTTP 408 Request Timeout The setup looks like this: Load balancer- 001(AWS ELB) -> mmonit-001 -> mysql-001 Load balancer- 001(AWS ELB) -> mmonit-002 -> mysql-001 Everything is set for SSL communication, from LB to mmonit to mysql (for now) Most things seem to work nicely as events are captured and logged. Reviewing the error logs reveals the items above. The monit log looks quiet. I did not see much about this error on the manual or in google searches. Any suggestions or tips would go a long way in helping us in our eval. Best Regards, Tom -- To unsubscribe: https://lists.nongnu.org/mailman/listinfo/monit-general
