[ClusterLabs] corosync init script is not a LSB compliance ?

Hi all, I compiled latest version of corosync and found its init script is not LSB compliance. When I check stopped corosync service status with cmd "service corosync status" (on centos 6 without systemd), it returns "1" rather than "3". I found the "status" function in init script return

[ClusterLabs] corosync init script is not a LSB compliance ?

Hi all, I compiled latest version of corosync and found its init script is not LSB compliance. When I check stopped corosync service status with cmd "service corosync status" (on centos 6 without systemd), it returns "1" rather than "3". I found the "status" function in init script return

Re: [ClusterLabs] Master-Slaver resource Restarted after configuration change

On 06/29/2016 01:35 PM, Ilia Sokolinski wrote: > >> >> I'm not sure there's a way to do this. >> >> If a (non-reloadable) parameter changes, the entire clone does need a >> restart, so the cluster will want all instances to be stopped, before >> proceeding to start them all again. >> >> Your

[ClusterLabs] fence-agents 4.0.23 release

Welcome to the fence-agents 4.0.23 release This release includes several bugfixes and features: * A lot of changes in fence_compute (OpenStack compute instance) * Obtain status of nodes from Cisco UCS correctly * New fence agent for AMT using openwsman * Python3 support * Fence agent for PVE can

Re: [ClusterLabs] error: crm_timer_popped: Shutdown Escalation (I_STOP) just popped in state S_POLICY_ENGINE

On 06/29/2016 09:38 AM, Kostiantyn Ponomarenko wrote: > Hello, > > I am seeing those error messages in the syslog when the machine goes > down (one-node cluster): For anyone who missed the IRC discussion: This is probably the issue fixed by commit 6aae854 in the just-released Pacemaker 1.1.15.

Re: [ClusterLabs] Default Behavior

On 06/29/2016 04:54 AM, Klaus Wenninger wrote: > On 06/29/2016 11:00 AM, Pavlov, Vladimir wrote: >> Thanks a lot. >> We also thought to use Fencing (stonith). >> But production cluster works in the cloud, node1 and node2 is virtual >> machines without any hardware fencing devices. > But there are

Re: [ClusterLabs] pcs testsuite status

On Wed, Jun 29, 2016 at 10:31:42AM +0200, Tomas Jelinek wrote: > This should be replaceable by any agent which does not provide unfencing, > i.e. it does not have on_target="1" automatic="1" attributes in name="on" /> . You may need to experiment with few agents to find one which > works. Just

Re: [ClusterLabs] Default Behavior

Thanks a lot. We also thought to use Fencing (stonith). But production cluster works in the cloud, node1 and node2 is virtual machines without any hardware fencing devices. We looked in the direction of the SBR, but its use as far as we understand is not justified without shared storage in