Strange bind behavior

Issues related to software problems
Post Reply
grifs71
Posts: 157
Joined: 2007/10/02 05:15:38
Location: Arkansas, United States

Strange bind behavior

Post by grifs71 » 2009/08/06 22:47:46

I am at a loss here, bind (dns) is dieing in the primaryname server running centos 4.6 x64.

The only way I can get it going again is to reboot the server, if I try to restart it with the service named restart it fails with 'named already running'...

The version of bind is bind-9.2.4-30.el4, once the reboot is complete it works fine, however it is getting more frequent with the named process dieing
and leaving a pid on the server.

I am not a bind expert, however I read if a file was not configured correctly it would cause bind to fail, however it is still running according to the
service named status and on restart it fails.

'named' is not in the list of processes when I do a top either???

Does anyone have any tips or have you seen this type of behavior before. If I run named-checkconf /etc/named.conf ( I get no errors)???

I am wondering why it stops responding and I cannot get named to run without a reboot of the server.

pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact:

Strange bind behavior

Post by pschaff » 2009/08/14 14:12:01

[quote]
grifs71 wrote:
I am at a loss here, bind (dns) is dieing in the primaryname server running centos 4.6 x64.
[/quote]
If you are still running 4.6 please update to 4.7 + updates - 4.8 will be released any day now. The current version is bind-9.2.4-30.el4_7.2

[quote]
...
I am not a bind expert, however I read if a file was not configured correctly it would cause bind to fail, however it is still running according to the
service named status and on restart it fails.

'named' is not in the list of processes when I do a top either???
[/quote]
Neither am I a bind expert, but try "ps auxww | grep named" and /sbin/pidof named" - the technique used by the initscript and you should see a process. Possibly it is hung but must exist or "pidof" would fail.

[quote]
Does anyone have any tips or have you seen this type of behavior before. If I run named-checkconf /etc/named.conf ( I get no errors)???

I am wondering why it stops responding and I cannot get named to run without a reboot of the server.[/quote]

Try updating and see if the problem persists.

grifs71
Posts: 157
Joined: 2007/10/02 05:15:38
Location: Arkansas, United States

Re: Strange bind behavior

Post by grifs71 » 2009/09/15 19:11:07

[ Superfluous quote removed by moderator. ]
I resolved the issue with BIND by going back to the kernel it was compiled with and inserting a parameter into the grub.conf stanza.

Now it is stable and I am able to restart bind after changes.

Thanks for you help.

:)

pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact:

Re: Strange bind behavior

Post by pschaff » 2009/09/15 19:24:38

You're welcome, but please don't unnecessarily quote the entire previous message. If I understand you correctly you are still not updated and are vulnerable to known exploits already fixed in released updates. It also sounds like you may be running a locally-built version of bind tied to an old kernel.

grifs71
Posts: 157
Joined: 2007/10/02 05:15:38
Location: Arkansas, United States

Re: Strange bind behavior

Post by grifs71 » 2009/09/17 13:16:14

You are correct, I did not build this server initially I will be building a new VM to replace it with and using the version
of BIND out of the channel so it can be updated correctly.


I will be using CentOS5.4 x64 when it comes out, is there any tips here on bind in the 5 release of Cent?

thank you again,

:-D

pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact:

Re: Strange bind behavior

Post by pschaff » 2009/09/18 13:14:22

https://www.centos.org/modules/newbb/viewtopic.php?topic_id=22004&forum=37

Post Reply

Return to “CentOS 4 - Software Support”