Conference csc32::consolemanager

    
    PCM V1.5 has been running on our production management station 
    little bit over one day.
    
    Console Ctrl 04 processes is now looping. I had to stop it?
    What kind of informatio we should collect if this happens again?
    We have 49 systems connected with LAT. VMS version V6.1 (VAX)
    
    When I restarted PCM I'll get accvio when I try to make conenction
    to certain systems.
    
    -Olli              

Olli,

  We have had this reported here in Reading too, I am collecting the 
  necessary data locally, so at the moment we dont really need anything from 
  you, but thanks for the offer and thanks for reporting this here.

  I will update this topic again when I have some more info (which wont be 
  until next week sometime as I am out of the office tomorrow and Monday is a 
  public holiday here).

Cheers,
Phil

Hi, 


Was this one ever resolved?


I have a customer who has a VMS V6.1 machine running 
PCM and he's monitoring a digital unix box. 

His VAXen seem fine but the Alpha Unix box is showing 
defunct processes and he can't release the console or terminal 
server port from them. 

He's connecting over telnet, port is set up as below, also 
the config of the unix box on the PCM system is tagged on too.
His inittab looks quite normal. 

Was there a problem with V1.5 not releasing the telnet 
link correctly? Was it fixed in a later release?

I'll be encouraging him to upgrade anyway but it'd help 
to know at which version (or if) it was fixed. 


Thanks 


Jo Coffey. 

----------------------------------------------------




System Name         = bgsa01
    Information     = BGSA01 Alphaserver 2000
    Connection      = TELNET (terminal server)
    Terminal Server = BGAT06
    Listener Number = 2004
    Scan Profile    = unix    UNIX System V Scan Profile
    Icon filename   = DECSYSTEM_5100.XBM
    Console line    = Enabled
    Logging is enabled, directory = CONSOLE$LOGFILES
Port  4:                               Server: BGAT06

Character Size:            8           Input Speed:               9600
Flow Control:            XON           Output Speed:              9600
Parity:                 None           Signal Control:        Disabled
Stop Bits:           Dynamic           Signal Select:  CTS-DSR-RTS-DTR

Access:               Remote           Local Switch:              None
Backwards Switch:       None           Name:                    PORT_4
Break:              Disabled           Session Limit:                4
Forwards Switch:        None           Type:                      Ansi
Default Protocol:     Telnet

Preferred Service: None

Authorized Groups:   0
(Current)  Groups:   0

Enabled Characteristics:
Input Flow Control,  Loss Notification,  Message Codes,
Output Flow Control,  Verification

Hi,

I have taken this over from Jo.
The customer refuses to upgrade to 1.6 or ECO1 without assurances that this
problem has been addressed. Does anyone know whether or not it was?

Thanks in advance,

Ian.

    Ian,
      Several issues with TELNET were resolved in V1.6. I have never had a
    report of this problem with V1.6 at all.
    
    Regards,
       Dan

Thanks Dan,

I'll feed this back to the customer.

Ian.