Re: bind on fbsd no longer starting

2024-10-14 Thread Christoph Moench-Tegeder
## Kurt Jaeger (bind-us...@opsec.eu): > 14-Oct-2024 21:49:18.566 netmgr/netmgr.c:302:isc__netmgr_create(): fatal > error: > 14-Oct-2024 21:49:18.566 uv_loop_init failed: no such file or directory > 14-Oct-2024 21:49:18.566 exiting (due to fatal error in library) Check if your chroot has a /dev/

bind on fbsd no longer starting

2024-10-14 Thread Kurt Jaeger
Hi! when I try to start bind 9.18.30 from the ports tree, build for fbsd 14.1p5, I get this error: 14-Oct-2024 21:49:18.566 netmgr/netmgr.c:302:isc__netmgr_create(): fatal error: 14-Oct-2024 21:49:18.566 uv_loop_init failed: no such file or directory 14-Oct-2024 21:49:18.566 exiting (due to fata

Re: FYI: FreeBSD: upgrade to protobuf-c 1.4.1_6 breaks dig

2024-10-14 Thread Peter
On Mon, Oct 14, 2024 at 06:10:20AM -0700, Steve Rikli wrote: ! On Mon, Oct 14, 2024 at 07:19:06AM +0200, Peter wrote: ! > On Sun, Oct 13, 2024 at 10:55:52PM +0100, Niall O'Reilly wrote: ! > ! FYI only. I've submitted a [bug report][] to the FreeBSD Bugzilla. ! > ! > ! After upgrading to 1.4.1_6,

Re: bind on fbsd no longer starting

2024-10-14 Thread Kurt Jaeger
Hi! > when I try to start bind 9.18.30 from the ports tree, build > for fbsd 14.1p5, I get this error: [...] > 14-Oct-2024 22:14:14.515 compiled with libuv version: 1.49.1 Downgrading libuv to 1.48.0 seems to fix the startup problem. See: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282088

Re: bind on fbsd no longer starting

2024-10-14 Thread Christoph Moench-Tegeder
## Kurt Jaeger (bind-us...@opsec.eu): > > 14-Oct-2024 22:14:14.515 compiled with libuv version: 1.49.1 > Downgrading libuv to 1.48.0 seems to fix the startup problem. I just re-checked so I can absolutely not confirm it would be a general libuv problem: Oct 15 00:00:17 disconnector named[56975]:

Re: FYI: FreeBSD: upgrade to protobuf-c 1.4.1_6 breaks dig

2024-10-14 Thread Niall O'Reilly
On 14 Oct 2024, at 6:19, Peter wrote: > I cannot reproduce: Thanks. I've been made aware, off list, of people who can. One of these has let me know that, for them, re-installing bind[-tools] instead of downgrading protobuf[-c] cleared the problem. /Niall -- Visit https://lists.isc.org/mailman

Re: FYI: FreeBSD: upgrade to protobuf-c 1.4.1_6 breaks dig

2024-10-14 Thread Peter
On Mon, Oct 14, 2024 at 11:26:58AM +0100, Niall O'Reilly wrote: ! On 14 Oct 2024, at 6:19, Peter wrote: ! ! > I cannot reproduce: ! ! Thanks. I've been made aware, off list, of people who can. Interesting. I for my part do normally not link dig against protobuf at all: $ pkg info bind-tools |

Re: FYI: FreeBSD: upgrade to protobuf-c 1.4.1_6 breaks dig

2024-10-14 Thread Steve Rikli
On Mon, Oct 14, 2024 at 07:19:06AM +0200, Peter wrote: > On Sun, Oct 13, 2024 at 10:55:52PM +0100, Niall O'Reilly wrote: > ! FYI only. I've submitted a [bug report][] to the FreeBSD Bugzilla. > > ! After upgrading to 1.4.1_6, I see: > ! > ! ``` > ! grab(maint)$ uname -a > ! FreeBSD grab.no8.be 1

Re: FYI: FreeBSD: upgrade to protobuf-c 1.4.1_6 breaks dig

2024-10-14 Thread Steve Rikli
On Mon, Oct 14, 2024 at 01:42:28PM +0200, Peter wrote: > On Mon, Oct 14, 2024 at 11:26:58AM +0100, Niall O'Reilly wrote: > ! On 14 Oct 2024, at 6:19, Peter wrote: > ! > ! > I cannot reproduce: > ! > ! Thanks. I've been made aware, off list, of people who can. > > Interesting. > I for my part do