[Debian-ha-maintainers] Bug#962454: Link failures after upgrade to +deb10u1

[Alberto Gonzalez Iniesta]

On Thu, Jun 11, 2020 at 10:59:06AM +0200, Valentin Vidic wrote:
> On Mon, Jun 08, 2020 at 12:29:35PM +0200, Alberto Gonzalez Iniesta wrote:
> > Some weeks ago I upgraded corosync (3.0.1-2 -> 3.0.1-2+deb10u1) and
> > started to notice these messages in my nodes (two node cluster):
> > Jun  2 01:10:13 patty corosync[2346]:   [KNET  ] link: host: 2 link: 0 is down
> > Jun  2 01:10:13 patty corosync[2346]:   [KNET  ] host: host: 2 (passive) best link: 1 (pri: 1)
> > Jun  2 01:10:14 patty corosync[2346]:   [KNET  ] rx: host: 2 link: 0 is up
> > Jun  2 01:10:14 patty corosync[2346]:   [KNET  ] host: host: 2 (passive) best link: 0 (pri: 1)
> > Jun  3 03:11:07 patty corosync[2346]:   [KNET  ] link: host: 2 link: 1 is down
> > Jun  3 03:11:07 patty corosync[2346]:   [KNET  ] host: host: 2 (passive) best link: 0 (pri: 1)
> > Jun  3 03:11:08 patty corosync[2346]:   [KNET  ] rx: host: 2 link: 1 is up
> > Jun  3 03:11:08 patty corosync[2346]:   [KNET  ] host: host: 2 (passive) best link: 0 (pri: 1)
> 
> Hi, can you confirm that downgrading to the previous version solves the
> link problem for you?
> 

Hi, I'll try that this weekend and keep you updated.

Thanks,
Alberto

-- 
Alberto Gonzalez Iniesta    | Formación, consultoría y soporte técnico
mailto/sip: agi at inittab.org | en GNU/Linux y software libre
Encrypted mail preferred    | http://inittab.com

Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D  4BF2 009B 3375 6B9A AA55