Re: [ClusterLabs] "VirtualDomain is active on 2 nodes" due to transient network failure

Hi, On Tue, Aug 30, 2016 at 10:03 PM, Scott Greenlese wrote: > Added an appropriate subject line (was blank). Thanks... > > > Scott Greenlese ... IBM z/BX Solutions Test, Poughkeepsie, N.Y. > INTERNET: swgre...@us.ibm.com > PHONE: 8/293-7301 (845-433-7301) M/S: POK

[ClusterLabs] "VirtualDomain is active on 2 nodes" due to transient network failure

Added an appropriate subject line (was blank). Thanks... Scott Greenlese ... IBM z/BX Solutions Test, Poughkeepsie, N.Y. INTERNET: swgre...@us.ibm.com PHONE: 8/293-7301 (845-433-7301)M/S: POK 42HA/P966 - Forwarded by Scott Greenlese/Poughkeepsie/IBM on 08/30/2016 03:59 PM

Re: [ClusterLabs] ocf scripts shell and local variables

On 08/30/2016 11:15 AM, Dejan Muhamedagic wrote: > I suppose that it is explained in enough detail here: > > https://en.wikipedia.org/wiki/Shebang_(Unix) I expect you're being deliberately obtuse. It does not explain which program loader interprets line 1 of findif.sh: "#!/bin/sh" when it is

Re: [ClusterLabs] ocf scripts shell and local variables

On Tue, Aug 30, 2016 at 06:15:49PM +0200, Dejan Muhamedagic wrote: > On Tue, Aug 30, 2016 at 10:08:00AM -0500, Dmitri Maziuk wrote: > > On 2016-08-30 03:44, Dejan Muhamedagic wrote: > > > > >The kernel reads the shebang line and it is what defines the > > >interpreter which is to be invoked to

Re: [ClusterLabs] ocf scripts shell and local variables

On Tue, Aug 30, 2016 at 10:08:00AM -0500, Dmitri Maziuk wrote: > On 2016-08-30 03:44, Dejan Muhamedagic wrote: > > >The kernel reads the shebang line and it is what defines the > >interpreter which is to be invoked to run the script. > > Yes, and does the kernel read when the script is source'd

[ClusterLabs] Service pacemaker start kills my cluster and other NFS HA issues

Hello, I have set up a DRBD-Corosync-Pacemaker cluster following the instructions from https://wiki.ubuntu.com/ClusterStack/Natty adapting them to CentOS 7 (e.g: using systemd). After testing it in Virtual Machines it seemed to be working fine, so it is now implemented in physical machines,

Re: [ClusterLabs] ocf scripts shell and local variables

On 2016-08-30 03:44, Dejan Muhamedagic wrote: The kernel reads the shebang line and it is what defines the interpreter which is to be invoked to run the script. Yes, and does the kernel read when the script is source'd or executed via any of the mechanisms that have the executable specified

Re: [ClusterLabs] ocf scripts shell and local variables

illumos (and Solaris 11) delivers ksh93, that is fully Bourn compatible, but not with the bash extension of "local" variables, that is not Bourn shell. It is supported in ksh93 with the "typedef" operator, instead of "local". This is used inside the "ocf-*" scripts. Gabriele

Re: [ClusterLabs] ocf scripts shell and local variables

Not RA, but ocf-* do, because of the "local" operator usage. Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon

Re: [ClusterLabs] ocf scripts shell and local variables

Hi, On Mon, Aug 29, 2016 at 05:08:35PM +0200, Gabriele Bulfon wrote: > Sure, infact I can change all shebang to point to /bin/bash and it's ok. > The question is about current shebang /bin/sh which may go into trouble (as > if one would point to a generic python but uses many specific features

Re: [ClusterLabs] systemd RA start/stop delays

Hi, On Thu, Aug 18, 2016 at 09:00:24AM -0500, Ken Gaillot wrote: > On 08/17/2016 08:17 PM, TEG AMJG wrote: > > Hi > > > > I am having a problem with a simple Active/Passive cluster which > > consists in the next configuration > > > > Cluster Name: kamcluster > > Corosync Nodes: > > kam1vs3

Re: [ClusterLabs] ip clustering strange behaviour

Then it is probably the default for no-quorum-policy (=stop) On 08/30/2016 08:52 AM, Gabriele Bulfon wrote: > Sorry for reiterating, but my main question was: > > why does node 1 removes its own IP if I shut down node 2 abruptly? > I understand that it does not take the node 2 IP (because the >

Re: [ClusterLabs] ocf scripts shell and local variables

Hi, On Mon, Aug 29, 2016 at 10:13:18AM -0500, Dmitri Maziuk wrote: > On 2016-08-29 04:06, Gabriele Bulfon wrote: > >Thanks, though this does not work :) > > Uhm... right. Too many languages, sorry: perl's system() will call the login > shell, system system() uses /bin/sh, and exec()s will run

