Starting bind 9.16.x with systemctl fails

[Adrian van Bloois]

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

[Anand Buddhdev]

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

Post by Adrian van Bloois
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.
* named.service - Berkeley Internet Name Domain (DNS)
Loaded: error (Reason: Bad message)
Active: inactive (dead)
These messages are not very helpful, any ideas???

[Nyamkhand Buluukhuu]

Hi,

You can see what is happening in debug mode.

Start your named with -g option
ex: /usr/sbin/named -g


Have a nice day :)
BR, NYAMKHAND Buluukhuu




________________________________
From: bind-users <bind-users-***@lists.isc.org> on behalf of Adrian van Bloois <***@pa0rda.nl>
Sent: Thursday, July 9, 2020 6:08 PM
To: BIND 9 mailinglist <bind-***@lists.isc.org>
Subject: Starting bind 9.16.x with systemctl fails

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.
_______________________________________________
Please visit https://protect2.fireeye.com/v1/url?k=ad60492d-f3fe4f08-ad6770f2-869600a3c855-fb3ed8b8ebf09aad&q=1&e=92485019-1c68-41ca-b239-1b00b6f4f381&u=https%3A%2F%2Flists.isc.org%2Fmailman%2Flistinfo%2Fbind-users to unsubscribe from this list

ISC funds the development of this software with paid support subscriptions. Contact us at https://protect2.fireeye.com/v1/url?k=cead8273-90338456-ceaabbac-869600a3c855-3d0f193407c15999&q=1&e=92485019-1c68-41ca-b239-1b00b6f4f381&u=https%3A%2F%2Fwww.isc.org%2Fcontact%2F for more information.


bind-users mailing list
bind-***@lists.isc.org
https://protect2.fireeye.com/v1/url?k=c89e11e0-960017c5-c899283f-869600a3c855-b48f3ef414cf2960&q=1&e=92485019-1c68-41ca-b239-1b00b6f4f381&u=https%3A%2F%2Flists.isc.org%2Fmailman%2Flistinfo%2Fbind-users

[Reindl Harald]

Post by Adrian van Bloois
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.
* 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.