From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Description of problem:
Yesterday i upgraded 2 machines and installed 1 from scratch
1 from RedHat 7.3 to RedHat 9.0
1 from RedHat 8.0 to RedHat 9.0
1 clean install from RedHat 9.0
on all machine's i can't stop the named process by typing
/etc/init.d/named stop kill the process is working fine (normal kill)
starting the named daemon with /etc/init.d/named start
is also working fine, how to solve this problem
i think the problem is in the "/usr/sbin/rndc" program
which will be executed from the /etc/init.d/named script
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. /etc/init.d/named stop
2. ps -ef|grep named
Actual Results: the named daemon was still running
Expected Results: the named daemon should be not running anymore
version: bind-9.2.1-16 (RedHat 9.0 + latest patches 'up2date')
[root@smarthost root]# /etc/init.d/named stop
[root@smarthost root]# /usr/sbin/rndc stop
[root@smarthost root]# ps -ef|grep named
named 2098 1 0 08:15 ? 00:00:00 [named]
root 10993 10933 0 09:47 pts/0 00:00:00 grep named
I see this also.
I upgraded to bind-9.2.2-8 from rawhide and still see this problem.
Apr 7 05:00:07 localhost named: app.c:562: unexpected error:
Apr 7 05:00:07 localhost named: isc_app_shutdown() pthread_kill: No such
Got this in the logs after "service named stop".
This is even after trying recompiling(9.2.2-8) it on the machine.
I was able to get it to shutdown by recompiling without --enable-threads
I still don't get a proper OK from the stop though. It just says
Yes we know about this problem, but it is Kernel related. Basically there is a
thread signalling problem in the Kernel. So when the named recieves the thread
shutdown kernel it goes into a weird state. We have to wait for the errata
kernel to fix this problem.
85896 Is the bug description that causes this problem.
i've got a message saying
You are not authorized to access bug #85896.
how can i see this ?
Get a job at Red Hat :^)
I changed the permission so you should be able to see it now.
I can confirm that kernel-2.4.20-9 fixes my issue with the actual shutdown of
named when using service named stop.
when stopping the deamon with new kernel it's stopping
only there is no [OK] sign
That problem has already been reported in another bug report, 87527.
the line is not erased at start as discribed in problem 87527
but when manual stopping /etc/init.d/named stop then there is no [OK] sign
but the named is stopped
It works in bind-9.2.2-10.