[ClusterLabs] Antw: emergency stop does not honor resources ordering constraints (?)

>>> Radoslaw Garbacz schrieb am 06.12.2016 >>> um 18:50 in Nachricht : > Hi, > > I have encountered a problem with pacemaker resources shutdown in case of > (seems like) any emergency situation, when order constraints are not > honored. > I would be grateful for any information, whether this beh

[ClusterLabs] Antw: Re: Error performing operation: Argument list too long

>>> Ken Gaillot schrieb am 06.12.2016 um 16:44 in Nachricht <58329eaf-cbe0-55e0-7648-849879f1b...@redhat.com>: > On 12/05/2016 02:29 PM, Shane Lawrence wrote: >> I'm experiencing a strange issue with pacemaker. It is unable to check >> the status of a systemd resource. >> >> systemctl shows that

Re: [ClusterLabs] Error performing operation: Argument list too long

06.12.2016 20:41, Jan Pokorný пишет: > On 06/12/16 09:44 -0600, Ken Gaillot wrote: >> On 12/05/2016 02:29 PM, Shane Lawrence wrote: >>> I'm experiencing a strange issue with pacemaker. It is unable to check >>> the status of a systemd resource. >>> >>> systemctl shows that the service crashed: No,

[ClusterLabs] emergency stop does not honor resources ordering constraints (?)

Hi, I have encountered a problem with pacemaker resources shutdown in case of (seems like) any emergency situation, when order constraints are not honored. I would be grateful for any information, whether this behavior is intentional or should not happen (i.e. some testing issue rather then pacema

Re: [ClusterLabs] Error performing operation: Argument list too long

On 06/12/16 09:44 -0600, Ken Gaillot wrote: > On 12/05/2016 02:29 PM, Shane Lawrence wrote: >> I'm experiencing a strange issue with pacemaker. It is unable to check >> the status of a systemd resource. >> >> systemctl shows that the service crashed: >> [root@xx ~]# systemctl status rsyslo

Re: [ClusterLabs] Error performing operation: Argument list too long

On 12/05/2016 02:29 PM, Shane Lawrence wrote: > I'm experiencing a strange issue with pacemaker. It is unable to check > the status of a systemd resource. > > systemctl shows that the service crashed: > [root@xx ~]# systemctl status rsyslog > ● rsyslog.service - System Logging Service >

Re: [ClusterLabs] Antw: [pacemaker+ clvm] Cluster lvm must be active exclusively to create snapshot

Yes! I have tried it and succeeded. Clustered LVM can take snapshot only on exclusively lock mode. 2016-12-06 16:23 GMT+08:00 Ulrich Windl : > >>> su liu schrieb am 06.12.2016 um 02:16 in > Nachricht > : > > *Hi all,* > > > > > > *I am new to pacemaker and I have some questions about the clv

Re: [ClusterLabs] How to DRBD + Pacemaker + Samba in Active/Passive Cluster?

Hi, like Ulrich already said, you don't need CTDB for "active/passive" Samba, we use standard LSB RA for Samba init script without problems since many years. Best, Stan 2016-12-05 10:16 GMT+01:00 Semion Itic : > Hello Everybody, > > How to DRBD + Pacemaker + Samba in Active/Passive Cluster? > >

[ClusterLabs] Antw: [pacemaker+ clvm] Cluster lvm must be active exclusively to create snapshot

>>> su liu schrieb am 06.12.2016 um 02:16 in Nachricht : > *Hi all,* > > > *I am new to pacemaker and I have some questions about the clvmd + > pacemaker + corosync. I wish you could explain it for me if you are free. > thank you very much!* > *I have 2 nodes and the pacemaker's status is as fol

[ClusterLabs] Antw: How to DRBD + Pacemaker + Samba in Active/Passive Cluster?

>>> Semion Itic schrieb am 05.12.2016 um 10:16 in Nachricht <7bdd2f4d-7c0a-49b1-b42e-9668befbb...@outlook.de>: > Hello Everybody, > > How to DRBD + Pacemaker + Samba in Active/Passive Cluster? > > I have been searching now about many days how to integrate drbd + pacemaker > and corosync in a t