1826457 Members
3276 Online
109692 Solutions
New Discussion

Re: System Slowdown

 
Joe Kanakaraj
Advisor

System Slowdown

Hi,

I have seen a lot of system slowdown threads, but can't seem to find a problem to my solution.

One of my C3600 workstations, has slowed down to a turtles (maybe a snail) pace. Telnets to the machine require me to have cup a coffee & a snack before I can see the login prompt. The machine runs UG NX 2 on HP UX 11.

I checked using sar and top and the system is practically idle. I guess it is a network problem. I restarted the machine and it took almost 1 hour to boot up, it held up for a while, when starting the SNMP subagent(20 minutes) then hung up at time synchronization (10 minutes), X print server (20 minutes) and CDE startup (10 Minutes). I have not been able to get into cde, it just stops at the CUI prompt.

Right now I am trying to install patches and it is taking very long, I have left the machine on for 3 hours and it is still trying to create a depot. my ps -ef looks fine and shows that the system is executing the right commands, and top shows that the processes are executing, but why the slow response.

I hope to get the patches installed and see if there is a change, but before I even reconsider a reinstall, maybe some of you can give me some ideas as to the cause and the way to figure it our.

Cheers,

Joe
Unix is simple, but it takes a genius to understand the simplicity. - quoted Dennis Ritchie
6 REPLIES 6
Patrick Wallek
Honored Contributor

Re: System Slowdown

It sounds like a hostname / ip address resolution issue.

1) Is the hostname and ip address configured correctly in /etc/hosts? If not, do so.

2) Are you using DNS? If so, is your /etc/resolv.conf set to look for the correct DNS server? Is you /etc/nsswitch.conf file set to look for stuff in the correct order?

In the nsswitch.conf file, you should look in files first and the dns.

hosts: files [ NOUTFOUND=continue ] dns

or something very similar.

Also check if nslookup returns the correct values for this machine for both the name and IP address.

# nslookup machinename

# nslookup 1.2.3.4
(where 1.2.3.4 is the correct IP address for this machine). The values returned should be appropriate for this machine. If not, fix dns or /etc/hosts depending on where the resolution came from.
Steven E. Protter
Exalted Contributor

Re: System Slowdown

Patricks idea is most promisign.

Most of the trouble is probably from what he said. If you are using DNS and you can't contact /etc/resolv.conf servers or they are slow out of date microsoft servers that could be a major contributor.

Network hardware between you and those /etc/resolve.conf servers can also slow you down and needs to be checked for correct swtich port speed and duplex settings.

AND.

When i first but 11i v1 on a slow D320 everything involving SD/UX was painfully slow. Depot create and install.

Then i downloaded and installed every sd/ux patch in creation and things speed up.

You also might want to go command line mode and do an init 2.

Less stuff will be running and your machine will be less stressed when you try to do the patches. All of the swagentd processes that sd/ux software distributor needs are at level 2, so you can do the install with less junk running.

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
Victor Fridyev
Honored Contributor

Re: System Slowdown

I agree with Patrik and Steven that the most probably this is name resolution problem., but, may be the problem is with a SCSI errors. Could you run
dmesg -
and look at its output ? If you see SCSI reset messages, check all SCSI connections and SCSI ID duplication.
The main question: what has been changed on this machine, which caused the slow down ? Did the computer work properly before ?
Entities are not to be multiplied beyond necessity - RTFM
KCS_1
Respected Contributor

Re: System Slowdown

Hi,

I agree with all forumer here about this,similar problems are issued by not proper Networking problem in the case(DNS,ip,hostname and so on)
As you see, all above posting are really nice soulution.
If you treat network files these days, that is able to remind you what happened on it.
Normally,when boot the system up, it checks network environment itself whether normal or not.

Easy going at all.
R. Sri Ram Kishore_1
Respected Contributor

Re: System Slowdown

Ted Buis
Honored Contributor

Re: System Slowdown

If you are using 10/100BaseT, I have seen similar problems from having the half/full duplex mismatched between the NIC and the switch. True, they are supposed to auto-negotiate, but it doesn't always work.
Mom 6