[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

796.0. "MLS+ and PCM problem" by MARVEL::MCNULTY () Wed Jun 07 1995 18:58

[ Cross posted to MKOTS3::DEC_MLS_PLUS, note 149 ]

Folks,

I've had a customer ( a very large one with *lots* of MLS+ boxes on the way )
log a call today.  He's got the following problem.

They're running, MLS+ v3.1 and Polycenter Console Manager (PCM) v1.5

He has an MLS+ system with a terminal server connected to the console.  If he
installs PCM on a standard OSF/1 system, then he can connect to the remote
console without any problems.

If he then installs PCM on a second MLS+ system and uses that to connect to
the remote console, it fails with this message:

                (Note:  this was dictated over the phone)

    Process 567 exited "console manager" xio: fatal i/o error 32 (broken pipe)
    on Xserver "0:0.0" after zero requests (0 known processed) with 0 events
    remaining.

    The connection was probably broken by a server shutdown or kill client


Impact
~~~~~
They need a pretty speedy answer to this.  Either a fix, or an answer which
says it won't work so they can re-think their approach.  The systems which 
are to be installed will not all have graphics heads.

Questions
~~~~~~~~
  -  Is this a known problem with PCM which is not related to MLS+

  -  Has PCM ever been tested/qualified with MLS+


Regards,

John McNulty 
UK CSC, UNIX Support Group
 
    
T.RTitleUserPersonal
Name
DateLines
796.1CSC32::BUTTERWORTHGun Control is a steady hand.Thu Jun 08 1995 22:3336
>He has an MLS+ system with a terminal server connected to the console.  If he
>installs PCM on a standard OSF/1 system, then he can connect to the remote
>console without any problems.

>If he then installs PCM on a second MLS+ system and uses that to connect to
>the remote console, it fails with this message:
    
    Are you saying that he has two different PCM engines and both PCM
    engines the same node configured into the database and that all config
    data is identical down to the terminal server name and port number?
    
    If so then this is the first problem. You *cannot* actively manage the
    same system from more than one PCM engine at a time. This is because
    the terminal server port the system is connected can only have one
    LAT or TELNET connection at a time. Sure you can shut down PCM on the
    engine that is currently connected to the port and then start up
    PCM on the other engine and it will now be managing the console of the
    system in question. You can also login to the engine that is currently
    managing everything and set your X-display back to any X-capable windowing
    system and then send the C3 back to it but this is al W-windowing
    protocol nad doesn't have a thing to do with LAT or TELNET connections
    to a server port.

                (Note:  this was dictated over the phone)

>    Process 567 exited "console manager" xio: fatal i/o error 32 (broken pipe)
>    on Xserver "0:0.0" after zero requests (0 known processed) with 0 events
>    remaining.
    
    Now this sounds like your trying to send the C3 back to some remote
    display. Check to make sure the Session Manager security on the remote
    display allows access to the display for the PCM engine and userid that
    your running the C3 from.

Regs,
      Dan