Skip to main content
Kofax

Kapow Log Matrix

13529
Component File Name/Table Name Folder/Location Comment

Management Console

(deployed into Tomcat)

service-stdout.YYYY-MM-DD.log

<Tomcat installation folder>\logs

E.g. C:\Program Files\Apache Software Foundation\Tomcat 8.0_Apache_Tomcat8\logs

 
service-stderr.YYYY-MM-DD.log

<Tomcat installation folder>\logs

E.g. C:\Program Files\Apache Software Foundation\Tomcat 8.0_Apache_Tomcat8\logs

 

catalina.YYYY-MM-DD.log

or

catalina.out

<Tomcat installation folder>\logs

E.g. C:\Program Files\Apache Software Foundation\Tomcat 8.0_Apache_Tomcat8\logs

 
RoboServer

Wrapper.log
 

- not enabled by default, see Comment column

Custom, defined by

wrapper.logfile parameter

or

<Kapow installation folder>\bin

E.g. D:\Program Files\Kapow 9.7.4 x64\bin

To enable, uncomment and edit the lines below in common.conf and restart RoboServer:

wrapper.logfile.loglevel=DEBUG
wrapper.logfile=C:\logs\WrapperDebug_RoboServer_ROLLNUM.log
wrapper.logfile.rollmode=SIZE_OR_WRAPPER
wrapper.logfile.maxsize=50m
wrapper.logfile.maxfiles=10

Server Messages

Logs tab in Management Console > RoboServer

or, directly in the RoboServer Log Database:  in the SERVER_MESSAGE table

You can set up the retention policy for your logs in the RoboServer Log Database by specifying a number
of days to keep the logs and a number of messages in the robot run. The logs are cleaned on a daily
basis by deleting the oldest messages first. The default values are 10 days and 500 messages.

This setting can be changed from Management Console > Admin > Settings > RoboServer Log Database.

Kapow Browser Crash Dump

Windows:

C:\Users\UserRunningService \AppData\Local\Temp\Kapow

Linux:

/tmp/Kapow

 
Instant Crash Dump Run process explorer, right click on the kapowbrowser.exe from which you what to extract the dump: Create Dump > Create Full Dump... or Create Minidump... To identify the PID of the related -ona | find "50001" (if the Kapow on the RobotServer 50001)
Robot Robot Runs and Robot Messages

Logs tab in Management Console

or directly in the RoboServer Log Database: ROBOT MESSAGE and ROBOT_RUN tables

You can set up the retention policy for your logs in the RoboServer Log Database by specifying a number
of days to keep the logs and a number of messages in the robot run. The logs are cleaned on a daily
basis by deleting the oldest messages first. The default values are 10 days and 500 messages.

This setting can be changed from Management Console > Admin > Settings > RoboServer Log Database.

Crash Dump C:\Users\UserRunningService \AppData\Local\Temp\Kapow Enabled by default
Schedules Schedule Runs and Schedule Messages

Logs tab in Management Console

or directly in the RoboServer Log Database: SCHEDULE_RUN and SCHEDULE_MESSAGE tables

You can set up the retention policy for your logs in the RoboServer Log Database by specifying a number
of days to keep the logs and a number of messages in the robot run. The logs are cleaned on a daily
basis by deleting the oldest messages first. The default values are 10 days and 500 messages.

This setting can be changed from Management Console > Admin > Settings > RoboServer Log Database.

Desktop Automation

Device Automation Service.log

or

Desktop Automation Service.log (since version 10.4)

C:\Users\UserRunningService \AppData\Local\Kapow\<version>\Logs Can also be reached from the DAS Configuration Tool > System tab

Keywords: Kapow Log Matrix, Kapow, Robotic Process Automation

  • Was this article helpful?