bind/named dying after 24-48 hrs. "assertion failure"?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



All,

  Has anyone else encountered a bind 9.13.4-1/named daemon dying with
"assertion failure" in the past week. I have encountered the problem twice.
When named dies, status reports:

● named.service - Internet domain name server
   Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor
preset: disabled)
   Active: failed (Result: signal) since Thu 2018-12-06 10:35:51 CST; 15h ago
  Process: 23007 ExecStart=/usr/bin/named -f -u named (code=killed, signal=ABRT)
 Main PID: 23007 (code=killed, signal=ABRT)

Dec 06 10:35:51 phoinix named[23007]: #1 0x7f078ea0fcaa in ??
Dec 06 10:35:51 phoinix named[23007]: #2 0x7f078ebc295b in ??
Dec 06 10:35:51 phoinix named[23007]: #3 0x7f078ebc806e in ??
Dec 06 10:35:51 phoinix named[23007]: #4 0x7f078ebcbaba in ??
Dec 06 10:35:51 phoinix named[23007]: #5 0x7f078ea2f349 in ??
Dec 06 10:35:51 phoinix named[23007]: #6 0x7f078df1ea9d in ??
Dec 06 10:35:51 phoinix named[23007]: #7 0x7f078de4eb23 in ??
Dec 06 10:35:51 phoinix named[23007]: exiting (due to assertion failure)
Dec 06 10:35:51 phoinix systemd[1]: named.service: Main process exited,
code=killed, status=6/ABRT
Dec 06 10:35:51 phoinix systemd[1]: named.service: Failed with result 'signal'.

  This hasn't happened before. A simple restart makes it happy again -- but
for how long?

 # systemctl start named
● named.service - Internet domain name server
   Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor
preset: disabled)
   Active: active (running) since Fri 2018-12-07 02:04:03 CST; 4s ago
 Main PID: 26487 (named)
    Tasks: 10 (limit: 4915)
   Memory: 15.5M
   CGroup: /system.slice/named.service
           └─26487 /usr/bin/named -f -u named

Dec 07 02:04:03 phoinix named[26487]: managed-keys-zone: loaded serial 129
Dec 07 02:04:03 phoinix named[26487]: zone 0.0.127.in-addr.arpa/IN: loaded
serial 42
Dec 07 02:04:03 phoinix named[26487]: zone rlfpllc.com/IN: loaded serial
2017000017
Dec 07 02:04:03 phoinix named[26487]: zone localhost/IN: loaded serial 42
Dec 07 02:04:03 phoinix named[26487]: zone 7.168.192.in-addr.arpa/IN: loaded
serial 2017000011
Dec 07 02:04:03 phoinix named[26487]: all zones loaded
Dec 07 02:04:03 phoinix named[26487]: running
Dec 07 02:04:04 phoinix named[26487]: managed-keys-zone: Key 19036 for zone .
is now trusted (acceptance timer com>
Dec 07 02:04:04 phoinix named[26487]: managed-keys-zone: Key 20326 for zone .
is now trusted (acceptance timer com>
Dec 07 02:04:04 phoinix named[26487]: resolver priming query complete

  I don't know if this is somehow related to the timers and keys that may be
timing out after some period of time. If no one else has seen this, I'll keep
watching, but if anybody has any ideas, I'd welcome your thoughts.

-- 
David C. Rankin, J.D.,P.E.



[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux