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 w

[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" > choose-your-brand-and-year-and-version shell, j

[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 could do a moderately complex shell scripts

[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 the > login shell, system s

[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 one would point to a gen

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 least,

[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 this operator (never

[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 it: Their VI was unabl

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

>>> Gabriele Bulfon schrieb am 29.08.2016 um 11:17 in Nachricht <3973483.545.1472462255112.JavaMail.sonicle@www>: > Hi Ken, > I have been talking with the illumos guys about the shell problem. > They all agreed that ksh (and specially the ksh93 used in illumos) is > absolutely Bourne-compatible,

[ClusterLabs] (no subject)

Hi folks, I'm assigned to system test Pacemaker/Corosync on the KVM on System Z platform with pacemaker-1.1.13-10 and corosync-2.3.4-7 . I have a cluster with 5 KVM hosts, and a total of 200 ocf:pacemakerVirtualDomain resources defined to run across the 5 cluster nodes (symmertical is true for

Re: [ClusterLabs] ocf scripts shell and local variables

On 08/29/2016 03:27 PM, Vladislav Bogdanov wrote: > Maybe #!/bin/ocfsh symlink provided by resource-agents package? ... and that's how lennartware ended up implementing its own syslog... -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc

Re: [ClusterLabs] ocf scripts shell and local variables

On August 29, 2016 11:07:39 PM GMT+03:00, Lars Ellenberg wrote: >On Mon, Aug 29, 2016 at 04:37:00PM +0200, Dejan Muhamedagic wrote: >> 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

Re: [ClusterLabs] ocf scripts shell and local variables

On Mon, Aug 29, 2016 at 04:37:00PM +0200, Dejan Muhamedagic wrote: > 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 this operator (never used!), don't know how hard it is > >

[ClusterLabs] generic 'initscript' resource agent that passes arguments?

I've got a number of scripts that are based on LSB compliant scripts, but which also accept arguments & values. For example, a script to manage multiple virtual machines has a command-line in the form: vbox_init --vmname $VMNAME [-d|--debug] [start|stop|status|restart] I'd like to manage

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

No ideas/inputs on this? Appreciate anything you guys can throw me here… Thank you! -- [ jR ] @: ja...@eramsey.org there is no path to greatness; greatness is the path From: Jason Ramsey Reply-To: Cluster Labs - All topics related to open-source clustering welcom

Re: [ClusterLabs] ocf scripts shell and local variables

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 variables' scope and retaining >> sanity at the same time. > > This prefixing approach

Re: [ClusterLabs] ip clustering strange behaviour

Ok, got it, I hadn't gracefully shut pacemaker on node2. Now I restarted, everything was up, stopped pacemaker service on host2 and I got host1 with both IPs configured. ;) But, though I understand that if I halt host2 with no grace shut of pacemaker, it will not move the IP2 to Host1, I don't ex

Re: [ClusterLabs] ip clustering strange behaviour

On 08/29/2016 05:18 PM, Gabriele Bulfon wrote: > Hi, > > now that I have IPaddr work, I have a strange behaviour on my test > setup of 2 nodes, here is my configuration: > > ===STONITH/FENCING=== > > primitive xstorage1-stonith stonith:external/ssh-sonicle op monitor > interval="25" timeout="25" st

[ClusterLabs] ip clustering strange behaviour

Hi, now that I have IPaddr work, I have a strange behaviour on my test setup of 2 nodes, here is my configuration: ===STONITH/FENCING=== primitive xstorage1-stonith stonith:external/ssh-sonicle op monitor interval="25" timeout="25" start-delay="25" params hostlist="xstorage1" primitive xstorage2-

Re: [ClusterLabs] ocf scripts shell and local variables

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 whatever the programmer tells them to. The point is none of them cares what

Re: [ClusterLabs] ocf scripts shell and local variables

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 of a version of python). Also, the question is about bash being a good option

Re: [ClusterLabs] ocf scripts shell and local variables

On 08/29/2016 09:43 AM, Dejan Muhamedagic wrote: > Hi, > > On Mon, Aug 29, 2016 at 08:47:43AM -0500, Ken Gaillot wrote: >> On 08/29/2016 04:17 AM, Gabriele Bulfon wrote: >>> Hi Ken, >>> >>> I have been talking with the illumos guys about the shell problem. >>> They all agreed that ksh (and special

Re: [ClusterLabs] ocf scripts shell and local variables

Hi, On Mon, Aug 29, 2016 at 08:47:43AM -0500, Ken Gaillot wrote: > On 08/29/2016 04:17 AM, Gabriele Bulfon wrote: > > Hi Ken, > > > > I have been talking with the illumos guys about the shell problem. > > They all agreed that ksh (and specially the ksh93 used in illumos) is > > absolutely Bourne-

Re: [ClusterLabs] ocf scripts shell and local variables

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 this operator (never used!), don't know how hard it is > to replace it with a standard version. Unfortunately, there's no command defi

Re: [ClusterLabs] data loss of network would cause Pacemaker exit abnormally

On 08/27/2016 09:15 PM, chenhj wrote: > Hi all, > > When i use the following command to simulate data lost of network at one > member of my 3 nodes Pacemaker+Corosync cluster, > sometimes it cause Pacemaker on another node exit. > > tc qdisc add dev eth2 root netem loss 90% > > Is there any me

Re: [ClusterLabs] Howto restart resource

On 08/29/2016 04:03 PM, Ken Gaillot wrote: > On 08/29/2016 01:38 AM, Stefano Ruberti wrote: >> Dear all, >> >> I have following situation and I need an advice from you: >> >> in my Active/Passive Cluster (Ubuntu_16.04 corosync + pacemaker , no pcs) >> >> Node_ANode_B >> Resource1Resou

Re: [ClusterLabs] Howto restart resource

On 08/29/2016 01:38 AM, Stefano Ruberti wrote: > Dear all, > > I have following situation and I need an advice from you: > > in my Active/Passive Cluster (Ubuntu_16.04 corosync + pacemaker , no pcs) > > Node_ANode_B > Resource1Resource1 > Resource2Resource2 > Resource3Resou

Re: [ClusterLabs] ocf scripts shell and local variables

On 08/29/2016 03:47 PM, Ken Gaillot wrote: > On 08/29/2016 04:17 AM, Gabriele Bulfon wrote: >> Hi Ken, >> >> I have been talking with the illumos guys about the shell problem. >> They all agreed that ksh (and specially the ksh93 used in illumos) is >> absolutely Bourne-compatible, and that the "loc

Re: [ClusterLabs] ocf scripts shell and local variables

On 08/29/2016 04:17 AM, Gabriele Bulfon wrote: > Hi Ken, > > I have been talking with the illumos guys about the shell problem. > They all agreed that ksh (and specially the ksh93 used in illumos) is > absolutely Bourne-compatible, and that the "local" variables used in the > ocf shells is not a B

Re: [ClusterLabs] ocf scripts shell and local variables

I think the main issue is the usage of the "local" operator in ocf* I'm not an expert on this operator (never used!), don't know how hard it is to replace it with a standard version. Happy to contribute, it still the case Gabriele ---

Re: [ClusterLabs] ocf scripts shell and local variables

Gabriele Bulfon writes: > Hi Ken, > I have been talking with the illumos guys about the shell problem. > They all agreed that ksh (and specially the ksh93 used in illumos) is > absolutely Bourne-compatible, and that the "local" variables used in the ocf > shells is not a Bourne syntax, but prob

Re: [ClusterLabs] ocf scripts shell and local variables

Hi Ken, I have been talking with the illumos guys about the shell problem. They all agreed that ksh (and specially the ksh93 used in illumos) is absolutely Bourne-compatible, and that the "local" variables used in the ocf shells is not a Bourne syntax, but probably a bash specific. This means tha

Re: [ClusterLabs] ocf scripts shell and local variables

Thanks, though this does not work :) Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon

Re: [ClusterLabs] data loss of network would cause Pacemaker exit abnormally

On 08/28/2016 04:15 AM, chenhj wrote: > Hi all, > > When i use the following command to simulate data lost of network at > one member of my 3 nodes Pacemaker+Corosync cluster, > sometimes it cause Pacemaker on another node exit. > > tc qdisc add dev eth2 root netem loss 90% > > Is there any metho