SCIENTIFIC-LINUX-USERS Archives

December 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Bill Maidment <[log in to unmask]>
Reply To:
Bill Maidment <[log in to unmask]>
Date:
Sat, 10 Dec 2011 20:54:02 +1100
Content-Type:
text/plain
Parts/Attachments:
text/plain (18 lines)
Hi again
I have been having some issues with named (bind-9.7.3-2.el6_1.P3.3.x86_64) where after a while it fails to resolve some domains and when I try to do service named restart I get a message that says:
Stopping named: .............umount: /var/named/chroot/var/named: device is busy.

I have to do a kill -9 to stop named before I can start it again.
I have searched high and low in logs and google to find the cause of this; even disabling openvpn and dnssec, but I still can't solve it. lsof doesn't seem to reveal the culprit.

This occurs with a variety of named.conf settings, but the simplest is with just these two lines added to the standard config
        forwarders { 192.168.2.4; 192.168.2.18; };
        forward only;

Has anyone else experienced this or knows how to resolve this?

Cheers
Bill Maidment
IT Consultant to Elgas Ltd
Phone: 02 4294 3649

ATOM RSS1 RSS2