topic Re: named start errors in Operating System - HP-UX

named start errors

JEAN TAYLOR — Wed, 11 Apr 2001 19:35:59 GMT

running named 4.9.7 PHNE_23277 as a secondary DNS server

Named hangs; have to stop then start. NAMED doesn't start properly. errors below for each entry in the named.boot file.

Mar 30 15:50:34 leghorn named-xfer[28132]: can't make tmpfile (rtc1/avoca.db.{28132): Bad file number
Mar 30 15:50:34 leghorn named-xfer[28131]: can't make tmpfile (rtc1/d64.db.{28131): Bad file number

After several unsuccessful attempts, named starts and runs fine until the next hang

Re: named start errors

John Bolene — Wed, 11 Apr 2001 20:08:26 GMT

Sounds like you have not done a mkdir on /usr/local/domain/rtc1 or wherever you have specified that the DNS subdirectories have to go in named.boot

Named cannot add a subdirectory, it can only add files.

If the subdirectory exists, it may not be globally writable and executable. Make the permissions 777 on the directory.

Re: named start errors

JEAN TAYLOR — Wed, 11 Apr 2001 21:08:22 GMT

The directories already exist with 777. NAMED starts eventually.

Re: named start errors

John Bolene — Thu, 12 Apr 2001 11:42:08 GMT

Could you post some of the named.boot file?
Also a ll of the /usr/local/domain or wherever you have your DNS set up to reside?

I am puzzled by the can't create temp file.
Do you have a lack of inodes available?
How about doing a bdf -i to see if you are running out of inodes?

Re: named start errors

JEAN TAYLOR — Thu, 12 Apr 2001 12:37:21 GMT

# ps -ef | grep named
root 19365 1 0 Mar 30 ? 92:22 /usr/sbin/named -b /etc/named.data/named.boot
# pwd
/etc/named.data
# ls -al
total 1498
drw-r--r-- 11 root sys 27648 Jan 30 14:31 .
dr-xr-xr-x 27 bin bin 6144 Mar 30 16:46 ..
-rw-rw-rw- 1 root sys 96597 Dec 28 1998 allsecondary.boot
drwxrwxrwx 6 root sys 1024 Apr 7 09:57 core
-r--r--r-- 1 root sys 1928 Dec 9 1998 db.cache
-rw-rw-rw- 1 root sys 10240 Aug 17 2000 directories
-rw-rw-rw- 1 root sys 3 Feb 26 10:23 dirs.lst
-rw-rw-rw- 1 root sys 106 Aug 17 2000 dnsdirsync.pl
drwxrwxrwx 11 root sys 1024 Apr 11 18:51 isbe
-rw-r--r-- 1 root sys 87550 Dec 11 1998 named.backup
-rw-r--r-- 1 root sys 159330 Apr 9 08:06 named.boot
-rw-r--r-- 1 root sys 140 Jun 9 1999 named.bootp
-rw-r--r-- 1 root sys 89 Jun 9 1999 named.bootp.bak
-rw-r--r-- 1 root sys 96347 Jun 28 1999 named.boot.backup
-rw-r--r-- 1 root sys 152180 Jan 30 15:11 named.boot.jmt
-rw-r--r-- 1 root sys 96261 Jun 9 1999 named.boot.lincon
-rwx------ 1 root sys 273 Feb 26 10:21 named.push
-rw-r----- 1 root sys 2501 Dec 9 1998 primaries.lst
drwxrwxrwx 14 root sys 3072 Apr 12 07:52 rtc1
drwxrwxrwx 11 root sys 6144 Feb 28 14:02 rtc1-4
drwxrwxrwx 13 root sys 1024 Apr 11 19:30 rtc5
drwxrwxrwx 26 root sys 2048 Apr 12 07:46 rtc6
drwxrwxrwx 14 root sys 4096 Apr 12 07:46 rtc7
drwxrwxrwx 18 root sys 1024 Apr 12 07:48 rtc8
drwxrwxrwx 27 root sys 1024 Apr 12 07:46 rtc9
# bdf -i
Filesystem kbytes used avail %used iused ifree %iuse Mounted on
/dev/vg00/lvol3 86016 36386 47060 44% 3539 12405 22% /
/dev/vg00/lvol1 47829 9079 33967 21% 15 7665 0% /stand
/dev/vg00/lvol8 512000 164153 326210 33% 6020 86960 6% /var
/dev/vg00/lvol7 450560 303132 138227 69% 14283 36857 28% /usr
/dev/vg00/lvol4 32768 4372 26659 14% 140 7096 2% /tmp
/dev/vg00/lvol6 249856 112379 128896 47% 2038 34366 6% /opt
/dev/vg00/lvol5 307200 70098 222347 24% 802 59274 1% /home
#
# more named.boot
;
secondary coveschool.pvt.k12.il.us 206.166.50.100 rtc1/coveschl.db
secondary winfield.lib.il.us 206.166.50.100 rtc1/winfieldlib.db
secondary echs.edwrds.k12.il.us 206.166.67.100 rtc9/edwrds/echs.db
secondary ags.edwrds.k12.il.us 206.166.67.100 rtc9/edwrds/ags.db
secondary wsgs.edwrds.k12.il.us 206.166.67.100 rtc9/edwrds/wsgs.db
secondary eccusd.edwrds.k12.il.us 206.166.67.100 rtc9/edwrds/eccusd.db
secondary 225.107.64.in-addr.arpa

Re: named start errors

John Bolene — Thu, 12 Apr 2001 13:07:02 GMT

try adding the statement
directory /etc/named.data
to named.boot

This tells named where to get its initial data.
It may be trying to first oput them in /tmp since no directory is stated on startup.

Re: named start errors

Kevin Wright — Thu, 12 Apr 2001 16:27:00 GMT

your named.boot/conf file on the slave should be the same format as on the primary, except that primary should be secondary (except for your loopback) and you need the ip of the primary in the 3rd field.. you need to have the directory directive of where your data is like mentioned above
directory /etc/named.data
then stop and restart named

Re: named start errors

JEAN TAYLOR — Thu, 26 Apr 2001 14:26:05 GMT

i added the directory statement and that fixed the problem. thanks much