Hi, On Mon, Sep 17, 2007 at 03:23:04PM +0200, Johan Bergström wrote: > I have a problem in a pretty simple 2node cluster that the stonithd > daemon is respawned on every cluster operation there is, it seems. > > I have 1 IPaddr resource and 2 eDir88 resources, 1 pingd and the stonith > resource. > > When I checked the system today, I had 4045 processes running. > > # ps -efa | grep /usr/lib64/heartbeat/stonithd | wc -l > 4045
Oooo, that is no good. > I don't know what I've done wrong, setting it up. I'll attach the ha.cf > and the cib.xml. Your cib says meatware agent and it is stopped. Or did you stop it later? A meatware thing needs some kind of interaction with people, as the name says, so perhaps your processes are hanging waiting for input from somewhere/somebody. Can you attach the logs too? > Also, I'm going to add another heartbeat NIC interface, but I'm not sure > how to set that up, any hints to where there's documentation about that? To ha.cf? Just add another bcast/ucast/mcast directive with a name of your interface. Thanks, Dejan > MVH, > > Johan > > autojoin any > crm true > bcast eth0 > node ssm2srv1 > node ssm2srv2 > watchdog /dev/watchdog > keepalive 2 > warntime 10 > deadtime 30 > initdead 120 > udpport 694 > ping 172.19.180.225 > #apiauth stonithd uid=root > #respawn root /usr/lib64/heartbeat/stonithd > respawn root /usr/lib64/heartbeat/pingd -m 100 -d 5s -a pingd > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
