[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

824.0. "Problem with DIALOG and boot (PCM 1.5)" by UTRTSC::DORLAND (There's always one more bug!) Fri Jun 16 1995 15:27

    Hello,
    
    a customer reported a problem with DIALOG.
    He tries to perform a dialog which does a 
    shutdown, boot S/A backup,
    perform S/A backup and reboot the system.
    
    However, during the first boot phase he sees :
    
    >>> boot -flags 0,0 dka400
    
    init-s-scpu...
    init-s-reset-tc...
    
    At this point PCM reports  
    
    connection between line sensor and remote console has been lost
    
    2 minutes later he sees 
    
    link to system lim006 reestablished
    
    followed by a clear of the screen and a stackdump.
    
    After reconnecting he sees that the system is continuing 
    with the S/A backup but the dialog file is now completely
    confused.
    
    Is this a known problem ? (PCM 1.5) fixed in 1.6 ?
    
    Thanks in advance,
    
    Ton
T.RTitleUserPersonal
Name		DateLines
824.1CSC32::BUTTERWORTHGun Control is a steady hand.Tue Jun 20 1995 19:2636
>    connection between line sensor and remote console has been lost
    
    This means that link between the decserver (or whatever) was lost. This
    is the real problem.
    
>    2 minutes later he sees 
>    link to system lim006 reestablished
    
    Which makes sense because the timer to check line status and attempt
    reopens runs every 150 seconds.
    
>    Is this a known problem ? (PCM 1.5) fixed in 1.6 ?
    
     Not really. I don't think you have a problem with DIALOG in itself.
    It almost like the combination of doing a dialog plus all the messages
    being output due to the boot is causing us to drop the connection. What
    we need is for the customer to turn on debug via the following command:
    
    
    DEFINE/SYS CONSOLE$DEBUG DAEMON
    
    This will cause *a lot* of output to get logged to the logfiles in
    CONSOLE$TMP. The point is the customer should, turn the logical on,
    restart PCM, reproduce the problem, shutdown the software, *copy the
    logfiles from CONSOLE$TMP* and then deassign the logical and restart
    PCM. The copy step is most important as the CONSOLE$STARTUP procedure
    will delete them when you do the final restart. Just post the logfiles
    here. We are most interested in the CONTOLLER_0x logfiles from the
    actuall line controllers. We really only need the one frrom the
    controller that was handling the failing system. You'll have to look at
    each one for messages regarding the closing and reopening of that
    systems console line to find the right one.
    
    Regs,
      Dan