[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

725.0. "Console CTRL 01 stays LEF" by SWTHOM::DEGAGE () Thu May 11 1995 11:17

	Hi,

DEC 3300 with PCM 1.5A on OpenVMS/AXP 6.1.

PCM is configured with 8 systems to look at ( 3 through Telnet, 5 through LAT).

Sometimes ( seems to be random), no more connection seems to be possible with
PCM : Console connect leads to window creation but nothing at all appears in
the window.
The process Console CTRL 01 is in LEF state with many channels on mbas ( 3 of
them BUSY), no quota problem ( specially BYTLM which is very large ).

Console shutdown has no effect of course, the only way to cancel the problem
is to reboot BUT the problem can reproduce immediatly after the reboot.

The only error messages I found are in CONTROLLER_01.LOG and deals with problem
connecting to Telnet systems ( ending with SYSTEM-F-TIMEOUT, devbice timeout);
but $ telnet DSR listener gains the connection.

The main question is :
why is Console CTRL 01 in LEF state ( IO in progress ??)
What direction to look at ??

Thanks for your answer.
Seems to be clear that I'm a PCM beginner

Marielle DEGAGE  CSC France 
T.RTitleUserPersonal
Name
DateLines
725.1YOSSAM::SIMONSimon Jackson @reo 830 X3879Thu May 11 1995 11:357
Marielle
	we are currently field testing the V1.6 release of PCM. A lot of work
has been done to fix problems in the process communication code in this version.
Please Pull the FT kit (location in note 2.LAST in this conference asnd tell us
if this fixes your problem.

Cheers sImon...
725.2FT VersionSWTHOM::DEGAGEFri May 12 1995 09:377
	Thanks a lot for your reply.
So it seems to be a problem within the product and not within the customer
configuration.

May I give the FT 1.6 to the customer ??

Marielle
725.3PBUNIX::pgbAnd through the square window...Fri May 12 1995 10:579
Marielle,

  By all means, give T1.6 to your customer, but please explain to
  them that this is FT software and we are continually fixing bugs
  as they are reported.

Cheers,
Phil

725.4wait for a next FT-kitHLSM04::GERRITGerrit Woertman, UTO, 838-2535Fri May 12 1995 14:0210
    Hi,
    
    I also had this problem in V1.5, upgraded to the current FT T1.6-kit,
    and my LEF-situation got even worse, i.e. an unworkable situation,
    where we reboot the station once an hour.
    
    regards,
    
    Gerrit
    
725.5YOSSAM::PHILIPAnd through the square window...Sat May 13 1995 19:1610
All,

  When this LEF situation occurs, does the controller it happens to have
  PSEUDO terminal devices assigned to it?

  The reason I ask is that we have experienced this problem ourselves over 
  the last couple of days when we have been using Pseudo terminals.

Cheers,
Phil
725.6LEF not only on PSEUDO terminalsHLSM04::GERRITGerrit Woertman, UTO, 838-2535Mon May 15 1995 22:4936
    The LEF situation occurs on a controller with Pseudo terminal devices,
    even when this is only doing very little, like:
    
$     set noon
$     wait 00:00:10
$     i = f$trnlnm("SYS$INPUT")
$     c = f$trnlnm("SYS$COMMAND")
$     o = f$trnlnm("SYS$OUTPUT")
$     set term 'o'/broad
$     write sys$output "SYS$INPUT =''i' SYS$COMMAND = ''c' SYS$OUTPUT = ''o'"
$     write sys$output "Issuing $ REPLY/ENA"
$     reply/ena
$     write sys$output "Issuing $ REPLY/STAT"
$     reply/stat
$     wait 00:01:00
$ loop:
$     write sys$output "This is reply only terminal"
$     wait 01:00:00
$     goto loop
    
    and on this station there are almost none OPCOM-messages.
    When this system happens, according to the alphabet, to be the first
    system for a controller, then it is a pity for the other 15 systems.
    
    But besides the pseudoterminals, the LEF situation happens also
    on a controller that gets quite a lot of console-output.
    In our UTO-situation this already happened in V1.5, but things are
    worse in the current FT-version.
    In fact, last Friday I have downgraded to V1.5 to get a more stable
    situation, after 5 unworkable days, and quite a lot of criticism!
    
    On my failover-station I still have got the FT-version, and in the
    quiet hours, I maybe can test new FT-kits.
    
    Gerrit
    
725.7PBUNIX::pgbAnd through the square window...Tue May 16 1995 11:2610
Gerrit,

  This is a problem we found on Friday and fixed Monday which is why 
 we didnt release a new kit as planned on Friday!

  Anyway, thanks for the confirmation that it is the same problem we 
 found, look for updated kits when we announce them later today.

Cheers,
Phil