Hi all,
I just came across following scenario:
- using resource group DRBD - Delay - Xen
- resources are active on node A that should become active
- Start CRM
- CRM probes resources, detects Delay as Stopped
- CRM wants to start it, because of dependancy meaning Stop VM, Start
Hi all,
I just came across following scenario:
- using resource group DRBD - Delay - Xen
- resources are active on node A that should become active
- Start CRM
- CRM probes resources, detects Delay as Stopped
- CRM wants to start it, because of dependancy meaning Stop VM, Start
Delay, Start
I'm not very good at reading these logs yet, but I notice it had to kill
off a bunch of processes to get node1 to unmount. Could this have caused
it to be viewed as unstable and hence not failback? I've got the same
No, the unmount in the end succeded.
ipfail[20237]: 2010/05/19_19:09:07
ping xx.xx.xx.129
respawn hacluster /usr/lib/heartbeat/ipfail
apiauth ipfail gid=haclient uid=hacluster
What version do you use? Is there anything in the log files from the
time of gateway was fixed?
If we say Heartbeat V1 config style is obsolete, use of ipfail is
obsolete absolutely. If you
Hi all,
using:
heartbeat-libs-3.0.1-1.el5.x86_64
heartbeat-3.0.1-1.el5.x86_64
This is what I can see in process tree:
root 11991 0.0 0.2 35584 1148 ?S15:14 0:00
/usr/lib64/heartbeat/ha_logd -d -c /etc/logd.cf
root 11992 0.0 0.1 35584 684 ?S15:14 0:00
Hi all,
I downloaded latest EPEL Pacemaker/Heartbeat RPMS. After installing on
CentOS 5.4 I found that the heartbeat will not start correctly because
of missing directory /var/run/heartbeat/crm:
Jan 26 11:37:33 vsp7 /usr/lib64/heartbeat/dopd: [11357]: debug:
Setting message filter mode
Jan 26
Hi Nick,
I am not an expert in this area but I would expect use of attrd_updater to
update any scoring informations that you want to use for constraints. At
least this is what pingd uses to update the attributes. So if you have any
IPMI monitoring daemon, you could call attrd_updater to modify
Hi all,
I'm having problems when active node is lost for a while (gets rebooted).
Scenario:
- two machines, heartbeat 2.1 in V1 config style, all resources defined in
just one group
- kill the active node (e.g. echo b /proc/sysrq-trigger)
- standby node tries to take over all the resources -
Hi all,
Scenario:
- two machines, heartbeat 2.1 in V1 config style, all resources defined in
just one group
- kill the active node (e.g. echo b /proc/sysrq-trigger)
- standby node tries to take over all the resources - OK
- standby fails to start any resource for any reason (e.g. drbd device
Hi all,
we are building Xen virtual machine failover system using heartbeat 2.1.3
(v1 config style - 2 node cluster setup) on CentOS 5.2.
We are using LDAP user authentication on the Domain-0 OS,
the same database will be used for Dom-Us user authentications.
That's why along with migration we
Thanks Thomas for very prompt answer.
we are building Xen virtual machine failover system using heartbeat 2.1.3
(v1 config style - 2 node cluster setup) on CentOS 5.2.
Make your life easier and use hb2 with crm.
Our problem is if we would later on want to use live migration, CRM does not
# cat /proc/drbd
version: 8.0.13 (api:86/proto:86)
GIT-hash: ee3ad77563d2e87171a3da17cc002ddfd1677dbe build by
phil at fat-tyre, 2008-08-04 15:28:07
0: cs:Connected st:Primary/Primary ds:UpToDate/UpToDate C r---
ns:0 nr:25425620 dw:25425620 dr:44 al:0 bm:204 lo:0 pe:0 ua:0 ap:0
12 matches
Mail list logo
