Bug#962454: Link failures after upgrade to +deb10u1

2020-07-04 Thread wferi
Alberto Gonzalez Iniesta writes: > Hi, again. After some days with libknet1=1.16-2, I'm still getting > errors from time to time (less than with buster's libknet1): > Jun 22 01:16:54 selma corosync[28610]: [KNET ] link: host: 1 link: 0 is > down > Jun 22 01:16:54 selma corosync[28610]:

Bug#962454: Link failures after upgrade to +deb10u1

2020-06-11 Thread 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

Bug#962454: Link failures after upgrade to +deb10u1

2020-06-11 Thread Valentin Vidic
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

Bug#962454: Link failures after upgrade to +deb10u1

2020-06-08 Thread Alberto Gonzalez Iniesta
Source: corosync Version: 3.0.1-2+deb10u1 Severity: important Hi, 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