Hello,
I'm trying to help someone who just got a deticated server with DirectAdmin and CentOS 5.5 on it. DirectAdmin and the OS were cleanly installed to begin with. The problem has to do with Named.
When I stop named from SSH, the error produced says:
service named stop
Stopping named: [failed]
Restarting Named from SSH gives the error:
service named restart
Stopping named: [Failed]
Named: Already running
DirectAdmin also produces errors for Named. Restarting named from DirectAdmin gives the error
An error has occurred
Details
/sbin/service named restart 2>&1
Stopping named from DirectAdmin produces no errors, but also named never stops either. In otherwords, named does not show up as a stopped process from within DirectAdmin's Service Moniter.
Reloading Named both from within DA and SSH seems to work fine though. Any ideas as to a fix to this?
I removed the old Named Init script and downloaded a new one from directadmin.com/named
I set the new Named init script's permissions to 0755, and did chkconfig named reset. The problems above still occur however.
I'm trying to help someone who just got a deticated server with DirectAdmin and CentOS 5.5 on it. DirectAdmin and the OS were cleanly installed to begin with. The problem has to do with Named.
When I stop named from SSH, the error produced says:
service named stop
Stopping named: [failed]
Restarting Named from SSH gives the error:
service named restart
Stopping named: [Failed]
Named: Already running
DirectAdmin also produces errors for Named. Restarting named from DirectAdmin gives the error
An error has occurred
Details
/sbin/service named restart 2>&1
Stopping named from DirectAdmin produces no errors, but also named never stops either. In otherwords, named does not show up as a stopped process from within DirectAdmin's Service Moniter.
Reloading Named both from within DA and SSH seems to work fine though. Any ideas as to a fix to this?
I removed the old Named Init script and downloaded a new one from directadmin.com/named
I set the new Named init script's permissions to 0755, and did chkconfig named reset. The problems above still occur however.
Last edited: