Re: [ClusterLabs] Ocassionally IPaddr2 resource fails to start

2019-10-07 Thread Jan Pokorný
Donat, On 07/10/19 09:24 -0500, Ken Gaillot wrote: > If this always happens when the VM is being snapshotted, you can put > the cluster in maintenance mode (or even unmanage just the IP > resource) while the snapshotting is happening. I don't know of any > reason why snapshotting would affect

Re: [ClusterLabs] Apache doesn't start under corosync with systemd

2019-10-07 Thread Jan Pokorný
On 07/10/19 10:27 -0500, Ken Gaillot wrote: > Additionally, your pacemaker configuration is using the apache OCF > script, so the cluster won't use /etc/init.d/apache2 at all (it invokes > the httpd binary directly). See my parallel response. > Keep in mind that the httpd monitor action requires

Re: [ClusterLabs] Unable to resource due to nvpair[@name="target-role"]: No such device or address

2019-10-07 Thread Ken Gaillot
On Mon, 2019-10-07 at 13:34 +, S Sathish S wrote: > Hi Team, > > I have two below query , we have been using Rhel 6.5 OS Version with > below clusterlab source code compiled. > > corosync-1.4.10 > pacemaker-1.1.10 > pcs-0.9.90 > resource-agents-3.9.2 Ouch, that's really old. It should

Re: [ClusterLabs] Apache doesn't start under corosync with systemd

2019-10-07 Thread Ken Gaillot
On Fri, 2019-10-04 at 14:10 +, Reynolds, John F - San Mateo, CA - Contractor wrote: > Good morning. > > I’ve just upgraded a two-node active-passive cluster from SLES11 to > SLES12. This means that I’ve gone from /etc/init.d scripts to > systemd services. > > On the SLES11 server, this

Re: [ClusterLabs] Antw: Ocassionally IPaddr2 resource fails to start

2019-10-07 Thread Ken Gaillot
On Mon, 2019-10-07 at 14:40 +0300, Donat Zenichev wrote: > Hello and thank you for your answer! > > So should I just disable "monitor" options at all? In my case I'd > better delete the whole "op" row: > "op monitor interval=20 timeout=60 on-fail=restart" > > am I correct? Personally I

[ClusterLabs] Unable to resource due to nvpair[@name="target-role"]: No such device or address

2019-10-07 Thread S Sathish S
Hi Team, I have two below query , we have been using Rhel 6.5 OS Version with below clusterlab source code compiled. corosync-1.4.10 pacemaker-1.1.10 pcs-0.9.90 resource-agents-3.9.2 Query 1 : we have added below resource group as required later we are trying to start the resource group , but

Re: [ClusterLabs] Antw: Ocassionally IPaddr2 resource fails to start

2019-10-07 Thread Donat Zenichev
Hello and thank you for your answer! So should I just disable "monitor" options at all? In my case I'd better delete the whole "op" row: "op monitor interval=20 timeout=60 on-fail=restart" am I correct? On Mon, Oct 7, 2019 at 2:36 PM Ulrich Windl < ulrich.wi...@rz.uni-regensburg.de> wrote: >

[ClusterLabs] Antw: Ocassionally IPaddr2 resource fails to start

2019-10-07 Thread Ulrich Windl
Hi! I can't remember the exact reason, but probably it was exactly that what made us remove any monitor operation from IPaddr2 (back in 2011). So far no problems doing so ;-) Regards, Ulrich P.S.: Of cource it would be nice if the real issue could be found and fixed. >>> Donat Zenichev

[ClusterLabs] Antw: Coming in Pacemaker 2.0.3: Year 2038 compatibility

2019-10-07 Thread Ulrich Windl
>>> Ken Gaillot schrieb am 17.09.2019 um 06:38 in Nachricht : > Hi all, > > I wanted to highlight a feature of the next Pacemaker release: it will > be ready for the Year 2038. > > I'm sure most people reading this are familiar with the problem. > Representing epoch timestamps (seconds since

Re: [ClusterLabs] Apache doesn't start under corosync with systemd

2019-10-07 Thread Jan Pokorný
On 04/10/19 14:10 +, Reynolds, John F - San Mateo, CA - Contractor wrote: > I've just upgraded a two-node active-passive cluster from SLES11 to > SLES12. This means that I've gone from /etc/init.d scripts to > systemd services. > > On the SLES11 server, this worked: > >