HP3000-L Archives

May 1995, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Ken Sletten b894 c331 x2525 <[log in to unmask]>
Reply To:
Ken Sletten b894 c331 x2525 <[log in to unmask]>
Date:
Fri, 12 May 1995 12:29:00 P
Content-Type:
text/plain
Parts/Attachments:
text/plain (37 lines)
For those running 5.0 PUSH (C.50.00), we just
experienced a VT ghost session problem that
required a re-boot.  Here's the scenario:
 
I tried to start another VT session to our 957 this
morning.  Got "connection refused" message.
After a little looking around, discovered that even
though we had only one LOCAL and 8 REMOTE
NS users, NSCONTROL said we had a total of
*131* ACTIVE VTSERVERS.....  Huh ?!?!?........
(our MAX VTSERVER is set at 300.)
 
The SESSION numbers associated with the
supposedly ACTIVE VTSERVERS went all the
way back to like five weeks ago, about the last
time we rebooted the system to put in a patch.
Apparently when you get enough ghost sessions
hanging around, some resouce gets maxed out
and no more new VT sessions are allowed.
 
Did the usual PICS thing.  Found out there is a
known problem in this area (at least we think we
are having the known problem).  There is a patch;
don't have the number yet.
 
NSCONTROL KILLSESS could not kill the ghost
VT sessions;  so ended up having to do a START
NORECOVERY in the middle of the day.......    :-(
 
So if you run a lot of VT sessions on C.50.00 and
haven't checked for ghosts lately with NSCONTROL
STATUS, you might want to take a look..........
 
Just another day at the office,
 
Ken Sletten

ATOM RSS1 RSS2