Hi,
I was trying to understand how Heartbeat actually works. I found out that Heartbeat provides HA at a system level rather than application level, meaning the Virtual IP is moved to backup system only on a system-down-scenario and not when application monitored goes down. I verified this. I had configured httpd in my haresources file and I manually stopped httpd using "service httpd stop". Although this stops httpd service, Heartbeat doesn't recognize this. ..!!
But when I stop heartbeat or bring down my machine, Backup comes up and starts httpd. Is this the correct scenario.. if so, please let me know why I should provide a script in resources.d/ to start, stop and find status of the application. Also, how can I achieve application level HA using heartbeat..!
Thanks in advance.. :)
Regards,
Ravikiran N
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
I was trying to understand how Heartbeat actually works. I found out that Heartbeat provides HA at a system level rather than application level, meaning the Virtual IP is moved to backup system only on a system-down-scenario and not when application monitored goes down. I verified this. I had configured httpd in my haresources file and I manually stopped httpd using "service httpd stop". Although this stops httpd service, Heartbeat doesn't recognize this. ..!!
But when I stop heartbeat or bring down my machine, Backup comes up and starts httpd. Is this the correct scenario.. if so, please let me know why I should provide a script in resources.d/ to start, stop and find status of the application. Also, how can I achieve application level HA using heartbeat..!
Thanks in advance.. :)
Regards,
Ravikiran N
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems