Operating System - HP-UX
1825766 Members
2072 Online
109687 Solutions
New Discussion

Re: named process consuming 100% CPU.

 
Gulam Mohiuddin
Regular Advisor

named process consuming 100% CPU.

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.
Everyday Learning.
5 REPLIES 5
Kent Ostby
Honored Contributor

Re: named process consuming 100% CPU.

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
"Well, actually, she is a rocket scientist" -- Steve Martin in "Roxanne"
Steven E. Protter
Exalted Contributor

Re: named process consuming 100% CPU.

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

Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Giedo Stolk_1
New Member

Re: named process consuming 100% CPU.

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 ..
Geoff Wild
Honored Contributor

Re: named process consuming 100% CPU.

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
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
Bill Hassell
Honored Contributor

Re: named process consuming 100% CPU.

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.


Bill Hassell, sysadmin