Hi All I should clarify this a bit,
I have just upgraded a test cluster from FC8 to FC13 and with it the latest version of Heartbeat / Pacemaker / Corosync (cluster is heartbeat / pacemaker, corosync is installed but not running) I have the cluster set to not use stonith as this it not a production system and there is no supported hardware within the test environment that will allow a proper shutdown. Since the upgrade the logs have been getting flooded with the errors below, and from reading a previous post (http://www.gossamer-threads.com/lists/linuxha/pacemaker/61682) I am under the impression that the stonithd service should be launched by heartbeat (crm respawn set in ha.cf) as pacemaker insists on connecting to the stonithd event if no stonith is enabled. Any advice? Thanks Jay On 30 July 2010 17:09, Jason Fitzpatrick <[email protected]> wrote: > Hi all > > I am under the impression that Pacemaker insists on connecting to the > Stonith Daemon which should have been launched by Heartbeat when the > heartbeat starts, and was wondering what is the best way of > configuring this? > > As is stands I am getting 1000's of > Jul 30 17:07:36 lpissan1001 crmd: [25483]: ERROR: te_connect_stonith: > Sign-in failed: triggered a retry > Jul 30 17:07:36 lpissan1001 crmd: [25483]: info: te_connect_stonith: > Attempting connection to fencing daemon... > in /var/log/ha.log and /var/log/messages > > This is only since upgrading Fedora, Heartbeat et el from a much older version > > Thanks a mill > > Jay > > -- > > "The only difference between saints and sinners is that every saint > has a past while every sinner has a future. " > — Oscar Wilde > -- "The only difference between saints and sinners is that every saint has a past while every sinner has a future. " — Oscar Wilde _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
