Gönderim Listesi ecs-isp@2rosenthals.com Ar?vli ?leti #1260

Gönderen: "Massimo S." <ecs-isp@2rosenthals.com> Tam Ba?l?klar
Çözülmemi? ?leti
Konu: Re: [eCS-ISP] Updating bind
Tarih: Thu, 23 Oct 2025 10:03:38 +0200
Alacak: eCS ISP Mailing List <ecs-isp@2rosenthals.com>

Il 23/10/2025 09:46, Massimo S. ha scritto:


Il 23/10/2025 08:18, Steven Levine ha scritto:
In <list-14480631@2rosenthals.com>, on 10/19/25
    at 12:23 PM, "Massimo S." <ecs-isp@2rosenthals.com> said:

Hi,

Of course no, sometimes it "zombify" even 2 times per day and a reboot is
required. (I've a lot of dumps of the named process in this condition if
this can help). Process unkillable and unresponsive.

Rather than "of course no", I suspect you mean unfortunately no.  Dan's
dns servers stay up for weeks at a time.  His setup is not huge, but there
are more than 70 zone files.

some minutes ago, i received a notify from my fault-daemon
again bind on MTA1 has become unresponsibe and unkillable
i neither was connected to the vm..

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

...
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)

this is the fault-daemon that tried to restart bind since it was not
answering dns requests (the fault-daemon do a check each 5 minutes)

so i connected to the VM, i tried to kill it, but the process was unkillable
and i had to setboot /b

what was doing bind before the "unresponsibe+unkillable" state?
nothing special, just answering dns requests
there is no DDoS, i've examined the logs

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

it also do one or two daily scheduled restarts

i forgot, when this "unresponsible+unkillable" state happens
i don't get any popuplog.os2 or any exceptQ dump
just nothing

another detail, bind send output to syslogD, dunno if this can cause issues
syslogD writes output to a ram FS and to the screen

bind -V:

BIND 9.11.37 (Extended Support Version) <id:796133c>
running on OS/2 i386 1 2.45
built by make with '--prefix=/bind9' '--disable-shared' '--enable-static' '--enable-largefile' '--enable-threads' '--disable-ipv6' '--disable-chroot' '--with-openssl=/extras' '--with-dlopen=no' '--without-python' '--with-geoip=/extras' '--with-libjson=/extras' '--with-zlib=/extras' 'CC=gcc' 'LIBS=-llzma -lcx -lz -static-libgcc' 'PKG_CONFIG_PATH=u:/extras/lib/pkgconfig;e:/usr/lib/pkgconfig'
compiled by GCC 12.2.0
compiled with OpenSSL version: OpenSSL 1.1.1q  5 Jul 2022
linked to OpenSSL version: OpenSSL 1.1.1s  1 Nov 2022
compiled with libxml2 version: 2.6.19
linked to libxml2 version: 20900
compiled with libjson-c version: 0.11
linked to libjson-c version: 0.11
compiled with zlib version: 1.2.13
linked to zlib version: 1.2.13
threads support is enabled


build: bind-9.11.37-os2-20240704.zip

massimo

Abone ol: Bildirim, Derleme, Fihrist.
Abonelikten ç?k
Liste Sorumlusuna Postala