named.service: Doesn't crash on start but doesn't listen on port 53 either
by rnturn from LinuxQuestions.org on (#6N309)
I just migrated a set of named zone files from an older Raspberry Pi to a newer one and the named.service will not start.
From the CLI, If I run "named -f" I see a series of zone files being loaded and a message "all zones loaded" at the end of the log file followed by the normal named shutdown messages you see when ending it with Ctrl-C.. ("named -g" gives me the same results but on the console as expected.)
When running named by hand at the CLI, running nmap on another system pointed to the new Pi doesn't show anything listening on port 53.
When I issue "systemctl start named.service", I get the dreaded "exited with error code" message and instructions to run "journalctl -xeu named.service". That command tells me in about eight different ways that the named.service finished with an error. But nothing specific about the reason for the 'exit-code' result I'm seeing. The start via systemctl is not adding anything to the log files under /var/log/named, either, leaving me in the dark.
I added "-d 3" to the named command line in the service file, restarted the systemd daemon, and expected (hoped is probably more accurate, TBH) to see something in the file /var/log/named/debug.log as defined in the "named.conf.options" file. Nothing is being produced in that file when starting the service.
Anything else I could post to help?
Is there another location where systemd could be writing errors?
TIA for anything LQers can offer.
From the CLI, If I run "named -f" I see a series of zone files being loaded and a message "all zones loaded" at the end of the log file followed by the normal named shutdown messages you see when ending it with Ctrl-C.. ("named -g" gives me the same results but on the console as expected.)
When running named by hand at the CLI, running nmap on another system pointed to the new Pi doesn't show anything listening on port 53.
When I issue "systemctl start named.service", I get the dreaded "exited with error code" message and instructions to run "journalctl -xeu named.service". That command tells me in about eight different ways that the named.service finished with an error. But nothing specific about the reason for the 'exit-code' result I'm seeing. The start via systemctl is not adding anything to the log files under /var/log/named, either, leaving me in the dark.
I added "-d 3" to the named command line in the service file, restarted the systemd daemon, and expected (hoped is probably more accurate, TBH) to see something in the file /var/log/named/debug.log as defined in the "named.conf.options" file. Nothing is being produced in that file when starting the service.
Anything else I could post to help?
Is there another location where systemd could be writing errors?
TIA for anything LQers can offer.