Failed actions: httpd_monitor_5000 on abc-zabserver-b 'not running' (7): call=65, status=complete, last-rc-change='Wed Jul 15 21:44:43 2015', queued=0ms, exec=8ms [root@abc-zabserver-b ~]# pcs status Cluster name: abc-zabvip Last updated: Wed Jul 15 21:50:52 2015 Last change: Wed Jul 15 20:38:07 2015 Stack: cman Current DC: abc-zabserver-b - partition with quorum Version: 1.1.11-97629de 2 Nodes configured 3 Resources configured Online: [ abc-zabserver-a abc-zabserver-b ] Full list of resources: Resource Group: zabbix-cluster ClusterIP (ocf::heartbeat:IPaddr2): Started abc-zabserver-b zabbix-server (lsb:zabbix-server): Started abc-zabserver-b httpd (lsb:httpd): Started abc-zabserver-b Failed actions: httpd_monitor_5000 on abc-zabserver-b 'not running' (7): call=65, status=complete, last-rc-change='Wed Jul 15 21:44:43 2015', queued=0ms, exec=8ms
pcs resource create ClusterIP ocf:heartbeat:IPaddr2 ip=10.99.122.69 cidr_netmask=24 op monitor interval=5s pcs property set stonith-enabled=false pcs resource create zabbix-server lsb:zabbix-server op monitor interval=5s pcs resource create httpd lsb:httpd op monitor interval=5s pcs resource group add zabbix-cluster ClusterIP zabbix-server httpd pcs property set no-quorum-policy=ignore pcs property set default-resource-stickiness="100"
[root@abc-zabserver-b ~]# pcs config show Cluster Name: abc-zabvip Corosync Nodes: abc-zabserver-a abc-zabserver-b Pacemaker Nodes: abc-zabserver-a abc-zabserver-b Resources: Group: zabbix-cluster Resource: ClusterIP (class=ocf provider=heartbeat type=IPaddr2) Attributes: ip=10.99.122.69 cidr_netmask=24 Operations: start interval=0s timeout=20s (ClusterIP-start-timeout-20s) stop interval=0s timeout=20s (ClusterIP-stop-timeout-20s) monitor interval=5s (ClusterIP-monitor-interval-5s) Resource: zabbix-server (class=lsb type=zabbix-server) Operations: monitor interval=5s (zabbix-server-monitor-interval-5s) Resource: httpd (class=lsb type=httpd) Operations: monitor interval=5s (httpd-monitor-interval-5s) Stonith Devices: Fencing Levels: Location Constraints: Ordering Constraints: Colocation Constraints: Cluster Properties: cluster-infrastructure: cman dc-version: 1.1.11-97629de default-resource-stickiness: 100 no-quorum-policy: ignore stonith-enabled: false
[root@abc-zabserver-b ~]# cat /etc/cluster/cluster.conf <cluster config_version="9" name="abc-zabvip"> <fence_daemon/> <clusternodes> <clusternode name="abc-zabserver-a" nodeid="1"> <fence> <method name="pcmk-redirect"> <device name="pcmk" port="abc-zabserver-a"/> </method> </fence> </clusternode> <clusternode name="abc-zabserver-b" nodeid="2"> <fence> <method name="pcmk-redirect"> <device name="pcmk" port="abc-zabserver-b"/> </method> </fence> </clusternode> </clusternodes> <cman expected_votes="1" port="5405" transport="udpu" two_node="1"/> <fencedevices> <fencedevice agent="fence_pcmk" name="pcmk"/> </fencedevices> <rm> <failoverdomains/> <resources/> </rm> </cluster>
httpd资源似乎正在运行（根据您显示的pcs状态输出）。 也许有些东西停止了服务，而Pacemaker正在监控它，这会抛出你看到的上述错误，并触发恢复。
如果您对“LogActions”grep您的日志（在DC：“当前DC：vda-zabserver-b – 带有仲裁的分区”），您应该看到任何启动/停止/恢复/重新启动/离开操作Pacemaker在资源上执行。
如果是这样的话，除了Pacemaker公司正在pipe理这些集群服务之外， 起搏器希望是唯一启动和停止这些服务的东西。
您可以通过运行以下命令来清除错误：
# pcs resource cleanup httpd
返回码7通常意味着当Pacemaker检查其状态时服务未运行。
http://clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/ap-lsb.html http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core -generic / iniscrptact.html
我通过在httpd.conf中取消注释状态URL并通过这种方式创build资源来解决这个问题。 请确保在添加资源之前， http：// localhost / server-status是可访问的
pcs resource create httpd apache configfile="/etc/httpd/conf/httpd.conf" statusurl="http://localhost/server-status" op monitor interval=5s --group zabbix-cluster