named does’t start when using systemctl
I am having trouble getting named to start using systemd on the Fedora 18 Raspberry Pi spin. It starts, then a few moments later there is a timeout and it fails. If I run the commands in named.service by hand, named starts just fine. I don’t know what the timeout is that systemctl is looking for or where it is being invoked. I have read the man pages for systemctl , systemd and others and I will continue to research this, but if anyone has any pointers, that would be great. systemctl status named.service output:
named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; disabled) Active: failed (Result: timeout) since Tue 2013-01-29 14:36:41 EST; 35min ago Process: 4189 ExecStart=/usr/sbin/named -u named $OPTIONS (code=exited, status=0/SUCCESS) Process: 4186 ExecStartPre=/usr/sbin/named-checkconf -z /etc/named.conf (code=exited, status=0/SUCCESS) Process: 4183 ExecStartPre=/usr/libexec/generate-rndc-key.sh (code=exited, status=0/SUCCESS) Jan 29 14:35:12 raspi.example.com named[4191]: all zones loaded Jan 29 14:35:12 raspi.example.com systemd[1]: PID file /run/named/named.pid not readable (yet?) after start. Jan 29 14:35:12 raspi.example.com named[4191]: running Jan 29 14:36:41 raspi.example.com systemd[1]: named.service operation timed out. Terminating. Jan 29 14:36:41 raspi.example.com named[4191]: shutting down Jan 29 14:36:41 raspi.example.com named[4191]: stopping command channel on 127.0.0.1#953 Jan 29 14:36:41 raspi.example.com named[4191]: no longer listening on 127.0.0.1#53 Jan 29 14:36:41 raspi.example.com named[4191]: exiting Jan 29 14:36:41 raspi.example.com systemd[1]: Failed to start Berkeley Internet Name Domain (DNS). Jan 29 14:36:41 raspi.example.com systemd[1]: Unit named.service entered failed state [Unit] Description=Berkeley Internet Name Domain (DNS) Wants=nss-lookup.target Before=nss-lookup.target After=network.target [Service] Type=forking EnvironmentFile=-/etc/sysconfig/named Environment=KRB5_KTNAME=/etc/named.keytab PIDFile=/run/named/named.pid ExecStartPre=/usr/libexec/generate-rndc-key.sh ExecStartPre=/usr/sbin/named-checkconf -z /etc/named.conf ExecStart=/usr/sbin/named -u named $OPTIONS ExecReload=/bin/sh -c '/usr/sbin/rndc reload > /dev/null 2>&1 || /bin/kill -HUP $MAINPID' ExecStop=/bin/sh -c '/usr/sbin/rndc stop > /dev/null 2>&1 || /bin/kill -TERM $MAINPID' PrivateTmp=true [Install] WantedBy=multi-user.target Vesta Control Panel — Forum
Не удалось «перезапустить» «‘named'» — если из панельки перезапускать службу.
Если из консоли: service named restart
Redirecting to /bin/systemctl restart named.service
Job for named.service failed because the control process exited with error code. See «systemctl status named.service» and «journalctl -xe» for details.
Далее ввожу команду: 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: exit-code) since Thu 2016-02-04 16:14:35 CET; 1min 21s ago
Process: 12505 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=1/FAILURE)
Feb 04 16:14:35 CentOS-72-64-minimal bash[12505]: zone mydomain1.com/IN: loaded serial 2016020301
Feb 04 16:14:35 CentOS-72-64-minimal bash[12505]: zone mydomain2.com/IN: loaded serial 2016020301
Feb 04 16:14:35 CentOS-72-64-minimal bash[12505]: zone mydomain3.com/IN: loaded serial 2016020301
Feb 04 16:14:35 CentOS-72-64-minimal bash[12505]: zone mydomain4.com/IN: loaded serial 2016020301
Feb 04 16:14:35 CentOS-72-64-minimal bash[12505]: zone mydomain5.com/IN: loaded serial 2016020301
Feb 04 16:14:35 CentOS-72-64-minimal bash[12505]: zone mydomain6/IN: loaded serial 2016020403
Feb 04 16:14:35 CentOS-72-64-minimal systemd[1]: named.service: control process exited, code=exited status=1
Feb 04 16:14:35 CentOS-72-64-minimal systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Feb 04 16:14:35 CentOS-72-64-minimal systemd[1]: Unit named.service entered failed state.
Feb 04 16:14:35 CentOS-72-64-minimal systemd[1]: named.service failed.
Помогите пожалуйста решить проблему, убил пол дня. named так и не работает.. (
Named service start fails
I’m trying to set up named but I’m in trouble trying to get it up. I’m using bind-9.9.4-29.el7_2.3.x86_64 on CentOS 7.2-1511 and that’s what happens when I do systemctl start named:
[root@berlin ~]# systemctl start named Job for named.service failed because the control process exited with error code. See "systemctl status named.service" and "journalctl -xe" for details. [root@berlin ~]# journalctl -xe -- Subject: Unit named-setup-rndc.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit named-setup-rndc.service has finished starting up. -- -- The start-up result is done. sep 01 12:35:56 berlin systemd[1]: Starting Berkeley Internet Name Domain (DNS). -- Subject: Unit named.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit named.service has begun starting up. sep 01 12:35:56 berlin bash[4808]: zone 184.132.10.IN-ADDR.ARPA/IN: loaded serial 2 sep 01 12:35:56 berlin bash[4808]: zone 7.237.10.IN-ADDR.ARPA/IN: loaded serial 2 sep 01 12:35:56 berlin bash[4808]: zone 1.168.192.IN-ADDR.ARPA/IN: loaded serial 3 sep 01 12:35:56 berlin bash[4808]: zone 1.1.10.IN-ADDR.ARPA/IN: loaded serial 6 sep 01 12:35:56 berlin bash[4808]: zone intra.genaker.net/IN: loaded serial 17 sep 01 12:35:56 berlin bash[4808]: zone localhost.localdomain/IN: loaded serial 0 sep 01 12:35:56 berlin bash[4808]: zone localhost/IN: loaded serial 0 sep 01 12:35:56 berlin bash[4808]: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: NS '1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 sep 01 12:35:56 berlin bash[4808]: zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: not loaded due to errors. sep 01 12:35:56 berlin bash[4808]: _default/1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: bad zone sep 01 12:35:56 berlin bash[4808]: zone 1.0.0.127.in-addr.arpa/IN: NS '1.0.0.127.in-addr.arpa' has no address records (A or AAAA) sep 01 12:35:56 berlin bash[4808]: zone 1.0.0.127.in-addr.arpa/IN: not loaded due to errors. sep 01 12:35:56 berlin bash[4808]: _default/1.0.0.127.in-addr.arpa/IN: bad zone sep 01 12:35:56 berlin bash[4808]: zone 0.in-addr.arpa/IN: NS '0.in-addr.arpa' has no address records (A or AAAA) sep 01 12:35:56 berlin bash[4808]: zone 0.in-addr.arpa/IN: not loaded due to errors. sep 01 12:35:56 berlin bash[4808]: _default/0.in-addr.arpa/IN: bad zone sep 01 12:35:56 berlin systemd[1]: named.service: control process exited, code=exited status=1 sep 01 12:35:56 berlin systemd[1]: Failed to start Berkeley Internet Name Domain (DNS). -- Subject: Unit named.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit named.service has failed. -- -- The result is failed. sep 01 12:35:56 berlin systemd[1]: Unit named.service entered failed state. sep 01 12:35:56 berlin systemd[1]: named.service failed. sep 01 12:35:56 berlin polkitd[4091]: Unregistered Authentication Agent for unix-process:4801:15030793 (system bus name :1.119, object path /org/freedesktop/PolicyKit1/Authenti [root@berlin ~]# named-checkconf -z /etc/named.conf zone 184.132.10.IN-ADDR.ARPA/IN: loaded serial 2 zone 7.237.10.IN-ADDR.ARPA/IN: loaded serial 2 zone 1.168.192.IN-ADDR.ARPA/IN: loaded serial 3 zone 1.1.10.IN-ADDR.ARPA/IN: loaded serial 6 zone intra.genaker.net/IN: loaded serial 17 zone localhost.localdomain/IN: loaded serial 0 zone localhost/IN: loaded serial 0 zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: NS '1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa' has no address records (A or AAAA) zone 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: not loaded due to errors. _default/1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa/IN: bad zone zone 1.0.0.127.in-addr.arpa/IN: NS '1.0.0.127.in-addr.arpa' has no address records (A or AAAA) zone 1.0.0.127.in-addr.arpa/IN: not loaded due to errors. _default/1.0.0.127.in-addr.arpa/IN: bad zone zone 0.in-addr.arpa/IN: NS '0.in-addr.arpa' has no address records (A or AAAA) zone 0.in-addr.arpa/IN: not loaded due to errors. _default/0.in-addr.arpa/IN: bad zone Some help will be appreciated. Thanks. Albert Many thanks for your answer, Neil. This is my /etc/named.rfc1912.zones
[root@berlin etc]# cat named.rfc1912.zones // named.rfc1912.zones: // // Provided by Red Hat caching-nameserver package // // ISC BIND named zone configuration for zones recommended by // RFC 1912 section 4.1 : localhost TLDs and address zones // and http://www.ietf.org/internet-drafts/draft-ietf-dnsop-default-local-zones-02.txt // (c)2007 R W Franks // // See /usr/share/doc/bind*/sample/ for example named configuration files. // zone "localhost.localdomain" IN < type master; file "named.localhost"; allow-update < none; >; >; zone "localhost" IN < type master; file "named.localhost"; allow-update < none; >; >; zone "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa" IN < type master; file "named.loopback"; allow-update < none; >; >; zone "1.0.0.127.in-addr.arpa" IN < type master; file "named.loopback"; allow-update < none; >; >; zone "0.in-addr.arpa" IN < type master; file "named.empty"; allow-update < none; >; >;