Re: [Pacemaker] A lot of errors in log
Don't worry about this question. I've already found the answer in google ... 16.07.2012 8:31, Andrew Beekhof пишет: On Fri, Jul 13, 2012 at 6:19 PM, Виталий Давудов vitaliy.davu...@vts24.ru wrote: Hi! Some time ago I upgraded my cluster installation: migrate pacemaker from 1.0.12 to 1.1.5 Here my configuration: crm(live)configure# show node $id=552f91eb-e70a-40a5-ac43-cb16e063fdba freeswitch1 \ attributes standby=off node $id=c86ab64d-26c4-4595-aa32-bf9d18f714e7 freeswitch2 \ attributes standby=off primitive FailoverIP1 ocf:heartbeat:IPaddr2 \ params iflabel=FoIP1 ip=91.211.219.142 cidr_netmask=30 nic=eth1.50 \ op monitor interval=1s primitive FailoverIP2 ocf:heartbeat:IPaddr2 \ params iflabel=FoIP2 ip=172.30.0.1 cidr_netmask=16 nic=eth1.554 \ op monitor interval=1s primitive FailoverIP3 ocf:heartbeat:IPaddr2 \ params iflabel=FoIP3 ip=10.18.1.1 cidr_netmask=24 nic=eth1.552 \ op monitor interval=1s primitive fs lsb:FSSofia \ op monitor interval=1s enabled=false timeout=2s on-fail=standby \ meta target-role=Started group HAServices FailoverIP1 FailoverIP2 FailoverIP3 \ meta target-role=Started order FS-after-IP inf: HAServices fs property $id=cib-bootstrap-options \ dc-version=1.1.5-1.1.el5-01e86afaaa6d4a8c4836f68df80ababd6ca3902f \ cluster-infrastructure=Heartbeat \ stonith-enabled=false \ expected-quorum-votes=1 \ no-quorum-policy=ignore \ last-lrm-refresh=1299964019 rsc_defaults $id=rsc-options \ resource-stickiness=100 And now, I see every second in ha-debug this errors, although in configuration stonith-enabled=false: Jul 13 11:32:27 freeswitch1 crmd: [6369]: ERROR: te_connect_stonith: Sign-in failed: triggered a retry Jul 13 11:32:27 freeswitch1 crmd: [6369]: info: te_connect_stonith: Attempting connection to fencing daemon... Jul 13 11:32:28 freeswitch1 crmd: [6369]: ERROR: te_connect_stonith: Sign-in failed: triggered a retry Jul 13 11:32:28 freeswitch1 crmd: [6369]: info: te_connect_stonith: Attempting connection to fencing daemon... Please, help to resolve this issue! How? ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org -- Best regards, Vitaly ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
Re: [Pacemaker] A lot of errors in log
On Fri, Jul 13, 2012 at 6:19 PM, Виталий Давудов vitaliy.davu...@vts24.ru wrote: Hi! Some time ago I upgraded my cluster installation: migrate pacemaker from 1.0.12 to 1.1.5 Here my configuration: crm(live)configure# show node $id=552f91eb-e70a-40a5-ac43-cb16e063fdba freeswitch1 \ attributes standby=off node $id=c86ab64d-26c4-4595-aa32-bf9d18f714e7 freeswitch2 \ attributes standby=off primitive FailoverIP1 ocf:heartbeat:IPaddr2 \ params iflabel=FoIP1 ip=91.211.219.142 cidr_netmask=30 nic=eth1.50 \ op monitor interval=1s primitive FailoverIP2 ocf:heartbeat:IPaddr2 \ params iflabel=FoIP2 ip=172.30.0.1 cidr_netmask=16 nic=eth1.554 \ op monitor interval=1s primitive FailoverIP3 ocf:heartbeat:IPaddr2 \ params iflabel=FoIP3 ip=10.18.1.1 cidr_netmask=24 nic=eth1.552 \ op monitor interval=1s primitive fs lsb:FSSofia \ op monitor interval=1s enabled=false timeout=2s on-fail=standby \ meta target-role=Started group HAServices FailoverIP1 FailoverIP2 FailoverIP3 \ meta target-role=Started order FS-after-IP inf: HAServices fs property $id=cib-bootstrap-options \ dc-version=1.1.5-1.1.el5-01e86afaaa6d4a8c4836f68df80ababd6ca3902f \ cluster-infrastructure=Heartbeat \ stonith-enabled=false \ expected-quorum-votes=1 \ no-quorum-policy=ignore \ last-lrm-refresh=1299964019 rsc_defaults $id=rsc-options \ resource-stickiness=100 And now, I see every second in ha-debug this errors, although in configuration stonith-enabled=false: Jul 13 11:32:27 freeswitch1 crmd: [6369]: ERROR: te_connect_stonith: Sign-in failed: triggered a retry Jul 13 11:32:27 freeswitch1 crmd: [6369]: info: te_connect_stonith: Attempting connection to fencing daemon... Jul 13 11:32:28 freeswitch1 crmd: [6369]: ERROR: te_connect_stonith: Sign-in failed: triggered a retry Jul 13 11:32:28 freeswitch1 crmd: [6369]: info: te_connect_stonith: Attempting connection to fencing daemon... Please, help to resolve this issue! How? ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
[Pacemaker] A lot of errors in log
Hi! Some time ago I upgraded my cluster installation: migrate pacemaker from 1.0.12 to 1.1.5 Here my configuration: crm(live)configure# show node $id=552f91eb-e70a-40a5-ac43-cb16e063fdba freeswitch1 \ attributes standby=off node $id=c86ab64d-26c4-4595-aa32-bf9d18f714e7 freeswitch2 \ attributes standby=off primitive FailoverIP1 ocf:heartbeat:IPaddr2 \ params iflabel=FoIP1 ip=91.211.219.142 cidr_netmask=30 nic=eth1.50 \ op monitor interval=1s primitive FailoverIP2 ocf:heartbeat:IPaddr2 \ params iflabel=FoIP2 ip=172.30.0.1 cidr_netmask=16 nic=eth1.554 \ op monitor interval=1s primitive FailoverIP3 ocf:heartbeat:IPaddr2 \ params iflabel=FoIP3 ip=10.18.1.1 cidr_netmask=24 nic=eth1.552 \ op monitor interval=1s primitive fs lsb:FSSofia \ op monitor interval=1s enabled=false timeout=2s on-fail=standby \ meta target-role=Started group HAServices FailoverIP1 FailoverIP2 FailoverIP3 \ meta target-role=Started order FS-after-IP inf: HAServices fs property $id=cib-bootstrap-options \ dc-version=1.1.5-1.1.el5-01e86afaaa6d4a8c4836f68df80ababd6ca3902f \ cluster-infrastructure=Heartbeat \ stonith-enabled=false \ expected-quorum-votes=1 \ no-quorum-policy=ignore \ last-lrm-refresh=1299964019 rsc_defaults $id=rsc-options \ resource-stickiness=100 And now, I see every second in ha-debug this errors, although in configuration stonith-enabled=false: Jul 13 11:32:27 freeswitch1 crmd: [6369]: ERROR: te_connect_stonith: Sign-in failed: triggered a retry Jul 13 11:32:27 freeswitch1 crmd: [6369]: info: te_connect_stonith: Attempting connection to fencing daemon... Jul 13 11:32:28 freeswitch1 crmd: [6369]: ERROR: te_connect_stonith: Sign-in failed: triggered a retry Jul 13 11:32:28 freeswitch1 crmd: [6369]: info: te_connect_stonith: Attempting connection to fencing daemon... Please, help to resolve this issue! -- Best regards, Vitaly ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
