Re: [ClusterLabs] [solved] heartbeat/anything Resource Agent : "wait for proper service before ending the start operation"

Le vendredi 13 avril 2018 à 11:15 +0200, Oyvind Albrigtsen a écrit : > On 13/04/18 11:07 +0200, Nicolas Huillard wrote: > > I figured that fixing this would require to add a monitor call > > inside the start operation, and wait for a successful monitor > > before returnin

Re: [ClusterLabs] heartbeat/anything Resource Agent : "wait for proper service before ending the start operation"

Le vendredi 13 avril 2018 à 11:59 +0200, Oyvind Albrigtsen a écrit : > On 13/04/18 11:53 +0200, Nicolas Huillard wrote: > > Le vendredi 13 avril 2018 à 11:15 +0200, Oyvind Albrigtsen a > > écrit : > > The issue here is the monitor will at first return a "fail"

Re: [ClusterLabs] heartbeat/anything Resource Agent : "wait for proper service before ending the start operation"

Le vendredi 13 avril 2018 à 11:15 +0200, Oyvind Albrigtsen a écrit : > On 13/04/18 11:07 +0200, Nicolas Huillard wrote: > > One of my resources is a pppd process, which is started with the > > heartbeat/anything RA. That RA just spawn the pppd process with the > > correct

[ClusterLabs] heartbeat/anything Resource Agent : "wait for proper service before ending the start operation"

ition" Resource Agent? Using Pacemaker 1.1.16 on Debian stretch. -- Nicolas Huillard ___ Users mailing list: Users@clusterlabs.org https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting sta

Re: [ClusterLabs] boothd-site/boothd-arbitrator: WARN: packet timestamp older than previous one

y eventually do it on the arbitrator (which unfortunately is also the machine less prone to trigger those warnings). I'll try to add the time-diff, to check if it is 0 or less when the warning appears. In the mean time, I'll just ignore those warnings. Thank you very much! -- Nicolas Huill

Re: [ClusterLabs] boothd-site/boothd-arbitrator: WARN: packet timestamp older than previous one

Le mardi 07 novembre 2017 à 13:41 +0100, Dejan Muhamedagic a écrit : > Hi, > > On Mon, Nov 06, 2017 at 10:52:12AM +0100, Nicolas Huillard wrote: > > Hello, > > > > I have many of those above syslog messages from boothd (counting > > all servers, that's nearly

[ClusterLabs] boothd-site/boothd-arbitrator: WARN: packet timestamp older than previous one

: Fllw -> Fllw Nov 06 10:32:21 arbitrator boothd-arbitrator: [9237]: debug: process_UPDATE:380: ticket-web (Fllw/3/298999): ticket leader set to [siteBIP] Nov 06 10:32:21 arbitrator boothd-arbitrator: [9237]: debug: log_next_wakeup:1182: ticket-web (Fllw/3/298999): set ticket wakeup in 298.999 -- Ni

Re: [ClusterLabs] Configuring booth for multi-site cluster

Thanks all, -- Nicolas Huillard ___ Users mailing list: Users@clusterlabs.org http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf

Re: [ClusterLabs] Configuring booth for multi-site cluster

trator= IPs be > > the > > internal virtual IPs, or DMZ IPs, or something else entirely ? > > Well, however the sites address each other ;-) Both sites can address each other in a symmetric way (I'll choose the exact fashion in time then), but the arbitrator is an outlier with it'

[ClusterLabs] Configuring booth for multi-site cluster

rator= IPs be the internal virtual IPs, or DMZ IPs, or something else entirely ? TIA, -- Nicolas Huillard ___ Users mailing list: Users@clusterlabs.org http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getti