On Sun, Nov 21, 2010 at 01:49:35PM -0800, Doug Barton wrote:
> On Thu, 11 Nov 2010, Carlos Vicente wrote:
>> Has anybody had this problem?
>> # /etc/init.d/named restart
>> Stopping named: . [FAILED]
>> Starting named: named: already running
On Thu, 11 Nov 2010, Carlos Vicente wrote:
Has anybody had this problem?
# /etc/init.d/named restart
Stopping named: . [FAILED]
Starting named: named: already running [ OK ]
Not sure what mechanism your linux distro is using, but
It is possible. I found that named wasn't logging to the configured
/var/log/named because logrotate failed to reload named after creating
the new file. If rndc stop was timing out because the daemon was trying
to write to the log file, then it could have been a catch 22 situation.
I have since re
Is it possible named was killed and restarted without
the /etc/init.d/named script?
The script looks up the process ID from /var/run/bind/run/named.pid (on
Debian) and if the PID doesn't match, the script can't stop named.
You can cat /var/run/bind/run/named.pid and compare the PID to what you
se
maybe this can be of help:
http://bugs.gentoo.org/show_bug.cgi?id=324315
On 11 November 2010 20:49, Carlos Vicente <
cvice...@network-services.uoregon.edu> wrote:
> Has anybody had this problem?
>
> # /etc/init.d/named restart
> Stopping named: . [FAILED]
What does /etc/init.d/named do when you run it with the restart option?
That file is not part of the BIND distribution and is likely a shell
script so take a look and see what's its attempting to do.
I wonder if its running 'rndc stop' and not waiting for the process to
finish up before trying t
Has anybody had this problem?
# /etc/init.d/named restart
Stopping named: . [FAILED]
Starting named: named: already running [ OK ]
I notice it happens after the daemon has been running for a while. If I
kill it and start it again, the
7 matches
Mail list logo
