In <list-14541197@2rosenthals.com>, on 10/23/25
    at 09:46 AM, "Massimo S." <ecs-isp@2rosenthals.com> said:

Hi Massimo,

at 9:17 syslog (from bind) wrote this:

Which syslog daemon are you running?  I use syslogd.exe from the
syslog3a.zip archive.  I find it to be more stable than the IBM supplied
syslog.

could not listen on UDP socket: address in use
creating IPv4 inteface failed; interface ignored
not listing on any interface
unable to listen on any interface
loading configuration: failure
exiting (due to fatal error)

Odd.  If this happens again, I recommend you do a netstat -s and look at
the socket count just in case that the reason.

if this can help, the same bind build on the other VM 2 cores is not
showing the issue (this VM instead has 8 cores assigned), dunno if this
is due to SMP

An SMP race condition is always a possibility, especially on faster
systems with lots of cores.

You can always try marking named.exe as MPUNSAFE and see if this helps.

Steven