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:
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:
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
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