Accessing and Using Log Files

Express Server uses six log files (including those of the optionally installed JPIP Server):

• Express Server Access Log
• Express Server Error Log
• Express Server JPIP Service Log
• Express Server JPIP Log
• Express Server Administration Log
• Express Server Admin Backend Log

These files are important tools for monitoring Express Server activity and diagnosing problems. The logs files are located in the directory <Express Server installation directory>/ImageServer/var/log, but you can easily access them via the Express Server Manager.

To access logs via the Express Server Manager:

1. Open the Express Server Manager (see Accessing the Express Server Manager).
2. Click Status on the top navigation bar, then click the name of a log in the "Download log files" list.

Some Notes on the Express Server Access Log

The access log file is analogous to a web server access log. It contains a record of all web requests handled by Express Server. For each request handled by Express Server, an entry is appended to this file.

The format of the access log is

date [thread ID] server client [requestID] [size] url [status]

where

• date is the date/time that the request was received
• thread ID is the thread that performed the processing
• server is the hostname/port of the server processing the request
• client is the IP address of the client making the request
• requestID is a numerical ID assigned to the request by Express Server
• size is the size in bytes of the response
• url is the actual request URL being processed
• status is the status of the request – 0 indicates success, all else indicates failure

Some Notes on the Express Server Error Log

The error log file contains error messages, warnings, informational statements, and debug information. You can specify the level of information written to this log file (see Setting Basic Express Server Settings)

The format of the error log is

date [thread ID] [type] [status] message

where

• date is the date/time that the message was generated
• thread ID is the thread that performed the processing

• type is the type of message, one of those in the following table

  Error Log Message Types

  Message	Notes
  emerg	an emergency situation in which Express Server cannot operate
  alert	an emergency situation in which Express Server cannot operate
  criti	a critical failure
  error	an error occurred and was handled
  warni	a warning
  notic	information that is normal, but also significant
  infor	additional information that may be of interest
  debug	information that may be helpful for debugging

• status is the status of the request – 0 indicates success, all others indicate failure
• message is a text message describing the condition