libuv-1.50.0 breaks bind 9.20 (again)

PatchyFog

PatchyFog

Thought I'd start a new thread to get more eyes on this. This is a continuation of the saga in this thread. Essentially, some problem back in November 2024 in libuv-1.49.0 and 1.49.1 would cause bind 9.20 to abort on initialization:

Code: 
04-Nov-2024 21:14:54.288 the limit on open files is already at the maximum allowed value: 87300
04-Nov-2024 21:14:54.288 found 2 CPUs, using 2 worker threads
04-Nov-2024 21:14:54.288 loop.c:201:loop_init(): fatal error:
04-Nov-2024 21:14:54.288 uv_loop_init failed: operation not supported on socket
04-Nov-2024 21:14:54.288 exiting (due to fatal error in library)
Abort trap

However, libuv-1.49.2 worked fine.

And now the new 1.50.0 that I installed from /latest on 26 Jan 25 has broken things again, 1 line later:

Code: 
03-Feb-2025 20:07:13.757 ----------------------------------------------------
03-Feb-2025 20:07:13.757 the limit on open files is already at the maximum allowed value: 87300
03-Feb-2025 20:07:13.757 found 2 CPUs, using 2 worker threads
03-Feb-2025 20:07:13.757 loop.c:202:loop_init(): fatal error:
03-Feb-2025 20:07:13.757 uv_loop_init failed: operation not supported on socket
03-Feb-2025 20:07:13.757 exiting (due to fatal error in library)
Abort trap

To get my bind up again I downgraded and locked to 1.49.2

pkg info -r libuv
libuv-1.49.2:
bind920-9.20.4
bind-tools-9.20.4
 
dns/bind918 doesn't seem to have a problem with libuv-1.50, or at least I haven't encountered any issues:
Code: 
root@maelcum:~ # pkg version -vRx bind
Updating dicelan repository catalogue...
dicelan repository is up to date.
All repositories are up to date.
bind-tools-9.20.4                  =   up-to-date with remote
bind918-9.18.32                    =   up-to-date with remote
root@maelcum:~ # pkg version -vRx libuv
Updating dicelan repository catalogue...
dicelan repository is up to date.
All repositories are up to date.
libuv-1.50.0                       =   up-to-date with remote
root@maelcum:~ # ps -ax | grep named
 2054  -  Ss       0:01.41 /usr/sbin/syslogd -l /var/run/log -l /var/named/var/run/log -s -cc
 2163  -  Is       4:20.92 /usr/local/sbin/named -t /var/named -u bind -c /usr/local/etc/namedb/named.conf
60230  1  S+       0:00.00 grep named
 
I have a production DNS cache at work in a secured network that is failing to load named. Using packages and not ports. Upgraded to 13.5-RELEASE today from 11.4-RELEASE which went without a hitch. The old version of named from bind916-9.16.8 started fine after the reboot. As soon as I upgraded to bind920-9.20.8 and tried to start named the trouble began. Due to company security policy I cannot build or install a custom port on this box, although I might be able to get an exception if I am forced to to solve the problem. In any case, it appears from web searches this problem appears with BIND port builds as well. Assistance getting this back up and running would be much appreciated. Output from the host in question:

Code: 
# freebsd-version -kru
13.5-RELEASE
13.5-RELEASE
13.5-RELEASE-p1

# service named start
Starting named.
/usr/local/etc/rc.d/named: WARNING: failed to start named

# pkg info|grep ^bind
bind-tools-9.20.8              Command line tools from BIND: delv, dig, host, nslookup...
bind920-9.20.8                 BIND DNS suite with updated DNSSEC and DNS64

# pkg info|grep libuv
libuv-1.50.0                   Multi-platform support library with a focus on asynchronous I/O

# tail -5 /var/log/messages
May 13 15:50:23 osssmecdnsvm-2 named[3371]: loop.c:203:loop_init(): fatal error:
May 13 15:50:23 osssmecdnsvm-2 named[3371]: uv_loop_init failed: no such file or directory
May 13 15:50:23 osssmecdnsvm-2 named[3371]: exiting (due to fatal error in library)
May 13 15:50:23 osssmecdnsvm-2 ealexander[3375]: /usr/local/etc/rc.d/named: WARNING: failed to start named
May 13 15:50:23 osssmecdnsvm-2 kernel: pid 3371 (named), jid 0, uid 0: exited on signal 6
 
I attempted to use the package bind918 which is mentioned above as working. Still no joy, although it does give a slightly different error.
Code: 
# service named start
Starting named.
/usr/local/etc/rc.d/named: WARNING: failed to start named

# tail -5 /var/log/messages
May 14 05:20:42 osssmecdnsvm-2 named[5195]: netmgr/netmgr.c:302:isc__netmgr_create(): fatal error:
May 14 05:20:42 osssmecdnsvm-2 named[5195]: uv_loop_init failed: no such file or directory
May 14 05:20:42 osssmecdnsvm-2 named[5195]: exiting (due to fatal error in library)
May 14 05:20:42 osssmecdnsvm-2 ealexander[5199]: /usr/local/etc/rc.d/named: WARNING: failed to start named
May 14 05:20:42 osssmecdnsvm-2 kernel: pid 5195 (named), jid 0, uid 0: exited on signal 6

# pkg info -r libuv
libuv-1.50.0:
        bind918-9.18.36
        bind-tools-9.20.8
        bind-tools-9.20.8 (libuv.so.1)
        bind918-9.18.36 (libuv.so.1)
An attempt to revert to the previous packages failed, which is not surprising.
Code: 
# pkg add /var/cache/pkg/libuv-1.40.0.txz /var/cache/pkg/bind916-9.16.8.txz /var/cache/pkg/bind-tools-9.16.8.txz
Installing libuv-1.40.0...
pkg: wrong architecture: FreeBSD:11:amd64 instead of FreeBSD:13:amd64
Installing bind916-9.16.8...
pkg: wrong architecture: FreeBSD:11:amd64 instead of FreeBSD:13:amd64
Installing bind-tools-9.16.8...
pkg: wrong architecture: FreeBSD:11:amd64 instead of FreeBSD:13:amd64

Failed to install the following 3 package(s): /var/cache/pkg/libuv-1.40.0.txz, /var/cache/pkg/bind916-9.16.8.txz, /var/cache/pkg/bind-tools-9.16.8.txz
After that I installed bind920 again and am back where I started.
Code: 
# tail -6 /var/log/messages
May 14 05:35:06 osssmecdnsvm-2 named[5304]: the limit on open files is already at the maximum allowed value: 57897
May 14 05:35:06 osssmecdnsvm-2 named[5304]: loop.c:203:loop_init(): fatal error: 
May 14 05:35:06 osssmecdnsvm-2 named[5304]: uv_loop_init failed: no such file or directory
May 14 05:35:06 osssmecdnsvm-2 named[5304]: exiting (due to fatal error in library)
May 14 05:35:06 osssmecdnsvm-2 ealexander[5308]: /usr/local/etc/rc.d/named: WARNING: failed to start named
May 14 05:35:06 osssmecdnsvm-2 kernel: pid 5304 (named), jid 0, uid 0: exited on signal 6

# pkg info -r libuv
libuv-1.50.0:
        bind920-9.20.8
        bind-tools-9.20.8
        bind-tools-9.20.8 (libuv.so.1)
        bind920-9.20.8 (libuv.so.1)
I found this bug report from last year that shows this is supposedly fixed, but it is not fixed for me: PR 282088 An assist as to what else I can try would be welcome.
 
You must log in or register to reply here.
Back
Top