[ClusterLabs] Create ressource to monitor each IPSEC VPN

Hi, We have a 2 nodes cluster with ipsec (libreswan). Actually we have a resource to monitor the service ipsec (via system). But now I would like to monitor each VPN. Is there a way to do that ? Which agent could I use for that ? Thanks in advance for your help. Damien

Re: [ClusterLabs] Antw: Re: Never join a list without a problem...

Just for grins and giggles (I need some of both right now) I just updated to SL6.8. We'll see what's what now. That's EVERYTHING changed. From: Jeffrey Westgate Sent: Wednesday, March 08, 2017 12:13 PM To: users@clusterlabs.org Subject: Re: Antw: Re:

Re: [ClusterLabs] Antw: Re: Never join a list without a problem...

yes - at least I think this is all the packages. (What I did was run a yum update -y, for the most part - had to do pacemaker separately -- had to stop it, update it, start it.) now, is it possible I'm missing a needed package after the update... but dependencies should have handled that?

Re: [ClusterLabs] corosync totem.token too long may cause pacemaker(cluster) unstable?

cys napsal(a): At 2017-03-08 17:10:36, "Jan Friesse" wrote: Hi, We changed totem.token from 3s to 60s. Then something strange were observed, such as unexpected node offline. I read corosync.conf manpage, but still don't understand the reason. Can anyone explain this? or

Re: [ClusterLabs] Antw: Re: Never join a list without a problem...

On 03/08/2017 09:58 AM, Jeffrey Westgate wrote: > Ok. > > Been running monit for a few days, and atop (running a script to capture an > atop output every 10 seconds for an hour, rotate the log, and do it again; > runs from midnight to midnight, changes the date, and does it again). I >

Re: [ClusterLabs] Antw: Corosync ring marked as FAULTY

Hi Everyone, So my question is - why Corosync didn't work correctly if it start under Pacemaker? Finally I found the answer. In short - it was caused by the wrong settings of local name resolver. /etc/cluster/cluster.conf contain the similar settings for each node:

Re: [ClusterLabs] Antw: Re: Antw: Expected recovery behavior of remote-node guest when corosync ring0 is lost in a passive mode RRP config?

Ulrich, Can you share with me some details how your pacemaker, corosync and LGM is configured? I should consider implementing a similar approach and this would be very helpful to me. Thanks... Scott Scott Greenlese ... KVM on System Z - Solutions Test, IBM Poughkeepsie, N.Y. INTERNET:

[ClusterLabs] VirtualDomain as non-root / encrypted

hi, Any ideas how to run VirtualDomain Resource as non-root user with encrypted transport to remote hypervisor(ssh)? i'm able to start/stop/migrate vm via libvirt as non-root, but it doesn't work with pacemaker - pacemaker runs VirtualDomain as root, also there is no option to pass user via

Re: [ClusterLabs] corosync totem.token too long may cause pacemaker(cluster) unstable?

At 2017-03-08 17:10:36, "Jan Friesse" wrote: >> Hi, >> We changed totem.token from 3s to 60s. Then something strange were observed, >> such as unexpected node offline. >> I read corosync.conf manpage, but still don't understand the reason. >> Can anyone explain this? or

Re: [ClusterLabs] corosync totem.token too long may cause pacemaker(cluster) unstable?

Hi, We changed totem.token from 3s to 60s. Then something strange were observed, such as unexpected node offline. I read corosync.conf manpage, but still don't understand the reason. Can anyone explain this? or maybe our conf is broken? What corosync version are you using? Your config file is

[ClusterLabs] Antw: Re: Antw: Expected recovery behavior of remote-node guest when corosync ring0 is lost in a passive mode RRP config?

>>> "Scott Greenlese" schrieb am 07.03.2017 um 17:28 in Nachricht : [...] > > Maybe my question is... is there any way to facilitate an alternate Live > Guest Migration path in the event of