named.service ramdom crashing

Issues related to applications and software problems and general support
Post Reply
larryg
Posts: 4
Joined: 2014/07/17 04:48:28

named.service ramdom crashing

Post by larryg » 2020/06/07 20:16:39

I'm running a caching name server on my system and it works fine for the most part but every few days it is crashing. The service dies with the following errors shown in the message log

Jun 7 03:48:05 LinuxServer systemd[1]: Reloading Berkeley Internet Name Domain (DNS).
Jun 7 03:48:05 LinuxServer systemd[5043]: named.service: Failed to set up mount namespacing: No such file or directory
Jun 7 03:48:05 LinuxServer systemd[5043]: named.service: Failed at step NAMESPACE spawning /bin/sh: No such file or directory
Jun 7 03:48:05 LinuxServer httpd[5038]: Server configured, listening on: port 443, port 80
Jun 7 03:48:05 LinuxServer systemd[1]: named.service: Control process exited, code=exited status=226
Jun 7 03:48:05 LinuxServer named[5120]: shutting down
Jun 7 03:48:05 LinuxServer named[5120]: stopping command channel on 127.0.0.1#953
Jun 7 03:48:05 LinuxServer named[5120]: no longer listening on 127.0.0.1#53
Jun 7 03:48:05 LinuxServer named[5120]: no longer listening on 192.168.1.2#53
Jun 7 03:48:05 LinuxServer named[5120]: no longer listening on 192.168.122.1#53
Jun 7 03:48:05 LinuxServer named[5120]: exiting
Jun 7 03:48:05 LinuxServer systemd[1]: named.service: Failed with result 'exit-code'.
Jun 7 03:48:05 LinuxServer systemd[1]: Reload failed for Berkeley Internet Name Domain (DNS).

And the message is current, there is no directory /bin/sh but it looks like named is trying to create it. I'm guessing its a permission error even though I have SELinux disabled.

Any thoughts on a workaround for this or is this a bug that needs to be reported as such.

Post Reply

Return to “CentOS 8 - General Support”