topic Re: named process consuming 100% CPU. in Operating System - HP-UX

named process consuming 100% CPU.

Gulam Mohiuddin — Tue, 11 Oct 2005 06:58:51 GMT

Hi,

On our HP-UX 11.0 Server the named process is consuming one CPU 100% since last three days continuously. This never happened before.

How to stop/start the named process?

Why it’s misbehaving?

Thanks,

Gulam.

Re: named process consuming 100% CPU.

Kent Ostby — Tue, 11 Oct 2005 07:02:27 GMT

Back on 11.00, there was a problem like this which was fixed by PHNE_22159. Might want to check your telnetd kernel patches.

To restart named:

/sbin/init.d/named stop

then:

/sbin/init.d/named start

Stopping and restarting named could cause an interruption on your system of other facilities if they rely on named.

Best regards,

Oz

Re: named process consuming 100% CPU.

Steven E. Protter — Tue, 11 Oct 2005 07:16:32 GMT

BIND 9.2.x latest version from software.hp.com will probably solve this performance problem. You may have to use the itrc patch database if you are using an earlier named/BIND version.

swlist -l fileset | grep -i bind

swlist -l product | grep -i bind

SEP

Re: named process consuming 100% CPU.

Giedo Stolk_1 — Tue, 11 Oct 2005 07:40:18 GMT

If you want to know what the proces is doing you can use tusc. But this tools is not on a standard HP-Ux box. You will have to download it ..

Re: named process consuming 100% CPU.

Geoff Wild — Tue, 11 Oct 2005 08:51:13 GMT

Kent tell you how to restart it and I agree with Stephen - you probably have an old version of bind - and should upgrade.

To tell what version you have:

You can use dig (if installed):

dig @yourserver version.bind chaos txt

Or with nslookup:

nslookup -q=txt -class=CHAOS version.bind. 0

Rgds...Geoff

Re: named process consuming 100% CPU.

Bill Hassell — Tue, 11 Oct 2005 09:38:30 GMT

Or you may have a bad machine slamming your server in a loop. Turn on tracing for named for a few seconds (NO MORE!) and then look at the trace file. Use kill -SIGUSR1 and then kill -SIGUSR2 to stop the trace. You may see a bunch of requests from the same server. Check if the server is in a loop or running a commercial backup program. Commercial backup programs are notorious for requesting a DNS lookup for every file.