Examining the Endeca IAS Service log

The Endeca IAS Service logs messages for all IAS components and crawls in the ias-service.log file.

Location of the IAS Service log

The Endeca IAS Service has one (and only one) log, regardless of how many crawls have been configured. The log is named ias-service.log and is located in the logs directory in the IAS workspace directory. If you are using the default workspace directory name, the pathname of the log file is similar to this: 
C:\Oracle\Endeca\IAS\workspace\logs\ias-service.log

Format of log entries

The log contains two types of log entries:
  • IAS component log entries, which are entries that pertain to starting and stopping IAS components.
  • Crawl log entries, which are entries that pertain to a specific crawl.
By default, crawl log entries have the format: 
yyyy-MM-dd HH:mm:ss,SSS logLevel [component] [thread name] class: <message>
where:
  • yy-MM-dd HH-mm-ss is the timestamp of the entry. You can change the format by editing the ias-server.log4j.properties file.
  • logLevel is the log level of the entry, such as INFO or FATAL.
  • component is ias (for the crawl manager), ComponentInstanceManager, or instance name for Record Stores.
  • thread name is the name of the processing thread for the message.
  • message is the message returned by a IAS Server module.

Enabling crawl statistics

If a crawl log level is set to INFO, TRACE, or DEBUG, the crawl statistics are entered as INFO entries in the log when the crawl finishes, as in this example (timestamps and log levels are omitted for ease of reading): 
Crawl Mode = FULL_CRAWL (MetricsReport)
Crawl Stop Cause = Completed (MetricsReport)
Directories Filtered from Archives = 0 (MetricsReport)
Directories Filtered = 0 (MetricsReport)
Total Records Output = 423 (MetricsReport)
Files Filtered from Archives = 124 (MetricsReport)
Directories Crawled Not from Archives = 55 (MetricsReport)
Documents Unsuccessfully Converted = 9 (MetricsReport)
Files Crawled from Archives = 65 (MetricsReport)
Files Crawled Not from Archives = 285 (MetricsReport)
Delete Records Output = 0 (MetricsReport)
Files Filtered Not from Archives = 51 (MetricsReport)
Directories Crawled = 73 (MetricsReport)
Directories Filtered Not from Archives = 0 (MetricsReport)
Documents Converted = 333 (MetricsReport)
Files Crawled = 350 (MetricsReport)
Documents Converted After Retry = 0 (MetricsReport)
New or Updated Records Output = 423 (MetricsReport)
Directories Crawled from Archives = 18 (MetricsReport)
Files Filtered = 175 (MetricsReport)
Crawl Seconds = 71 (MetricsReport)
Start Time = 5/23/08 9:23:59 AM EDT (MetricsReport)
End Time = 5/23/08 9:25:10 AM EDT (MetricsReport)

Note that for incremental crawls, the Delete Records Output statistic is also included and indicates how many files were deleted from the previous crawl. An Endeca record is created for each deleted file; the record will have the Endeca.Action property set to DELETE.

The Crawl Stop Cause statistic has one of the following values:
  • Completed
  • Failed
  • Aborted
If a crawl fails, the Crawl Failure Reason statistic provides a message from the IAS Server explaining the failure.

Keep in mind that if the log is too verbose (thus making it more difficult to find errors), you can change the log level of the crawl. The default log level is INFO.

The IAS logging configuration file is ias-service-log4j.properties and is located in the <install path>\IAS\workspace\conf directory. You can also change the log level on a per-crawl basis using the IAS API or the IAS command-line utilities.