Re: [Pacemaker] color_instance: Pre-allocation failed

2013-01-09 Thread Andrew Beekhof
On Wed, Jan 9, 2013 at 6:40 AM, Stefan Midjich wrote: > Sure but shortly after I posted this to the list I noticed I had duplicate > name entries in /etc/hosts. That wouldn't be good. So everything is working as expected now? > I had made a mistake when setting up a private > l2 vlan for corosy

Re: [Pacemaker] color_instance: Pre-allocation failed

2013-01-08 Thread Stefan Midjich
Sure but shortly after I posted this to the list I noticed I had duplicate name entries in /etc/hosts. I had made a mistake when setting up a private l2 vlan for corosync, it had separate IP-addresses but the same names as the public vlan, as aliases. I suspected this was the cause of the issue. Th

Re: [Pacemaker] color_instance: Pre-allocation failed

2013-01-07 Thread Andrew Beekhof
On Sat, Dec 29, 2012 at 1:21 AM, Stefan Midjich wrote: > Every 15-18 minutes one of my resources gets stopped on one node and then is > restarted shortly after. > > In the DC log I can see the following error lines. > > Dec 28 15:04:09 app01 pengine: [8618]: debug: clone_rsc_colocation_rh: > Pairi

[Pacemaker] color_instance: Pre-allocation failed

2012-12-28 Thread Stefan Midjich
Every 15-18 minutes one of my resources gets stopped on one node and then is restarted shortly after. In the DC log I can see the following error lines. Dec 28 15:04:09 app01 pengine: [8618]: debug: clone_rsc_colocation_rh: Pairing resOCFS:1 with groupOcfs2Mgmt:0 Dec 28 15:04:09 app01 pengine: [8