Re: [ClusterLabs] start a resource

2016-05-06 Thread Dimitri Maziuk
On 05/06/2016 12:05 PM, Ian wrote: > Are you getting any other errors now that you've fixed the config? It's running now that I did the cluster stop/start, but no: I wasn't getting any other errors. I did have a symlink resource "stopped" for no apparent reason and with no errors logged. The clus

Re: [ClusterLabs] why and when a call of crm_attribute can be delayed ?

2016-05-06 Thread Jehan-Guillaume de Rorthais
Le Wed, 4 May 2016 09:55:34 -0500, Ken Gaillot a écrit : > On 04/25/2016 05:02 AM, Jehan-Guillaume de Rorthais wrote: > > Hi all, > > > > I am facing a strange issue with attrd while doing some testing on a three > > node cluster with the pgsqlms RA [1]. > > > > pgsqld is my pgsqlms resource in

Re: [ClusterLabs] start a resource

2016-05-06 Thread Ian
Are you getting any other errors now that you've fixed the config? What does your config file look like? On May 6, 2016 10:33 AM, "Dmitri Maziuk" wrote: > On 2016-05-05 23:50, Moiz Arif wrote: > >> Hi Dimitri, >> >> Try cleanup of the fail count for the resource with the any of the below >> comm

Re: [ClusterLabs] start a resource

2016-05-06 Thread Dmitri Maziuk
On 2016-05-05 23:50, Moiz Arif wrote: Hi Dimitri, Try cleanup of the fail count for the resource with the any of the below commands: via pcs : pcs resource cleanup rsyncd Tried it, didn't work. Tried pcs resource debug-start rsyncd -- got no errors, resource didn't start. Tried disable/enabl

Re: [ClusterLabs] help compiling pacemaker 1.1 on Amazon Linux

2016-05-06 Thread Jan Pokorný
On 06/05/16 16:06 +0200, Jan Pokorný wrote: > On 06/05/16 14:52 +0100, Jim Rippon wrote: >> Thank you guys, >> >> I've taken your advice onboard and checked out 1.1.15-rc1 including the >> patches Lars mentions as Jan suggested - I see another warning with fatal >> warnings enabled: >> >> gmake[2

Re: [ClusterLabs] help compiling pacemaker 1.1 on Amazon Linux

2016-05-06 Thread Jan Pokorný
On 06/05/16 14:52 +0100, Jim Rippon wrote: > Thank you guys, > > I've taken your advice onboard and checked out 1.1.15-rc1 including the > patches Lars mentions as Jan suggested - I see another warning with fatal > warnings enabled: > > gmake[2]: Entering directory `/home/jrippon/pacemaker/lib/cl

Re: [ClusterLabs] help compiling pacemaker 1.1 on Amazon Linux

2016-05-06 Thread Jim Rippon
Thank you guys, I've taken your advice onboard and checked out 1.1.15-rc1 including the patches Lars mentions as Jan suggested - I see another warning with fatal warnings enabled: gmake[2]: Entering directory `/home/jrippon/pacemaker/lib/cluster' CC election.lo CC cluster.lo

Re: [ClusterLabs] help compiling pacemaker 1.1 on Amazon Linux

2016-05-06 Thread Jan Pokorný
On 06/05/16 13:31 +0200, Lars Ellenberg wrote: > On Fri, May 06, 2016 at 11:51:25AM +0100, Jim Rippon wrote: >> I'm new to the list so apologies if I'm way off base, but I wonder >> if someone can help me please? >> >> I'm looking to build private RPMs for pacemaker and any dependencies >> for Ama

Re: [ClusterLabs] Unable to run Pacemaker: pcmk_child_exit

2016-05-06 Thread Nikhil Utane
Hi, QQ, how can I configure to use a different folder other than /var/lib/pacemaker? Also, in /dev/shm I see that it created around 300+ files of around 250 MB. For e.g. -rw-rw1 hacluste hacluste 8232 May 6 13:03 qb-cib_rw-response-25035-25038-10-header -rw-rw1 hacluste hac

Re: [ClusterLabs] Unable to run Pacemaker: pcmk_child_exit

2016-05-06 Thread Nikhil Utane
Thanks for the details, Jan. We have cross-compiled the same way. However because of space constraints on target we copied selected folders. For this issue, I made a softlink for pacemaker-1.0.rng to point to pacemaker-next.rng and that did the trick. :) I am not getting the error and the node inf

