On 2016-09-20 09:53, Ken Gaillot wrote:
I do think ifdown is not quite the best failure simulation, since there
aren't that many real-world situation that merely take an interface
down. To simulate network loss (without pulling the cable), I think
maybe using the firewall to block all traffic to
On Tue, Sep 20, 2016 at 01:13:23PM +, Auer, Jens wrote:
> Hi,
>
> >> I've decided to create two answers for the two problems. The cluster
> >> still fails to relocate the resource after unloading the modules even
> >> with resource-agents 3.9.7
> > From the point of view of the resource agent,
nded in this message (or responsible for
> delivery of this message to such person), or you think for any reason that
> this message may have been addressed to you in error, you may not use or copy
> or deliver this message to anyone else. In such case, you should destroy this
> message
Hi,
>> I've decided to create two answers for the two problems. The cluster
>> still fails to relocate the resource after unloading the modules even
>> with resource-agents 3.9.7
> From the point of view of the resource agent,
> you configured it to use a non-existing network.
> Which it considers
On Tue, Sep 20, 2016 at 11:44:58AM +, Auer, Jens wrote:
> Hi,
>
> I've decided to create two answers for the two problems. The cluster
> still fails to relocate the resource after unloading the modules even
> with resource-agents 3.9.7
>From the point of view of the resource agent,
you config
.com]
Gesendet: Montag, 19. September 2016 16:36
An: Cluster Labs - All topics related to open-source clustering welcomed
Betreff: Re: [ClusterLabs] Virtual ip resource restarted on node with down
network device
Hi,
>> After the restart ifconfig still shows the device bond0 to be not
sage to anyone else. In such case, you should destroy this message and
are asked to notify the sender by reply e-mail.
Von: Ken Gaillot [kgail...@redhat.com]
Gesendet: Montag, 19. September 2016 17:31
An: users@clusterlabs.org
Betreff: Re: [ClusterLabs] Virt
ag, 19. September 2016 16:36
An: Cluster Labs - All topics related to open-source clustering welcomed
Betreff: Re: [ClusterLabs] Virtual ip resource restarted on node with down
network device
Hi,
>> After the restart ifconfig still shows the device bond0 to be not RUNNING:
>> M
On 09/19/2016 10:04 AM, Jan Pokorný wrote:
> On 19/09/16 10:18 +, Auer, Jens wrote:
>> Ok, after reading the log files again I found
>>
>> Sep 19 10:03:45 MDA1PFP-S01 crmd[7797]: notice: Initiating action 3: stop
>> mda-ip_stop_0 on MDA1PFP-PCS01 (local)
>> Sep 19 10:03:45 MDA1PFP-S01 crmd[7
On 19/09/16 10:18 +, Auer, Jens wrote:
> Ok, after reading the log files again I found
>
> Sep 19 10:03:45 MDA1PFP-S01 crmd[7797]: notice: Initiating action 3: stop
> mda-ip_stop_0 on MDA1PFP-PCS01 (local)
> Sep 19 10:03:45 MDA1PFP-S01 crmd[7797]: notice:
> MDA1PFP-PCS01-mda-ip_monitor_10
Von: Jan Pokorný [jpoko...@redhat.com]
Gesendet: Montag, 19. September 2016 14:57
An: Cluster Labs - All topics related to open-source clustering welcomed
Betreff: Re: [ClusterLabs] Virtual ip resource restarted on node with down
network device
On 19/0
On Mon, Sep 19, 2016 at 02:57:57PM +0200, Jan Pokorný wrote:
> On 19/09/16 09:15 +, Auer, Jens wrote:
> > After the restart ifconfig still shows the device bond0 to be not RUNNING:
> > MDA1PFP-S01 09:07:54 2127 0 ~ # ifconfig
> > bond0: flags=5123 mtu 1500
> > inet 192.168.120.20 netm
On 19/09/16 09:15 +, Auer, Jens wrote:
> After the restart ifconfig still shows the device bond0 to be not RUNNING:
> MDA1PFP-S01 09:07:54 2127 0 ~ # ifconfig
> bond0: flags=5123 mtu 1500
> inet 192.168.120.20 netmask 255.255.255.255 broadcast 0.0.0.0
> ether a6:17:2c:2a:72:f
to notify the sender by reply e-mail.
Von: Auer, Jens
Gesendet: Montag, 19. September 2016 12:08
An: Cluster Labs - All topics related to open-source clustering welcomed
Betreff: AW: [ClusterLabs] Virtual ip resource restarted on node with down
network
Hi,
> Would "rmmod " be a better hammer of choice?
I am just testing what happens in case of hardware/network issues. Any hammer
is good enough. Worst case would be that I unplug the machine, maybe with ILO.
I have created a simple testing setup of a two-node cluter with a virtual ip
and a pin
ed to notify the sender by reply e-mail.
Von: Jan Pokorný [jpoko...@redhat.com]
Gesendet: Freitag, 16. September 2016 23:13
An: users@clusterlabs.org
Betreff: Re: [ClusterLabs] Virtual ip resource restarted on node with down
network device
On 16/09/16 11:01 -0500, Ken Gaillo
On 16/09/16 11:01 -0500, Ken Gaillot wrote:
> On 09/16/2016 10:43 AM, Auer, Jens wrote:
>> thanks for the help.
>>
>>> I'm not sure what you mean by "the device the virtual ip is attached
>>> to", but a separate question is why the resource agent reported that
>>> restarting the IP was successful,
ssed to you in error, you may not use or copy
> or deliver this message to anyone else. In such case, you should destroy this
> message and are asked to notify the sender by reply e-mail.
>
> ____________
> Von: Ken Gaillot [kgail...@redhat.com]
>
and
are asked to notify the sender by reply e-mail.
Von: Ken Gaillot [kgail...@redhat.com]
Gesendet: Freitag, 16. September 2016 17:27
An: users@clusterlabs.org
Betreff: Re: [ClusterLabs] Virtual ip resource restarted on node with down
network device
On 09/1
On 09/16/2016 10:08 AM, Auer, Jens wrote:
> Hi,
>
> I have configured an Active/Passive cluster to host a virtual ip
> address. To test failovers, I shutdown the device the virtual ip is
> attached to and expected that it moves to the other node. However, the
> virtual ip is detected as FAILED, bu
Hi,
I have configured an Active/Passive cluster to host a virtual ip address. To
test failovers, I shutdown the device the virtual ip is attached to and
expected that it moves to the other node. However, the virtual ip is detected
as FAILED, but is then restarted on the same node. I was able to
21 matches
Mail list logo
