systemd[1]: named.service start operation timed out. Terminating.
Posted: Sat Aug 05, 2017 10:45 pm
Today during VestaCP installation, it stopped prematurely by starting named service and it timeouted:
i tried to install again with -f (force) swithc, but stopped at same point (named).
I never installed Vesta on this VPS. It is LXC virtualization and centos-7-x86_64 with 512MB RAM, Linux 4.4.67-1-pve #1 SMP PVE 4.4.67-92 (Fri, 23 Jun 2017 08:22:06 +0200) x86_64 x86_64 x86_64 GNU/Linux# systemctl status named.service
● named.service - Berkeley Internet Name Domain (DNS)
Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)
Active: failed (Result: timeout) since Sat 2017-08-05 22:26:01 UTC; 5min ago
Process: 2984 ExecStart=/usr/sbin/named -u named $OPTIONS (code=exited, status=0/SUCCESS)
Process: 2982 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z /etc/named.conf; else echo "Checking of zone files is disabled"; fi (code=exited, status=0/SUCCESS)
Aug 05 22:24:31 lxc.host.virtualizor systemd[1]: PID file /run/named/named.pid not readable (yet?) after start.
Aug 05 22:26:01 lxc.host.virtualizor named[2985]: shutting down
Aug 05 22:26:01 lxc.host.virtualizor named[2985]: stopping command channel on 127.0.0.1#953
Aug 05 22:26:01 lxc.host.virtualizor named[2985]: stopping command channel on ::1#953
Aug 05 22:26:01 lxc.host.virtualizor named[2985]: no longer listening on 127.0.0.1#53
Aug 05 22:26:01 lxc.host.virtualizor named[2985]: no longer listening on 107.155.140.139#53
Aug 05 22:26:01 lxc.host.virtualizor systemd[1]: named.service start operation timed out. Terminating.
Aug 05 22:26:01 lxc.host.virtualizor systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Aug 05 22:26:01 lxc.host.virtualizor systemd[1]: Unit named.service entered failed state.
Aug 05 22:26:01 lxc.host.virtualizor systemd[1]: named.service failed.
i tried to install again with -f (force) swithc, but stopped at same point (named).