Re: [ClusterLabs] Antw: Re: ocf scripts shell and local variables

On Tue, Aug 30, 2016 at 08:09:34AM +0200, Ulrich Windl wrote: > >>> Dejan Muhamedagic schrieb am 29.08.2016 um 16:37 in > Nachricht <20160829143700.GA1538@tuttle.homenet>: > > Hi, > > > > On Mon, Aug 29, 2016 at 02:58:11PM +0200, Gabriele Bulfon wrote: > >> I think the main

Re: [ClusterLabs] ocf scripts shell and local variables

Hi, On Tue, Aug 30, 2016 at 09:32:54AM +0200, Kristoffer Grönlund wrote: > Jehan-Guillaume de Rorthais writes: > > > On Mon, 29 Aug 2016 10:02:28 -0500 > > Ken Gaillot wrote: > > > >> On 08/29/2016 09:43 AM, Dejan Muhamedagic wrote: > > ... > >>> I doubt

Re: [ClusterLabs] ocf scripts shell and local variables

Jehan-Guillaume de Rorthais writes: > On Mon, 29 Aug 2016 10:02:28 -0500 > Ken Gaillot wrote: > >> On 08/29/2016 09:43 AM, Dejan Muhamedagic wrote: > ... >>> I doubt that we could do a moderately complex shell scripts >>> without capability of limiting the

Re: [ClusterLabs] ip clustering strange behaviour

Sorry for reiterating, but my main question was: why does node 1 removes its own IP if I shut down node 2 abruptly? I understand that it does not take the node 2 IP (because the ssh-fencing has no clue about what happened on the 2nd node), but I wouldn't expect it to shut down its own IP...this

[ClusterLabs] Antw: Re: ocf scripts shell and local variables

>>> Lars Ellenberg schrieb am 29.08.2016 um 22:07 in Nachricht <20160829200739.GQ5268@soda.linbit>: [...] > And no, I strongly do not think that we should "fall back" to the > "art" of shell syntax and idioms that was force on you by the original" >

[ClusterLabs] Antw: Re: ocf scripts shell and local variables

>>> Jehan-Guillaume de Rorthais schrieb am 29.08.2016 um >>> 18:04 in Nachricht <20160829180440.5b7f1a2e@firost>: > On Mon, 29 Aug 2016 10:02:28 -0500 > Ken Gaillot wrote: > >> On 08/29/2016 09:43 AM, Dejan Muhamedagic wrote: > ... >>> I doubt that we

[ClusterLabs] Antw: Re: ocf scripts shell and local variables

>>> Dmitri Maziuk schrieb am 29.08.2016 um 17:13 in Nachricht <161a5209-166c-e837-dcb0-169b8a4b3...@gmail.com>: > On 2016-08-29 04:06, Gabriele Bulfon wrote: >> Thanks, though this does not work :) > > Uhm... right. Too many languages, sorry: perl's system() will call

[ClusterLabs] Antw: Re: ocf scripts shell and local variables

>>> Gabriele Bulfon schrieb am 29.08.2016 um 17:08 in Nachricht <14184995.610.1472483315074.JavaMail.sonicle@www>: > Sure, infact I can change all shebang to point to /bin/bash and it's ok. > The question is about current shebang /bin/sh which may go into trouble (as > if

Re: [ClusterLabs] Node Fencing and STONITH in Amazon Web Services

Hi, Am 26.08.2016 um 22:32 schrieb Jason A Ramsey: > No users > would be connecting to the severed instances, but background and system > tasks would proceed as normal, potentially writing new data to the > databases making rejoining the nodes to the cluster a little bit tricky > to say the

[ClusterLabs] Antw: Re: ocf scripts shell and local variables

>>> Dejan Muhamedagic schrieb am 29.08.2016 um 16:37 in Nachricht <20160829143700.GA1538@tuttle.homenet>: > Hi, > > On Mon, Aug 29, 2016 at 02:58:11PM +0200, Gabriele Bulfon wrote: >> I think the main issue is the usage of the "local" operator in ocf* >> I'm not an expert on

[ClusterLabs] Antw: Re: ocf scripts shell and local variables

>>> Ken Gaillot schrieb am 29.08.2016 um 15:47 in >>> Nachricht <8ca22867-2103-b2da-316b-ac97234f8...@redhat.com>: > On 08/29/2016 04:17 AM, Gabriele Bulfon wrote: [...] > > Interesting, I thought local was posix, but it's not. It seems everyone > but solaris implemented