[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

909.0. "PCM 1.6-116 Disconnect Hangs" by 58392::COOKE (Vern Cooke @CTU (Western Canada OMS)) Sun Aug 06 1995 14:58

Hello:

Last Friday we upgraded from PCM 1.5-006 to 1.6-116 running on a VAX/VMS 6.1
4000vlc platform.

After a short while of using the text-based monitor interface to interact with
systems, users would "hang" when attempting to disconnect. For example, a user
would press the Control-G key to disconnect, PCM would respond with the message
"Disconnecting..." and that would be it, the user's session is hung. Not even a
control-Y would get a response.

I did a SHOW PROCESS/CONT on one of the hung processes and found it wasn't
doing anything: no I/O, CPU time, etc. was being used.

Also, on a probably related point, we found that, periodically, when connected
to a system using the text-based monitor interface, the user would be dumped
back to the DCL prompt with what appeared to be a one-line set of error codes.
This would occur when the user did not perform any work for a few minutes. The
error codes started with a cryptic word ending in "PSL"; unfortunately I did
not record what the text was.

As a result of this, I rolled back to 1.5-006 (basically, I restored my system
disk backup).

I would appreciate any ideas on why these problems could have occurred before I
attempt to upgrade again.
						Thank you,
								...... Vern.
T.RTitleUserPersonal
Name
DateLines
909.129067::BUTTERWORTHGun Control is a steady hand.Tue Aug 08 1995 13:4417
    None of what you are experiencing is a known problem in 1.6.  I have
    never had a connect or monitor session hang and neither did our big
    "field test" site that has 198 nodes in their configuration. The "PSL"
    sounds like you experienced an access violation. This sounds
    environmental to me and I suspect a resource limitation.  With the info 
    provided, all I can do is guess about the accvio. What I would do is 
    increase the PGFLQUOTA of the users in question - set it to 40K and
    makre sure your pagefileis big enough to handle it. Note also that the 
    4000 VLC can only be configured with a maximum of 24 megs of memory and 
    the SPD for PCM says that a minimum of 32 megs is required. Because
    of this limitation the 4000 VLC is not on the list of supported
    processors that are qualified to be the PCM engine itself. A 4000 VLC
    may be a service node however. Without being able to look at the system 
    when it's broken I can't help you too much.
    
    Regards,
       Dan
909.2Thank you58392::COOKEVern Cooke @CTU (Western Canada OMS)Tue Aug 08 1995 19:0813
    Dan:
    
    Thanks for the tuning suggestions. I will re-attempt the upgrade after
    ensuring the parameters are set as you suggested.
    
    As for the 4000vlc platform itself, wouldn't the limited memory only
    affect performance as additional swapping may be required? In the year
    we have been using the 4000vlc for PCM (prior to that we were using VCS
    with a u3900) we have not experienced problems other than those that
    were documented elsewhere in this conference.
    
    In any case, thank you for the speedy reply!
    							...... Vern.
909.3seen this also...52336::STRATMANPeter Stratman @VBOWed Aug 09 1995 05:4512
    Dan,

    For the record, I have seen the disconnect hanging on two occasions
    also.

    Once on a VAX/VMS PCM system. This was straight after the installation
    and happened during a couple of hours. (un)fortunatelythe pb. strangely
    went away after that. The second time was yesterday on an Alpha/VMS
    system when ^Ging out of a Connect to monitor mode. The accounts used
    had more than 40000 p. of pgflquo.

    Peter.
909.4What was the Resolution?58392::COOKEVern Cooke @CTU (Western Canada OMS)Wed Aug 09 1995 20:5911
    
    Hi Peter:
    
    You said that the problem went away after a few hours. Did you do
    anything to make it go away, like rebooting or restarting PCM? Were
    there any special configuration settings you may have set for the
    problem systems to help resolve the problem?
    
    				Any insights would be appreciated.
    							..... Vern.
    
909.5don't know...52336::STRATMANPeter Stratman @VBOThu Aug 10 1995 06:434
    Thats's what is unfortunate: the problem just disappeared after a
    while without anything being chaned (on purpose at least)...

    Peter.
909.6seen, reported at least couple of times...51666::KORKKOVeli K�rkk� @FNO, 879-5512, GPS FNOTue Aug 15 1995 09:2614
I've seen the hanging every now and then. And also the ACCVIO happens
every now and then. I think I've even reported these problems a few times...

LASt night I had couple of monitored system to crash and unfortunately the
CONS MONI also hung when I was trying control-G out of the connect mode.

Using SDA I was able to figure out that the process was busy to a mailbox.
Apparently "CONS CONNECT / control-G" process had read I/O to the mailbox in
question (as a DCL write to that mailbox resolved situation...).

I had to shutdown PCM anyway completely and restart. This shutdown also cleared
"archive in progress" flag.

_veli