On Wed, Jun 1, 2011 at 12:04 PM, 吴鸿宇 wrote:
> Thank you for your reply.
>
> My requirement is like this:
> The httpd service runs on every node in the cluster and is monitored by
> watchdog. VIP only runs on one node at a time. Heartbeat will check the
> status of httpd on each node and make sure
Thank you for your reply.
My requirement is like this:
The httpd service runs on every node in the cluster and is monitored by
watchdog. VIP only runs on one node at a time. Heartbeat will check the
status of httpd on each node and make sure the VIP runs on the node that has
httpd running. Note th
Il giorno Gio 19 Mag 2011 19:25:54 CET, 吴鸿宇 ha scritto:
> Hi All,
> I have a 2 node cluster. My intention is ensuring the VIP is always on the
> node that has httpd running, i.e. if service httpd on the VIP node is
> stopped and fails to start, the VIP should switch to the other node.
> With the co
Hi,
any chance to update to version 3?
2.1.3 is really very old & buggy!
HTH
Nikita Michalko
Am Donnerstag 19 Mai 2011 19:25:54 schrieb 吴鸿宇:
> Hi All,
>
> I have a 2 node cluster. My intention is ensuring the VIP is always on the
> node that has httpd running, i.e. if service httpd on the V
Hi All,
I have a 2 node cluster. My intention is ensuring the VIP is always on the
node that has httpd running, i.e. if service httpd on the VIP node is
stopped and fails to start, the VIP should switch to the other node.
With the configuration below, I observed that when httpd stops and fails to
