Visara Master Console Center Administration Guide - Manual (Page 175)

Chapter 10 Maintaining Log Files
Administration Guide 175
Troubleshooting Problems with Console History Logging
The console history log is not displayed if no console history is being maintained
for the associated printer. If console history is unavailable, check the following:
ƒ Run the configuration checker (see CFGCHK Program on page 210). The
checker displays warnings if Days History is specified inconsistently or
incorrectly, or if the printer is not referenced.
ƒ Check the historylogger.log file for messages indicating why the history
logger is ignoring the relevant printer. Printers are ignored if Days History is
omitted or is 0 days. Printers are ignored if no OS refers to the printer.
ƒ Consoles are associated with printers through an OS. There must be an OS
configured that refers to both the console and the printer associated with it.
cpu.log: CPU Log
The CPU log is populated by scripts using the LOG command:
LOG(LOG_CPU, $Msg)
The CPU log can be viewed only through the Unix command line.
When CPU colors are manually changed with the Icon command of the MCC, a
message can be entered which is recorded to this log.
The format of cpu.log is as follows:
CYYYYMMDD HHMM [Operator Initials or Script Name] Message
Where C=Color/Status; YYYYMMDD=Year, Month, Date; HHMM=Hour,
Minute.
For example:
220061212 1349 JDA GX8 has lost communications.