Re: [ClusterLabs] Unable to run Pacemaker: pcmk_child_exit

2016-05-06 Thread Jan Pokorný
On 06/05/16 16:59 +0530, Nikhil Utane wrote: > > [...] > >> On 05/06/2016 12:40 PM, Nikhil Utane wrote: >>> As I am cross-compiling pacemaker on a build machine and later moving >>> the binaries to the target, few binaries were missing. After fixing >>> that and bunch of other errors/warning, I a

Re: [ClusterLabs] Unable to run Pacemaker: pcmk_child_exit

2016-05-06 Thread Nikhil Utane
I suppose the failure is because I do not have a DC yet. [root@airv_cu xml]# pcs cluster status Cluster Status: Stack: corosync Current DC: NONE Can I bring it up when I have just 1 node? On Fri, May 6, 2016 at 4:59 PM, Nikhil Utane wrote: > The command failed. > [root@airv_cu pacemaker]# ci

Re: [ClusterLabs] help compiling pacemaker 1.1 on Amazon Linux

2016-05-06 Thread Lars Ellenberg
On Fri, May 06, 2016 at 11:51:25AM +0100, Jim Rippon wrote: > Hi guys > > I'm new to the list so apologies if I'm way off base, but I wonder > if someone can help me please? > > I'm looking to build private RPMs for pacemaker and any dependencies > for Amazon Linux because I have as yet been unab

Re: [ClusterLabs] Unable to run Pacemaker: pcmk_child_exit

2016-05-06 Thread Nikhil Utane
The command failed. [root@airv_cu pacemaker]# cibadmin --upgrade --force Call cib_upgrade failed (-62): Timer expired I did not do any tooling. (Not even aware how to) As I mentioned, I am cross-compiling and copying the relevant files on target platform. In one of the earlier run pacemaker cribb

Re: [ClusterLabs] help compiling pacemaker 1.1 on Amazon Linux

2016-05-06 Thread Jim Rippon
Hi Rafał Yes, I've got all the packages in the dependencies list in my "rpm -qa" output. I'm running gcc 4.8.3 with -v output as below: [root@Auto-Failover-Test-Arbiter pacemaker]# gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-amazon-linux/4

Re: [ClusterLabs] Unable to run Pacemaker: pcmk_child_exit

2016-05-06 Thread Klaus Wenninger
On 05/06/2016 12:40 PM, Nikhil Utane wrote: > Hi, > > I used the blackbox feature which showed the reason for failure. > As I am cross-compiling pacemaker on a build machine and later moving > the binaries to the target, few binaries were missing. After fixing > that and bunch of other errors/warni

Re: [ClusterLabs] help compiling pacemaker 1.1 on Amazon Linux

2016-05-06 Thread Rafał Sanocki
Hi, I guess you got: automake autoconf libtool-ltdl-devel libuuid-devel pkgconfig python (or python-devel if that's preferred as a build dependency) glib2-devel libxml2-devel libxslt-devel bzip2-devel gnutls-devel pam-devel libqb-devel show us gcc -v Rafal W dniu 2016-05-06 o 12:51, Jim Rippo

[ClusterLabs] help compiling pacemaker 1.1 on Amazon Linux

2016-05-06 Thread Jim Rippon
Hi guys I'm new to the list so apologies if I'm way off base, but I wonder if someone can help me please? I'm looking to build private RPMs for pacemaker and any dependencies for Amazon Linux because I have as yet been unable to get the CentOS binaries to install successfully. I've got lib

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

2016-05-06 Thread Rafał Sanocki
I modify configuration of drbd but still nothing. I not mention the clusters are on hp blades machines. I plug out connection on switch by disabling port. But still nothing :( , maybe add something like this to crm will do? ocf:pacemaker:ping \ params host_list="172.17.10.81 17

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

2016-05-06 Thread Rafał Sanocki
Thank you very much, I'll try now to set up. Rafał W dniu 2016-05-05 o 16:29, Ken Gaillot pisze: On 05/05/2016 07:43 AM, Rafał Sanocki wrote: for what? cluster working good when i stop pacemaker, resources go to second node, but when connection is lost nothing happend. Failed Actions: * p_