Troubleshooting
status_log
The status_log contains information about the attributes of a job once it has been accepted and tracked by the system.
The attribute information found in this file is as follows (the sequence and attributes displayed vary with the job):
Logging Module /t# Sender Name /t# Data Size /t# Document
Name /t# Document Format /t# Job ID /t# Virtual Printer Name /t#
Message /t# Time /t# Network Protocol /t# Assigned Physical
Printer /t# Plex /t# Plex Requested /t# Disposition
ep_exception_log and ep_primary_log
These logs contain a list of faults. The ep_exception_log contains
alisting of all logged faults. The ep_primary_log contains exceptions that are the primary cause of the problem.
The format of these files is as follows:
Logging Module /t# Absolute Time /t# Microseconds /t# Instance
ID:Module TD /t# Exception ID /t# Service Code
LPR logs
The following logs are important for troubleshooting problems in mapping NPS and Xerox FreeFlow Print Server:
•LPR logs that contain information related to the LPR gateway such as missing jobs or communications problems.
Examples: /opt/XRXnps/log/XLP/Debug.Log
•JPM logs that contain information related to the Job Pool Manager (JPM). The attribute set by the LPR Gateway can be checked and verified by looking at this log: /opt/XRXnps/ log/JPM.Debug.Log.
Printing the accounting log
Print the Accounting log to gather information and recover from various accounting problems. Either the entire Accounting log or a portion of the log may be printed. This can be completed on the Xerox FreeFlow Print Server interface in the [Administration] section.
System Guide |