Seeing the high dropping quote... (just compare this to the other NIC) - have
you tried a new cable? Maybe it's a cheap hardware problem...
-Ursprüngliche Nachricht-
Von: linux-ha-boun...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] Im Auftrag von Lars Marowsky-Bree
Hi Dejan,
It seems like resource restart does not work any longer.
# crm resource restart test01-vm
INFO: ordering test01-vm to stop
Traceback (most recent call last):
File /usr/sbin/crm, line 44, in module
main.run()
File /usr/lib64/python2.6/site-packages/crmsh/main.py, line 442, in
12.07.2013 12:06, Vladislav Bogdanov wrote:
Hi Dejan,
It seems like resource restart does not work any longer.
Ah, this seems to be fixed by bb39cce17f20. Sorry for noise.
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
On 2013-07-12T11:05:32, Wengatz Herbert herbert.weng...@baaderbank.de wrote:
Seeing the high dropping quote... (just compare this to the other NIC) - have
you tried a new cable? Maybe it's a cheap hardware problem...
The drop rate is normal. A slave NIC in a bonded active/passive
Hmmm.
Please correct me, if I'm wrong:
As I understand it, you have a number of packets, that go to BOTH NICs.
Depending, on which one is the active or the passive one, the sum of all
dropped packets should be equal to the number of received packets (plusminus
some drops for other reasons). So
Hi,
On Fri, Jul 12, 2013 at 12:08:12PM +0300, Vladislav Bogdanov wrote:
12.07.2013 12:06, Vladislav Bogdanov wrote:
Hi Dejan,
It seems like resource restart does not work any longer.
Yes, I still wonder how did that one slip.
Ah, this seems to be fixed by bb39cce17f20. Sorry for noise.
Vladislav Bogdanov bub...@hoster-ok.com schrieb am 12.07.2013 um 11:06 in
Nachricht 51dfc715.2030...@hoster-ok.com:
Hi Dejan,
It seems like resource restart does not work any longer.
BTW: The way resource restart is implemented (i.e.: stop wait, then start)
has a major problem: If stop
Lars Marowsky-Bree l...@suse.com schrieb am 12.07.2013 um 11:08 in
Nachricht
20130712090853.gm19...@suse.de:
On 2013-07-12T11:05:32, Wengatz Herbert herbert.weng...@baaderbank.de
wrote:
Seeing the high dropping quote... (just compare this to the other NIC) -
have
you tried a new cable?
01.07.2013 17:29, Vladislav Bogdanov wrote:
Hi,
I'm trying to look if it is now safe to delete non-running nodes
(corosync 2.3, pacemaker HEAD, crmsh tip).
# crm node delete v02-d
WARNING: 2: crm_node bad format: 7 v02-c
WARNING: 2: crm_node bad format: 8 v02-d
WARNING: 2: crm_node bad
On 2013-07-12T12:19:40, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote:
BTW: The way resource restart is implemented (i.e.: stop wait, then
start) has a major problem: If stop causes to fence the node where the crm
command is running, the resource will remain stopped even after the
Wengatz Herbert herbert.weng...@baaderbank.de schrieb am 12.07.2013 um
11:19
in Nachricht e0a8d3556d452c42977202b2d60934660431fae...@msx2.baag:
Hmmm.
Please correct me, if I'm wrong:
As I understand it, you have a number of packets, that go to BOTH NICs.
Depending, on which one is the
Lars Marowsky-Bree l...@suse.com schrieb am 12.07.2013 um 12:23 in
Nachricht
20130712102340.go19...@suse.de:
On 2013-07-12T12:19:40, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de
wrote:
BTW: The way resource restart is implemented (i.e.: stop wait, then
start) has a major problem: If
On 2013-07-12T12:26:18, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de wrote:
(Another way to trigger a restart is to modify the instance parameters.
Set __manual_restart=1 and it'll restart.)
once? ;-)
Keep increasing it. ;-)
--
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff
On 12/07/2013, at 8:23 PM, Vladislav Bogdanov bub...@hoster-ok.com wrote:
01.07.2013 17:29, Vladislav Bogdanov wrote:
Hi,
I'm trying to look if it is now safe to delete non-running nodes
(corosync 2.3, pacemaker HEAD, crmsh tip).
# crm node delete v02-d
WARNING: 2: crm_node bad format:
Hi,
I wanted to add new node into CIB in advance, before it is powered on
(to power it on in a standby mode while cl#5169 is not implemented).
So, I did
==
[root@vd01-a tmp]# cat u
node $id=4 vd01-d \
attributes standby=on virtualization=true
[root@vd01-a tmp]# crm configure load
On 12/07/2013, at 8:23 PM, Lars Marowsky-Bree l...@suse.com wrote:
On 2013-07-12T12:19:40, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de
wrote:
BTW: The way resource restart is implemented (i.e.: stop wait, then
start) has a major problem: If stop causes to fence the node where the crm
16 matches
Mail list logo