On the same lan, there are already two heartbeat node 136pri and 137sec.
I setup another 2 nodes with heartbeat. they keep receiving the following
messages:
heartbeat[9931]: 2010/01/19_10:53:01 WARN: string2msg_ll: node [136pri] failed
authentication
heartbeat[9931]: 2010/01/19_10:53:02 WARN:
Aclhk Aclhk wrote:
On the same lan, there are already two heartbeat node 136pri and 137sec.
I setup another 2 nodes with heartbeat. they keep receiving the following
messages:
heartbeat[9931]: 2010/01/19_10:53:01 WARN: string2msg_ll: node [136pri]
failed authentication
heartbeat[9931]:
On Tue, Jan 19, 2010 at 1:15 PM, Dominik Klein d...@in-telegence.net wrote:
Aclhk Aclhk wrote:
On the same lan, there are already two heartbeat node 136pri and 137sec.
I setup another 2 nodes with heartbeat. they keep receiving the following
messages:
heartbeat[9931]: 2010/01/19_10:53:01
On Fri, Jan 15, 2010 at 7:23 AM, 梁景明 futur...@gmail.com wrote:
hi ,there are 4 cases in my application to use pacemaker
case 1: one tomcat unexpected down ,restart it by pacemaker.
case 2: one tomcat served machine unexpected down ,fail over to another
machine,back if it recover.
case 3: some
