heartbeat启动问题

Submitted by netcrab on 周三, 2006-07-19 02:00

在我的LVS测试机器上启动heartbeat（两台load balancer都一样）,提示如下：

[root@lb1 log]# /etc/init.d/heartbeat start
Starting High-Availability services:
2006/07/19_09:52:49 CRITICAL: Resource IPaddr::192.168.136.10/24/eth0/192.168.136.255 is active, and should not be!
2006/07/19_09:52:49 CRITICAL: Non-idle resources can affect data integrity!
2006/07/19_09:52:49 info: If you don't know what this means, then get help!
2006/07/19_09:52:49 info: Read the docs and/or source to /usr/lib/heartbeat/ResourceManager for more details.
CRITICAL: Resource IPaddr::192.168.136.10/24/eth0/192.168.136.255 is active, and should not be!
CRITICAL: Non-idle resources can affect data integrity!
info: If you don't know what this means, then get help!
info: Read the docs and/or the source to /usr/lib/heartbeat/ResourceManager for more details.
2006/07/19_09:52:49 CRITICAL: Non-idle resources will affect resource takeback!
2006/07/19_09:52:49 CRITICAL: Non-idle resources may affect data integrity!
[ OK ]
[root@lb1 log]#

停止、再启动时提示如下：
[root@lb1 log]# /etc/init.d/heartbeat stop
Stopping High-Availability services:
[ OK ]
[root@lb1 log]# /etc/init.d/heartbeat start
Starting High-Availability services:
[ OK ]
[root@lb1 log]#

是不是有什么问题？请大家指点，谢谢！

Forums:

netcrab

周四, 2006-07-20 02:15

顶上

Anonymous (没有被验证)

周五, 2007-04-20 02:30

当我将heartbeat进程直接kill掉时，cluster资源（譬如浮动IP）仍然是active的。此时将heartbeat重新start起来，就会出现这样的告警。也就是说，heartbeat启动时发现了本应由heartbeat负责起停的资源，于是发出这样的CRITICAL告警。
或者你手工预先将资源自行配置并启动了，那么启动heartbeat时应该会有同样的结果吧。

Anonymous (没有被验证)

周二, 2014-03-04 12:32

This is both street smart and ingtelitenl.

Anonymous (没有被验证)

周三, 2014-03-05 08:43

So excited I found this article as it made things much qucriek! http://ngcktsymlq.com [url=http://ntfedqznvpe.com]ntfedqznvpe[/url] [link=http://zxyazbuvblx.com]zxyazbuvblx[/link]

randomness