[Pacemaker] Problems after updating from debian squeeze to wheezy

2013-07-29 Thread Arnold Krille
Hi all, I have a little problem here and would like to get some help: I have (had?) a working three-node cluster of two active nodes (nebel1 and nebel2) and one standby-node (nebel3) running debian squeeze + backports. That is pacemaker 1.1.7-1~bpo60+1 and corosync 1.4.2-1~bpo60+1. Now I up

Re: [Pacemaker] Problems after updating from debian squeeze to wheezy

2013-07-29 Thread Arnold Krille
Am 2013-07-29 18:46, schrieb Arnold Krille: Hi all, I have a little problem here and would like to get some help: I have (had?) a working three-node cluster of two active nodes (nebel1 and nebel2) and one standby-node (nebel3) running debian squeeze + backports. That is pacemaker 1.1.7-1~bpo60+

Re: [Pacemaker] Problems after updating from debian squeeze to wheezy

2013-07-29 Thread Jelle de Jong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/07/13 20:58, Arnold Krille wrote: > So further testing show that the bonded interfaces below seem to > eat all broadcasts and all forwards (for the virtual machines). > Don't know why yet. But as soon as I switched my network-config to > use the

Re: [Pacemaker] Problems after updating from debian squeeze to wheezy

2013-07-29 Thread Oriol Mula-Valls
Hi, There is a bug already open: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697357 Kind regards, Oriol On 29/07/13 21:41, Jelle de Jong wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/07/13 20:58, Arnold Krille wrote: So further testing show that the bonded interfaces below

Re: [Pacemaker] Problems after updating from debian squeeze to wheezy

2013-07-30 Thread Arnold Krille
On Mon, 29 Jul 2013 22:24:52 +0200 Oriol Mula-Valls wrote: > There is a bug already open: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697357 Thanks for the link. I did a combination of the things written there: - I slightly changed my network-setup. Now its one active-passive bond to