I think you have a network problem, your nodes are OFFLINE. If you read "Getting Started" from Linux-HA, you can read "initdead: With some configurations, the network takes some time to start working after a reboot. This is a separate "deadtime" to handle that case. It should be at least twice the normal deadtime <http://linux-ha.org/ha.cf/DeadtimeDirective>."
On Wed, Mar 5, 2008 at 10:39 AM, Schmidt, Florian < [EMAIL PROTECTED]> wrote: > Hi list, > > After starting heartbeat I always see the following message in > /var/log/ha-log: > > attrd[5813]: 2008/03/05_10:22:43 info: main: Starting mainloop... > > then 2 minutes nothing happens (no log entry) and crmmon -1 says: > > Refresh in 1s... > > ============ > Last updated: Wed Mar 5 10:24:10 2008 > Current DC: NONE > 2 Nodes configured. > 3 Resources configured. > ============ > > Node: noderz (91d062c3-ad0a-4c24-b759-acada7f19101): OFFLINE > Node: nodekrz (44425bd9-2cba-4d6a-ac62-82a8bb81a23d): OFFLINE > > > What does the heartbeat wait for during this 2 minutes? Is this because > of directive initdead? > > Here is my /etc/ha.d/ha.cf > > crm yes > debugfile /var/log/ha-debug > logfile /var/log/ha-log > logfacility local0 > keepalive 2 > deadtime 30 > warntime 10 > initdead 120 > bcast eth1 > ucast eth0 193.30.176.197 > auto_failback off > node noderz > node nodekrz > #ping 10.10.10.254 > respawn hacluster /usr/lib/heartbeat/dopd > apiauth dopd gid=haclient uid=hacluster > > Thanks > > Florian > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > -- I should have known better Than to let you go alone It's times like these I can't make it on my own Wasted days, and sleepless nights An' I can't wait to see you again _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
