On 11/11/2022 01.47, Ling Yun wrote:
# systemctl status bind9
● named.service - BIND Domain Name Server
      Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor 
preset: enabled)
      Active: failed (Result: signal) since Thu 2022-11-10 21:51:18 CST; 48s ago
        Docs: man:named(8)
     Process: 96944 ExecStart=/usr/sbin/named -f $OPTIONS (code=killed, 
signal=ABRT)
    Main PID: 96944 (code=killed, signal=ABRT)

Nov 10 21:51:18 h2o systemd[1]: named.service: Scheduled restart job, restart 
counter is at 6.
Nov 10 21:51:18 h2o systemd[1]: Stopped BIND Domain Name Server.
Nov 10 21:51:18 h2o systemd[1]: named.service: Start request repeated too 
quickly.
Nov 10 21:51:18 h2o systemd[1]: named.service: Failed with result 'signal'.
Nov 10 21:51:18 h2o systemd[1]: Failed to start BIND Domain Name Server.

These log messages are irrelevant - it's just the systemd's restart facility 
rate-limit. Please attach the log which contains the real cause of failure, 
e.g. by using:

# journalctl -u bind9

--
Tom Krizek

Attachment: OpenPGP_0x01623B9B652A20A7.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Reply via email to