The service 'named' on server server.domain.net is currently down

E

elegance

Verified User
Joined
Feb 11, 2008
Messages
10
I am recieving more than 40 email every day with this subject:

A new message or response with subject:

The service 'named' on server server.domain.net is currently down

has arrived for you to view.
Follow this link to view it:

http://server.domain.net:2222/CMD_TICKET?action=view&number=000000028&type=ticket


======================================================
Automatically generated email produced by DirectAdmin 1.31.4

Do Not Reply.
Click to expand...

Then i typed:
[root@server ~]# /etc/init.d/named restart
Stopping named: [FAILED]
Starting named: [FAILED]

Please tell me is it necessary service?! if yes how can i repair that?!
 
Last edited:
Also i try this page: http://help.directadmin.com/item.php?id=40

but now my errors is:

Feb 17 15:20:03 server sshd(pam_unix)[13038]: check pass; user unknown
Feb 17 15:20:03 server sshd(pam_unix)[13038]: authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89-96-215.ip14.fastwebnet.it
Feb 17 15:20:07 server sshd(pam_unix)[13040]: check pass; user unknown
Feb 17 15:20:07 server sshd(pam_unix)[13040]: authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89-96-215.ip14.fastwebnet.it
Feb 17 15:20:11 server sshd(pam_unix)[13042]: check pass; user unknown
Feb 17 15:20:11 server sshd(pam_unix)[13042]: authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89-96-215.ip14.fastwebnet.it
Feb 17 15:20:11 server named: named shutdown failed
Feb 17 15:20:11 server named[13058]: starting BIND 9.2.4 -u named
Feb 17 15:20:11 server named[13058]: using 2 CPUs
Feb 17 15:20:11 server named[13058]: loading configuration from '/etc/named.conf'
Feb 17 15:20:11 server named[13058]: listening on IPv4 interface lo, SERVER IP#53
Feb 17 15:20:11 server named[13058]: listening on IPv4 interface eth0, SERVER IP#53
Feb 17 15:20:11 server named[13058]: listening on IPv4 interface eth0:0, SERVER IP#53
Feb 17 15:20:11 server named[13058]: listening on IPv4 interface eth0:3, SERVER IP#53
Feb 17 15:20:11 server named[13058]: acl.c:284: REQUIRE((((acl) != ((void *)0)) && (((const isc__magic_t *)(acl))->magic == ((('D') << 24 | ('a') $
Feb 17 15:20:11 server named[13058]: exiting (due to assertion failure)
Click to expand...
 
elegance said:
Feb 17 15:20:11 server named[13058]: acl.c:284: REQUIRE((((acl) != ((void *)0)) && (((const isc__magic_t *)(acl))->magic == ((('D') << 24 | ('a') $
Feb 17 15:20:11 server named[13058]: exiting (due to assertion failure)
Click to expand...
What is the current version of BIND installed on your server? Did you try to upgrade or re-install BIND by any chance? This error means named daemon detected an error in internal consistency check. Also, look into '/etc/named.conf' file and check the syntax.
 
named is working now

i removed bind* form yum.conf and i used this command: yum update bind\*
now everything is working fine :)

also i report this problem to centos core team, and they said this bug is from Direct Admin not centos.
 
Last edited:
elegance said:
also i report this problem to centos core team, and they said this bug is from Direct Admin not centos.
Click to expand...
If it's a bug how come you're the only user who's reported it?

I don't think it's a bug.

Jeff
 
How was BIND originally installed on your server? In our case BIND is originally installed by yum, and it's always worked. How did you install BIND?

Jeff
 
You are not alone.

I also met this error. Cleaning centos, first time installation of DriectAdmin, then, error appers.

I think it is a bug
 
You must log in or register to reply here.
Back
Top