[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

541.0. "Console LOG Data MISSING from LOGFILE" by BSS::LIND (Jim Lind; 592-4099 CX03-1/N14 CNMC-West) Tue Jan 03 1995 19:20

    SOFTWARE:	OpenVMS VAX V6.1
    		PCM V1.5-002

    PROBLEM:	Console Log Data Missing from Log File

    It has been reported several times that console data appears
    to be missing from log files.

    I have verified that this is indeed the case ... 

    "$ CONSOLE MONITOR node" will provide a log file, but appears to
    NOT have the latest console data of as much as 30-40 screens
    of information.

    ANALYSIS:

    To verify the contents of the logfile, BACKUP was used to make a
    copy of the logfile for a node, then the editor was used to browse
    that file:

    	$ BACKUP /IGNORE=INTERLOCK CONSOLE$LOGFILES:node_name.LOG JUNK.TMP
    	$ EDIT JUNK.TMP

    Go to the bottom of the file, check date of last entry - note if
    the log file info had ended with information from several days ago,
    where this should not be the case.

    WORKAROUND:

    On the PCM node, $ CONSOLE MONITOR node

    In another screen, login to the problem node.  Force output to the
    console on the problem suspect node by logging into that node and
    sending output to the console:

    	$ COPY TT: OPA:
    	This is a test! ctrl-Z

    Notice if the log file in the MONITOR WINDOW is updated.  Experience
    shows that this forced output to the console port MAY force log
    data from memory to the log file.

    Verify the contents of the logfile using the editor as mentioned 
    in the ANALYSIS portion of this note.

    Jim Lind 
T.RTitleUserPersonal
Name
DateLines
541.1OPG::PHILIPAnd through the square window...Wed Jan 04 1995 10:3712
Jim,

  The behaviour you are seeing is something we are aware of. Two things...

  1) Can you retry your experiment when we re-release the MUP kit

  2) Using Backup (even with /IGNORE=INTERLOCK) is not guaranteed to get all 
     the data as the daemon will most likely still have som in its internal 
     buffers.

Cheers,
Phil
541.2No Missing Log Data Since MUPBSS::LINDJim Lind; 592-4099 CX03-1/N14 CNMC-WestMon Jan 16 1995 18:574
    Have not seen the porblem with missing log data since installation
    of the MUP.
    
    Jim Lind
541.3OPG::PHILIPAnd through the square window...Mon Jan 16 1995 20:094
Excellent, thanks for the feedback.

Cheers,
Phil