Hi everyone,

I just experienced again a check on the health of haproxy for one of our clients which forced a failover to our backup haproxy system. I am hoping someone has something to help with this. From looking at the documentation it states that the mode health will not log anything if logging is turned on. I am not finding anything in the system logs that would indicate why haproxy would not respond which caused Nagios to send the ha_standby to the system to fail it over. And I did not find anything on the Monitoring system to indicate that it had a problem either. As this was the primary system I did not have logging turned on, I do now and tonight when traffic is lower I will fail it back over to the primary.

Here is my health check section in haproxy, we are running version 1.3.15.7 running on Centos x86_64 kernel 2.6.18-92.1.10.el5:

listen health_check 0.0.0.0:60000
       mode health

Nagios Log entry for this event:

[1236025204] SERVICE ALERT: haproxy1;HAPROXY_HTTP;CRITICAL;HARD;1;HTTP CRITICAL - No data received from host

The failover happened at D/T: 02-03-2009 15:20:05

Any ideas or help would be very much appreciated.

Thanks

Joe

--
This message has been scanned for viruses by Colocube's AV Scanner

begin:vcard
fn:Joseph Hardeman
n:Hardeman;Joseph
org:Colocube, LLC;Operations
adr:;;4311 Communications Dr;Norcross;GA;30093;US
email;internet:[email protected]
title:Data Center Manager
tel;work:678-427-5890
tel;cell:678-427-5890
note:This email message is intended for the use of the person to whom it has been sent, and may contain information that is confidential or legally protected. If you are not the intended recipient or have received this message in error, you are not authorized to copy, distribute, or otherwise use this message or its attachments. Please notify the sender immediately by return e-mail and permanently delete this message and any attachments.  Thank you.
x-mozilla-html:FALSE
url:http://www.colocube.com
version:2.1
end:vcard

Reply via email to