[ClusterLabs] stonith:external/ssh: no such resource agent

Hi! OS: CentOS Linux release 7.0.1406 (Core) Pacemaker: pacemaker-1.1.13-10.el7.x86_64 Corosync: corosync-2.3.4-7.el7_2.1.x86_64 # stonith -L |grep -i external/ssh external/ssh # ls -l /usr/lib64/stonith/plugins/external/ssh -rwxr-xr-x 1 root root 4459 Jan 12 12:47 /usr/lib64/stonith/plugins/e

Re: [ClusterLabs] Corosync main process was not scheduled for 115935.2266 ms (threshold is 800.0000 ms). Consider token timeout increase.

Kostiantyn Ponomarenko napsal(a): Thank you for the suggestion. The OS is Debian 8. All Packages are build by myself. libqb-0.17.2 corosync-2.3.5 cluster-glue-1.0.12 pacemaker-1.1.13 It is really important for me to understand what is happening with the cluster under the high load. For Corosyn

Re: [ClusterLabs] Corosync main process was not scheduled for 115935.2266 ms (threshold is 800.0000 ms). Consider token timeout increase.

Thank you for the suggestion. The OS is Debian 8. All Packages are build by myself. libqb-0.17.2 corosync-2.3.5 cluster-glue-1.0.12 pacemaker-1.1.13 It is really important for me to understand what is happening with the cluster under the high load. So I would appreciate any help here =) Thank yo

[ClusterLabs] Fwd: stonith:external/ssh: no such resource agent

Hi! OS: CentOS Linux release 7.0.1406 (Core) Pacemaker: pacemaker-1.1.13-10.el7.x86_64 Corosync: corosync-2.3.4-7.el7_2.1.x86_64 # stonith -L |grep -i external/ssh external/ssh # ls -l /usr/lib64/stonith/plugins/external/ssh -rwxr-xr-x 1 root root 4459 Jan 12 12:47 /usr/lib64/stonith/plugins/ex

Re: [ClusterLabs] Corosync main process was not scheduled for 115935.2266 ms (threshold is 800.0000 ms). Consider token timeout increase.

On Wed, Feb 17, 2016 at 3:30 AM, Kostiantyn Ponomarenko < konstantin.ponomare...@gmail.com> wrote: > Jan 29 07:00:43 B5-2U-205-LS corosync[2742]: [MAIN ] Corosync main > process was not scheduled for 12483.7363 ms (threshold is 800. ms). > Consider token timeout increase. I was having this

Re: [ClusterLabs] Sudden stop of pacemaker functions

On 17/02/16 15:15 +0200, Klechomir wrote: > Here is the output from your command: > > attrd: 609413 > cib: 609409 > corosync: 608778 > crmd: 609415 > lrmd: 609412 > pengine: 609414 > pacemakerd: 609407 > stonithd: 609411 This may mean that you are triggering this nasty bug in libqb: https://githu

Re: [ClusterLabs] Sudden stop of pacemaker functions

Hi Jan, Here is the output from your command: attrd: 609413 cib: 609409 corosync: 608778 crmd: 609415 lrmd: 609412 pengine: 609414 pacemakerd: 609407 stonithd: 609411 Regarding using a newer version, that's what I've been thinking about, but I've been using this combination of corosync/pacemake

Re: [ClusterLabs] Sudden stop of pacemaker functions

On 17/02/16 14:10 +0200, Klechomir wrote: > Having strange issue lately. > I have two node cluster with some cloned resources on it. > One of my nodes suddenly starts reporting all its resources down (some of > them are actually running), stops logging and reminds in this this state > forever, whil

[ClusterLabs] Sudden stop of pacemaker functions

Hi List, Having strange issue lately. I have two node cluster with some cloned resources on it. One of my nodes suddenly starts reporting all its resources down (some of them are actually running), stops logging and reminds in this this state forever, while still responding to crm commands. Th

[ClusterLabs] Corosync main process was not scheduled for 115935.2266 ms (threshold is 800.0000 ms). Consider token timeout increase.

Hi, I am seeing massages like this in my logs: Jan 29 07:00:41 B5-2U-205-LS lrmd[3012]: notice: operation_finished: diskManager_monitor_3:18807:stderr [ Failed to get properties: Connection timed out ] Jan 29 07:00:41 B5-2U-205-LS lrmd[3012]: notice: operation_finished: pmdh_monitor_3:188