1. Forum
  2. USENET
  3. comp.protocols.dns.bind

  • Starting bind 9.16.x with systemctl fails

    From Adrian van Bloois@adrian@pa0rda.nl to BIND 9 mailinglist on Thu Jul 9 12:08:48 2020
    From Newsgroup: comp.protocols.dns.bind

    Hi,
    When I start bind 9.16.x with systemctl I get:

    Failed to start named.service: Unit is not loaded properly: Bad message.
    See system logs and 'systemctl status named.service' for details.


    I get no messages in the logs.
    Systemctl status named.service says:
    * named.service - Berkeley Internet Name Domain (DNS)
    Loaded: error (Reason: Bad message)
    Active: inactive (dead)


    These messages are not very helpful, any ideas???

    Adrian
    --
    Adri P. van Bloois


    "The greatest threat to our planet is the belief that someone else
    will save it."
    Robert Swan.
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Anand Buddhdev@anandb@ripe.net to Adrian van Bloois on Thu Jul 9 12:23:35 2020
    From Newsgroup: comp.protocols.dns.bind

    On 09/07/2020 12:08, Adrian van Bloois wrote:

    Hi Adrian,

    Run "journalctl -u named" to see any systemd logs for this unit. Also
    look in /var/log/messages to see what (if anything) BIND has logged to
    syslog. Finally, you would help yourself and everyone else to help you
    better if you show your systemd unit file with "systemctl cat named".
    No-one can read your mind or see your system configuration so we can't
    help you until we can see more details.

    Regards,
    Anand

    When I start bind 9.16.x with systemctl I get:

    Failed to start named.service: Unit is not loaded properly: Bad message.
    See system logs and 'systemctl status named.service' for details.


    I get no messages in the logs.
    Systemctl status named.service says:
    * named.service - Berkeley Internet Name Domain (DNS)
    Loaded: error (Reason: Bad message)
    Active: inactive (dead)

    These messages are not very helpful, any ideas???
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Reindl Harald@h.reindl@thelounge.net to bind-users on Thu Jul 9 12:31:00 2020
    From Newsgroup: comp.protocols.dns.bind



    Am 09.07.20 um 12:08 schrieb Adrian van Bloois:
    When I start bind 9.16.x with systemctl I get:

    Failed to start named.service: Unit is not loaded properly: Bad message.
    See system logs and 'systemctl status named.service' for details.


    I get no messages in the logs.
    Systemctl status named.service says:
    * named.service - Berkeley Internet Name Domain (DNS)
    Loaded: error (Reason: Bad message)
    Active: inactive (dead)

    These messages are not very helpful, any ideas???

    what about post the systemd-unit and besides that i find it unlikely
    that "journalctl" don't show any errors directly after try to restart
    (and yes you do "systemctl daemon-reload" and "systemctl restart named"
    in doubt)

    "systemctl daemon-reload" alone triggers in most cases messages when
    unitfiles are broken

    ----------------------------------

    similar issue with "Bad message" because nonsense in the unit-file

    https://www.raspberrypi.org/forums/viewtopic.php?t=173783

    Change that first line! Comment lines must begin with either # or ;

    That was the issue indeed ! Since I copy-pasted that from the Internet,
    I thought it was legit ... And then I don't really understand why the
    start command was working.
    --- Synchronet 3.21d-Linux NewsLink 1.2