Rhapsody And EasySpooler Logs

One of the strong features in managing printer or destination issues in Rhapsody or EasySpooler is the extensive information recorded in the various logs. There are five catagories of logs:

1. Startup Log
2. Server Logs
3. Archive Server Logs
4. Activity Log
5. WebUI Log or EZGui Log

1. There is one Startup Log and it is called “rclog”. The rclog log is only relevant for Unix and Linux servers and displays information about the master or backup server processes. It gives information about any problems encountered during initialization. Rebuilding the Queue or Printer Control files also record entries in the rclog.
2. There are two types of Server Logs, log_ev and log. The “log_ev” server log, which is for Rhapsody’s master server only, shows communicaton activity between the master server and all of the satellite servers. The “log” server log, for both Rhapsody and EasySpooler, shows communication activity to and from that server only. Setting specific environmental variables instructs Rhapsody or EasySpooler to include or exclude debug information in the “log”. Raising or lowering the msglevel setting allows you to control the level of detail captured in the “log”.
3. Archive Server Logs. These are just saved historical Server Logs. You can archive up to 999 log files for the master server and, in the case of Rhapsody, for each of the satellites by setting the global tuning parameter “logrollmax”. You can also specify the day and time that Rhapsody or EasySpooler restarts the log files by setting the global tuning parameter “killlog”. You can also manually start new log files at any time.
4. Activity Log. Is an optional log that records system activity on each satellite for Rhapsody or on the server for EasySpooler. Data is recorded to the “activity_log” by turning on the “act_log” global tuning parameter. The data captured in the “activity_log” file can then be used by the system activity reporting program(s) developed by each Rhapsody or EasySpooler customer. A “report_act” script is provided as a sample script that can be used to print a basic report of the data captured in the “activity_log” file.
5. WebUI Log or EZGUI Log. The WebUI and EZGUI automatically writes error message to the “webserver.log” or the “error_log_txt” files. If DEBUG is turned on in the WebUI, the debug information is also recorded in the “webserver.log” file. If DEBUG is turned on in the EZGUI, the debug information is recorded in the “debug_log_txt” file.