Re: BIND 9.16.1 failing assertion

2020-04-16 Thread Greg Rivers
> Yup, that borked our entire environment today. Shame on my for not testing > in non-prod first :( > > Fell back to 9.14 on FreeBSD for now. > Note that the libuv issue was seen (and fixed) on FreeBSD -CURRENT recently: . I'm not aware

Re: BIND 9.16.1 failing assertion

2020-04-16 Thread arlac77
Thanks, downgrading libuv to libuv 1.35.0-1 resolved the issue -- Sent from: http://bind-users-forum.2342410.n4.nabble.com/ ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list

Re: BIND 9.16.1 failing assertion

2020-04-16 Thread Tim Daneliuk
On 4/16/20 5:03 PM, arlac77 wrote: > Hello, > i am using > > BIND 9.16.1 (Stable Release) > > on > > Linux odroid1 4.14.173-1-ARCH #1 SMP PREEMPT Sun Mar 22 14:06:09 UTC 2020 > armv7l GNU/Linux > > > after a few seconds of operation bind dumps with: > > 16-Apr-2020 23:39:01.633

Re: BIND 9.16.1 failing assertion

2020-04-16 Thread Mark Andrews
This appears to libuv version related. We have had a couple of reports in the last couple of days. Roll back one version of libuv until we manage to isolate the issue. > On 17 Apr 2020, at 08:03, arlac77 wrote: > > Hello, > i am using > > BIND 9.16.1 (Stable Release) > > on > > Linux

BIND 9.16.1 failing assertion

2020-04-16 Thread arlac77
Hello, i am using BIND 9.16.1 (Stable Release) on Linux odroid1 4.14.173-1-ARCH #1 SMP PREEMPT Sun Mar 22 14:06:09 UTC 2020 armv7l GNU/Linux after a few seconds of operation bind dumps with: 16-Apr-2020 23:39:01.633 netmgr.c:1000: REQUIRE(worker->recvbuf_inuse) failed 16-Apr-2020