Skip to Content

Private agent log files

Introduction

Agents generate log messages (logs) that can help you to understand, debug, and monitor your integration projects and the systems they run on. This page catalogs them by location, where JITTERBIT_HOME is the private agent installation directory, (by default, C:\Program Files\Jitterbit Agent\ on Microsoft Windows, /opt/jitterbit/ on Linux).

JITTERBIT_HOME/log

Log file Description
AgentMetric.log JSON-formatted log for observability.
AgentSyncMetrics.log JSON-formatted log for observability.
CleanupService.log Cleanup service log file.
Installer.log Installer log file, written to when the agent is installed or upgraded.
JdbcEngine0.log Java log file.
JitterbitFileCleanup.err Cleanup service error file.
JitterbitProcessEngine.err Process engine error file.
JitterbitScheduler.err Scheduler error file.
JitterbitVerboseLogShipper.err Verbose log shipper error file.
JitterbitVerboseLogShipper.out Verbose log shipper output file.
OperationEngine.log Operation engine log file.
ProcessEngine.log Process engine log file.
Scheduler.log Scheduler log file.
entrypoint.log entrypoint.sh log file. (Only for Docker agents.)
jitterbit-agent.log Main private agent log.
jitterbit-axis.log Verbose connector log file.
jitterbit-component-listener.log JMS connector log file for Integration Studio and Design Studio.
metrics.log Jitterbit private agent metrics.
metrics_service.log Jitterbit private agent metrics.
tomcat_control.log Tomcat summary log file.

JITTERBIT_HOME/apache/logs/

Log file Description
access_log Apache HTTP access log file
apache_crash.txt Crash log file, recording the operation ID. To enable, set EnableOperationIdLogging=true in [APIOperation].
error_log Apache HTTP error log file

JITTERBIT_HOME/tomcat/logs/

This contains Apache Tomcat log files. To enable them, set the following parameters:

JITTERBIT_HOME/DataInterchange/Temp/Debug/

This contains component I/O data log when operation-level debug is enabled, and operation-level debug log files. To enable them, set the following parameters:

Curl logs

To enable (S)FTP and HTTP(S) curl logs, set CurlDebugDir in [Settings].

Each line of a curl log file starts with one of the following keywords to indicate the type of information:

  • CURL_DEBUG_TEXT: Messages.

  • CURL_DEBUG_HEADER_IN: Header information sent to the endpoint.

  • CURL_DEBUG_HEADER_OUT: Header information sent from the endpoint.

  • CURL_DEBUG_DATA_IN: Data sent to the endpoint.

  • CURL_DEBUG_DATA_OUT: Data sent from the endpoint.

  • CURL_DEBUG_OTHER: Any other type of message.

Example curl log for FTP connector activity
CURL_DEBUG_TEXT: Uses proxy env variable no_proxy == 'localhost,127.0.0.1'
CURL_DEBUG_TEXT:   Trying 123.456.789.001:21...
CURL_DEBUG_TEXT: TCP_NODELAY set
CURL_DEBUG_TEXT: Connected to ftp.example.net (123.456.789.1) port 21 (#0)
CURL_DEBUG_HEADER_IN: 220 FTP Server 1.2.3
CURL_DEBUG_HEADER_OUT: USER user.name
CURL_DEBUG_HEADER_IN: 331 Please, specify the password.
CURL_DEBUG_HEADER_OUT: PASS *****
CURL_DEBUG_HEADER_IN: 230 Login successful.
CURL_DEBUG_HEADER_OUT: PWD
CURL_DEBUG_HEADER_IN: 257 "/" is current directory.
CURL_DEBUG_TEXT: Entry path is '/'
CURL_DEBUG_HEADER_OUT: EPRT |1|123.456.789.1|21|
CURL_DEBUG_TEXT: ftp_perform ends with SECONDARY: 1
CURL_DEBUG_HEADER_IN: 200 EPRT command successful.
CURL_DEBUG_TEXT: Connect data stream actively
CURL_DEBUG_HEADER_OUT: TYPE A
CURL_DEBUG_HEADER_IN: 200 Type set to A
CURL_DEBUG_HEADER_OUT: APPE test.txt
CURL_DEBUG_HEADER_IN: 150 Starting data transfer.
CURL_DEBUG_TEXT: Preparing for accepting server on data port
CURL_DEBUG_TEXT: Checking for server connect
CURL_DEBUG_TEXT: Ready to accept data connection from server
CURL_DEBUG_TEXT: Connection accepted from server
CURL_DEBUG_DATA_OUT: EXAMPLE DATA
CURL_DEBUG_TEXT: We are completely uploaded and fine
CURL_DEBUG_TEXT: Remembering we are in dir ""
CURL_DEBUG_HEADER_IN: 226 Operation successful
CURL_DEBUG_TEXT: Connection #0 to host ftp.example.net left intact