named not working properly after cpanel update

[hst]

I get this message every time I restart named

named has failed, please contact the sysadmin (result was "named is not running"). Aug 23 15:54:45 n21 named: named shutdown failed Aug 23 15:54:46 n21 named[27087]: starting BIND 9.2.4 -u named Aug 23 15:54:46 n21 named[27087]: using 2 CPUs Aug 23 15:54:46 n21 named: named startup succeeded

[aby]

I get this message every time I restart named

named has failed, please contact the sysadmin (result was "named is not running"). Aug 23 15:54:45 n21 named: named shutdown failed Aug 23 15:54:46 n21 named[27087]: starting BIND 9.2.4 -u named Aug 23 15:54:46 n21 named[27087]: using 2 CPUs Aug 23 15:54:46 n21 w named startup succeeded

Can you please confirm that what was the status of the bind before you start it. Was it failed?. Also did you notice any errors in messages when you restart the bind.

[hst]

I think bind was OK before update but really hadn't checked. Sites were working OK

Messages says:
modeprobe: modprobe: can't locate char-major-10-224

[aby]

I think bind was OK before update but really hadn't checked. Sites were working OK

Messages says:
modeprobe: modprobe: can't locate char-major-10-224

Please try to stop the bind. Then see if it shows any errors the. Also simultaneously check the /var/log/messages

[hst]

Here is what SSH says:
root@n21 [~]# /etc/rc.d/init.d/named stop
Stopping named: /etc/rc.d/init.d/named: line 139: 11370 Segmentation fault /usr/sbin/rndc stop >/dev/null 2>&1
[FAILED]
root@n21 [~]#

Here is in message
GNU nano 1.2.1 File: /var/log/messages

Aug 23 18:25:13 n21 pure-ftpd: (?@127.0.0.1) [INFO] New connection from 127.0.0$
Aug 23 18:25:13 n21 pure-ftpd: (?@127.0.0.1) [INFO] Logout.
Aug 23 18:30:00 n21 modprobe: modprobe: Can't locate module char-major-10-224
Aug 23 18:30:30 n21 last message repeated 3 times
Aug 23 18:30:30 n21 sshd(pam_unix)[11239]: session opened for user root by (uid$
Aug 23 18:30:30 n21 modprobe: modprobe: Can't locate module char-major-10-224
Aug 23 18:30:46 n21 named: named shutdown failed

[hst]

Any ideas what might be the cause?

[aby]

Did you try

/scripts/updatenow
/scripts/fixndc

[hst]

Tried both and it didn't help. Still cannot stop named and get fail error

[bijo]

Hello,

I am pasting a /etc/rc.d/init.d/named file of redhat machine below. Move your file to a backup and create that file using this code and then check. May be the location of your pid file, the bind user and conf file location are different. You can correct it by checking the named.conf
--------------------------------------------------------------------
#!/bin/sh
#
# $Id$
#


case "$1" in
start)
if [ -e /etc/binddisable ]; then
exit
fi
if [ -e /etc/nameddisable ]; then
exit
fi
[ -x /usr/sbin/named ] && /usr/sbin/named -u named -c /etc/named.conf && echo -n ' named'
;;
stop)
kill `cat /var/run/named/named.pid` && echo -n ' named'
;;
*)
echo "Usage: `basename $0` {start|stop}" >&2
exit 64
;;
esac

exit 0
--------------------------------------------

Let me know the status

[hst]

Tried your code and code off of another server. Still errors. Says missing modeprobe: module char-major-10-224.

[ncconquer]

same problem
how to fix this .........

[DigiCrime]

mv /lib/tls /lib/tls.disable
service named restart