Date: Tue, 30 Apr 2013 23:20:11 +0100 From: Chris Rees <crees@FreeBSD.org> To: jmorenov@jmorenov.com.co Cc: FreeBSD <freebsd-stable@freebsd.org> Subject: Re: named fails two weeks ago unexpectedly Message-ID: <CADLo83_jxKcZr6LDHaR_=J1or__RRTW6rQQzXN8yv2%2BoT_C9Bw@mail.gmail.com> In-Reply-To: <9fb04ef95c1af64e3bd034910ccba590@jmorenov.com.co> References: <9fb04ef95c1af64e3bd034910ccba590@jmorenov.com.co>
next in thread | previous in thread | raw e-mail | index | archive | help
On 27 January 2013 20:25, <jmorenov@jmorenov.com.co> wrote:
> Hi
>
> I was used FreeBSD 9.1 Release since December 2012, I usually use
> "portsnap fetch && update" and "portmaster-a" to keep my system updated.
> Two weeks ago unexpectedly "named" not worked. this is my case:
>
> "Problem:
> root@server:/etc # /etc/rc.d/named start
> /etc/rc.d/named: ERROR: get_pidfile_from_conf: /etc/namedb/named.conf does
> not exist (named)
> Checking:
> root@server:/etc # ls -l /var/named/etc/namedb
> total 40
> drwxr-xr-x 2 bind wheel 512 Dec 4 04:32 dynamic
> drwxr-xr-x 2 root wheel 512 Dec 4 04:34 master
> -rw-r--r-- 1 bind wheel 15150 Jan 17 15:57 named.conf
> -rw-r--r-- 1 bind wheel 3135 Dec 4 04:34 named.root
> -rw------- 1 bind wheel 97 Dec 22 03:49 rndc.key
> drwxr-xr-x 2 bind wheel 512 Dec 4 04:32 slave
> drwxr-xr-x 2 bind wheel 512 Jan 27 13:25 working
>
> root@server:/root # cat /etc/defaults/rc.conf | grep named
> # named. It may be possible to run named in a sandbox, man security for
> named_enable="NO" # Run named, the DNS server (or NO).
> named_program="/usr/sbin/named" # Path to named, if you want a different
> one.
> named_conf="/etc/namedb/named.conf" # Path to the configuration file
> #named_flags="" # Use this for flags OTHER than -u and -c
> named_uid="bind" # User to run named as
> named_chrootdir="/var/named" # Chroot directory (or "" not to auto-chroot
> it)
> named_chroot_autoupdate="YES" # Automatically install/update chrooted
> # components of named. See /etc/rc.d/named.
> named_symlink_enable="YES" # Symlink the chrooted pid file
> named_wait="NO" # Wait for working name service before exiting
> named_wait_host="localhost" # Hostname to check if named_wait is enabled
> named_auto_forward="NO" # Set up forwarders from /etc/resolv.conf
> named_auto_forward_only="NO" # Do "forward only" instead of "forward
> first"
>
> root@server:/root # cat /etc/rc.conf | grep named
> named_enable="YES"
>
> Cause:
> FreeBSD 9.1 was running OK, but "named" failed for no apparent reason
>
> My Solution:
> root@server:/etc # ln -s /var/named/etc/namedb /etc/namedb
> root@server:/etc # /etc/rc.d/named start
> Starting named."
>
> I do not know what happened with "named" that it fails two weeks ago, any
> ideas ?
Necro-reply, sorry.
That symlink is there on all of my systems, you must have accidentally
removed it.
[crees@pegasus]~% grep -n namedb /usr/src/etc/Makefile
220: @if [ ! -e ${DESTDIR}/etc/namedb ]; then \
222: ln -s ../var/named/etc/namedb ${DESTDIR}/etc/namedb; \
226: ${_+_}cd ${.CURDIR}/namedb; ${MAKE} install
Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo83_jxKcZr6LDHaR_=J1or__RRTW6rQQzXN8yv2%2BoT_C9Bw>