On-prem agent (OPA) error troubleshooting ​

Use this guide to troubleshoot common issues with the Workato on-prem agent (OPA). These guides cover setup, upgrades, runtime behavior, and extensions.

Choose a guide based on the issue you plan to troubleshoot:

• Setup and installation issues: Covers agent startup failures, permission errors, directory creation problems, and proxy-related SSL errors.
• Upgrade and configuration issues: Fixes post-upgrade failures, service account resets, and connection profile changes.
• Runtime and performance issues: Resolves heap memory crashes and large response buffering problems.
• Connection issues: Resolves Java extension errors as well as connection errors for SFTP and Kafka.

OPA log generation and retention ​

You can use OPA logs to identify agent behavior and system issues during execution. The OPA generates a new log file daily based on the on-premise system time. If a log file exceeds 20 MB within a day, a new one is created and numbered sequentially. For example, if /agent-2019-11-01.0.log is the first log of the day, additional logs for the same day are /agent-2019-11-01.1.log and /agent-2019-11-01.2.log. The OPA retains the latest 60 log files or a maximum of 20 GB of logs.

Locate OPA logs ​

You must locate the log files to troubleshoot OPA issues. Depending on your operating system, complete the following instructions for Windows or Linux:

journalctl -u [name of the OPA service].service

journalctl -u workato.service --since "2020-07-26 23:15:00" --until "2020-08-5 23:20:00" > OPALogs.txt

Job-specific troubleshooting ​

Use the job ID to search OPA logs and trace job execution across all stages. This allows you to isolate OPA-specific operations within a single job. For example: j-AHd9XdsW-JppW.

Locate jobs