Named doesn't start on Cent OS 4.3

A

ashworth102680

Verified User
Joined
Mar 25, 2005
Messages
20
Location
Vancouver, WA
Maybe I'm just dumb right now, but I cannot remember for the life of me what to do to get named to start on reboot ...right now it doesn't.

Using fresh install of DA on CentOS 4.3. Thanks to all for your help.
 
Actually, I just noticed it crashed again ....maybe it's starting fine, but crashing.

Any ideas on a starting point? This type of admin on CentOS isn't my strong point, so I apologize for not really knowing where to start out.
 
If I choose "reload" from within DA for named, I see this in the /var/log/messages

May 23 15:58:55 vps1 named[32155]: loading configuration from '/etc/named.conf'
May 23 15:58:55 vps1 named[32155]: no IPv6 interfaces found
May 23 15:58:55 vps1 named[32155]: the key 'rndckey' is too short to be secure
 
chkconfig is a command that configures when daemons get started. It will make the links to /etc/init.d for you. In a shell, type
Code: 
man chkconfig
and it will tell you how to use it. As far as your server crashing, there are too many reasons to just guess, you need to look through your log files to see if there is a hardware problem or perhaps something else causing kernel panics.
 
I ran "chkconfig named on" to match settings that exim has ...

Code: 
named           0:off   1:off   2:on    3:on    4:on    5:on    6:off

I will let you know if this continues to happen for other users' sake. Thanks! :)
 
That wasn't it ...as soon as I rebooted after that change, named wouldn't work at all.

I switched back to "off" state, then rebooted the VPS, now it's back up just fine....the site's are browsing.

What's weird is DA as admin login says named is stopped, but it's running (I think) or my sites wouldn't work, right?

Also, if I run this command, I don't see processes, so maybe it's not really running...

[root@vps1 ~]# ps -ef | grep named
root 5731 5484 0 16:21 pts/0 00:00:00 grep named
 
VPS systems don't necessarily run all daemons as daemons; check to see if there's a listing in /etc/xinet.d.

Given that, ask the company you got your vps from; it may very well be an issue with how they set up their VPS.

Jeff
 
You must log in or register to reply here.
Back
Top