Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.protocols.dns.bind > #15940
| From | Reindl Harald <h.reindl@thelounge.net> |
|---|---|
| Newsgroups | comp.protocols.dns.bind |
| Subject | Re: Starting bind 9.16.x with systemctl fails |
| Date | 2020-07-09 12:31 +0200 |
| Organization | the lounge interactive design |
| Message-ID | <mailman.661.1594291051.942.bind-users@lists.isc.org> (permalink) |
| References | <20200709100848.GA24214@pa0rda.nl> <5359bf0e-bee9-54ea-6856-cc90f2791d53@thelounge.net> |
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.
Back to comp.protocols.dns.bind | Previous | Next | Find similar
Re: Starting bind 9.16.x with systemctl fails Reindl Harald <h.reindl@thelounge.net> - 2020-07-09 12:31 +0200
csiph-web