SUMMARY:Slow response from System login

From: Zion_Huang@focusppo.com
Date: Fri Aug 13 1999 - 12:40:57 CDT


Thanks to all the responses. Specially to:

Greg Obremski
Ken Robson
Dale Hsu

The Solution: The slow response was due to /usr/sbin/quota program in the
/etc/.login trying to check a nfs file system which system still tries to
mount yet it is not reachable.

After doing further study on quota file, I found one of the remote nfs file
system was not mounted because that system was not on UPS and it is a linux
box and I have decided to shut it down during the storm to prevent it from
crashing by power glitch.

After booting the linux box and the remote nfs file get mounted on the
Solaris server, the quota program will get a normal speed response and the
problem disappear.

Thank you all for the tips.

Zion

Here is the original question:

To All the Helpers:

Platform: Solaris 2.6 Ultra Enterprise II, Volume Manager, DNS only.

Problem:

Telnet to the system, get a quick login prompt. After entering login and
password, the system will sit there for about a minute or two and then
prompt the shell to user.

Interestingly, if we use root to telnet to the box, there is no such delay
getting shell prompt problem.

I have done recently to increase the pty port by edit /etc/system and in
it, I add set pt_cnt=120 from original number 70 and then reboot the system
with boot -r.

When I was rebooting the system, the system had problem to fsck one of the
file systems and I had to manually fsck and repaired some files, This file
system was not in any system related file system such as / or /usr or
/var.

After going to multi-user, I can telnet with good response. Then yesterday
afternoon, there is a power outage in the building., although the system is
on UPS, the client running telnet from PCs was not in UPS. After this
instance, when user tried to telnet to the box, the system started showing
slow response behavior.

I do not believe it is storm related though, since we have other Sun box
that in the same UPS system and showed no such abnormal behavior.

Any suggestion of how to troubleshoot this problem?

Thanks in advance for your help,

Zion



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:24 CDT