Re: [ClusterLabs] start a resource

2016-05-05 Thread Moiz Arif
Hi Dimitri, Try cleanup of the fail count for the resource with the any of the below commands: via pcs : pcs resource cleanup rsyncdvia crm: crm resource cleanup rsyncd Hope it helps. Moiz To: users@clusterlabs.org From: dmaz...@bmrb.wisc.edu Date: Thu, 5 May 2016 14:15:09 -0500 Subject:

[ClusterLabs] start a resource

2016-05-05 Thread Dimitri Maziuk
Hi all, I'm sure it must be a FAQ, but how do I start a resource? E.g. Failed Actions: * rsyncd_start_0 on tarpon 'unknown error' (1): call=78, status=complete, exitreason='Error. "pid file" entry required in the rsyncd config file by rsyncd OCF RA.', last-rc-change='Thu May 5 13:55:50

Re: [ClusterLabs] Unable to run Pacemaker: pcmk_child_exit

2016-05-05 Thread Ken Gaillot
On 05/05/2016 11:25 AM, Nikhil Utane wrote: > Thanks Ken for your quick response as always. > > But what if I don't want to use quorum? I just want to bring up > pacemaker + corosync on 1 node to check that it all comes up fine. > I added corosync_votequorum as you suggested. Additionally I also

[ClusterLabs] Unable to run Pacemaker: pcmk_child_exit

2016-05-05 Thread Nikhil Utane
Hi, Continuing with my adventure to run Pacemaker & Corosync on our big-endian system, I managed to get past the corosync issue for now. But facing an issue in running Pacemaker. Seeing following messages in corosync.log. pacemakerd: warning: pcmk_child_exit: The cib process (2) can no

Re: [ClusterLabs] Antw: ringid interface FAULTY no resource move

2016-05-05 Thread RafaƂ Sanocki
for what? cluster working good when i stop pacemaker, resources go to second node, but when connection is lost nothing happend. Failed Actions: * p_ip_2_monitor_3 on csb01B 'not running' (7): call=47, status=complete, exitreason='none', last-rc-change='Wed May 4 17:34:50 2016',

Re: [ClusterLabs] [ClusterLab] : Corosync not initializing successfully

2016-05-05 Thread Nikhil Utane
It worked for me. :) I'll wait for your formal patch but until then I am able to proceed further. (Don't know if I'll run into something else) However now encountering issue in pacemaker. May 05 09:35:53 [15184] airv_cu pacemakerd: warning: pcmk_child_exit: The cib process (15224) can no

Re: [ClusterLabs] [ClusterLab] : Corosync not initializing successfully

2016-05-05 Thread Jan Friesse
Nikhil Found the root-cause. In file schedwrk.c, the function handle2void() uses a union which was not initialized. Because of that the handle value was computed incorrectly (lower half was garbage). 56 static hdb_handle_t 57 void2handle (const void *v) { union u u={}; u.v = v; return u.h;

Re: [ClusterLabs] [ClusterLab] : Corosync not initializing successfully

2016-05-05 Thread Nikhil Utane
Found the root-cause. In file schedwrk.c, the function handle2void() uses a union which was not initialized. Because of that the handle value was computed incorrectly (lower half was garbage). 56 static hdb_handle_t 57 void2handle (const void *v) { union u u={}; u.v = v; return u.h; } 58