Using diagnostic, usage, and error logging : Configuring usage and error logging : Understanding an error log entry
 
Understanding an error log entry
Each error log entry is a comma-separated list containing up to 12 fields about an error-related event. The following example describes an error in a submit job event:
3272648796,2,3230,SubmitJob,Administrator,"Invalid start time or end time.",urup,urup,urup,-,-,-
A dash in the usage log entry means the field is not used. The error log organizes the entry fields into the following information groups:
*Fields 1 through 9 contain general information:
*Field 1 contains the log file time stamp. The time is in seconds since 00:00:00, Jan. 1, 1901, GMT.
*Field 2 contains the error severity level, an integer between 1 and 4. The numeric values in Table 3‑4 indicate the level.
Table 3‑4 Error severity levels and the corresponding values 
Error severity level
Value
Information
1
Warning
2
Severe
3
Fatal
4
*Field 3 contains the error ID code.
*Field 4 contains the service name, indicating the subsystem where the error occurred such as the Factory, Encyclopedia, View, or Request service.
*Field 5 indicates the Encyclopedia volume user.
*Field 6 contains the error message.
*Field 7 contains the Encyclopedia volume name.
*Field 8 contains the iHub cluster name.
*Field 9 contains the iHub node name.
*Depending on the error, fields 10 through 12 can contain information such as a file name and ID number.
Table 3‑5 summarizes some of the information available in fields 10 through 12 for an error log entry at standard level.
Table 3‑5 Information that is available for error log entries at the standard level 
Type of error
Operation data available
Encyclopedia volume user activity
Fields 10 through 12 can contain error parameters such as the following items:
*Object name
*ID number
Volume online or offline
Fields 10 and 11 contain the following data:
*Volume name
*Operation type either online or offline
iHub node start or stop
Field 10 contains the iHub name.
Service enable or disable
Fields 10 and 11 contain the following data:
*Server name
*List of services
Archive service error
Fields 10 through 12 contain error parameters.
Encyclopedia volume job purging
Field 4 is Job Purge
Fields 10 through 12 contain error parameters.
Encyclopedia volume health monitoring
Field 4 is Encyclopedia Health Monitor
Fields 10 through 12 contain error parameters.
Table 3‑6 lists the general categories of iHub error messages.
Table 3‑6 Categories of iHub error messages
Error ID range
Error description
0001 - 1000
System errors such as Out of memory or Low thread count
1001 - 3000
iHub errors such as Corrupt encyclopedia or Transient storage full
Within this error category, the following sub-categories exist:
*1001 - 2000 Actuate internal datastore
*2001 - 3000 Actuate internal
3001 - 6000
User errors such as Permission denied
Within this error category, the following sub-categories exist:
*3001 - 4000 Encyclopedia engine
*4001 - 5000 Report engine
*5001 - 6000 View engine
6001 - 12000
*6001 - 7000 SOAP engine
*7001 - 8000 Process management daemon
*8001 - 9000 Cluster engine
*10001 - 11000 Server configuration
*11001 - 12000 XML parsing
12001 - 13000
Viewing server errors
13000 - 14000
AcMail exceptions
100001 - 100600
Actuate Information service
100601 - 100699
Actuate Caching service
100700 - 150000
Shared by Actuate Information service and Actuate Caching service