Overview

This article explains how to generate and download JetPatch manager logs from the UI, retrieve them directly from the server, set logging to debug level, and configure advanced logging properties. 

Use this guide when troubleshooting issues with the JetPatch manager console and when the JetPatch support team requests log files.

Generating & Downloading JetPatch Logs from the UI

If you are experiencing issues with the JetPatch manager console, follow the steps below and send the relevant information to the JetPatch support team.

Option 1 - JetPatch Console

Open the "Support" menu in the top right of the JetPatch Console (accessible from any page in the JetPatch Console) and click on "Download JetPatch Logs."

Option 2 - Platform Configuration 

1. In platform configuration, click on Logs & Alerts

2. Click on Actions  -> Prepare Log Service 

If you are unable to generate the manager logs (till version 4.2.x)

You will need to clean the log files in the core server under the /tmp folder:

1. SSH to your JetPatch console
2. Run the following command (please copy the following line with NO changes):
   
   rm -rf /usr/share/tomcat/default/temp/*
3. Try to download logs again 

If issues persist, set the following properties to false in intigua.properties (/usr/share/tomcat/default/conf), then restart Tomcat:

//toggles whether monitoring files should be added to logs
download.monitoring.log.enabled=false

//toggles whether activities should be added to logs
download.activity.log.enabled=false

Gathering Logs from the JetPatch Server Itself

If you are unable to generate logs from the UI, retrieve them directly from the server.

Before version 5.0

Manager logs:

NGINX logs:

Version 5.0 and later

Setting Manager Logs to Debug (till version 4.2.x)

• Change the logging level in the file: /usr/share/tomcat/default/conf/log4j2.xml
• To set the log level to DEBUG, uncomment the two debug lines:

• After changing the logging level, restart Tomcat.
• Once in debug mode, reproduce the issue and then gather the logs.
  • If the issue is not easily reproducible, leave DEBUG logs on for 60 minutes.
• After gathering the logs, comment out the debug lines again and restart Tomcat.

Manager Log Files Reference (till version 4.2.x)

Each log has up to 10 files by default (configurable), ordered 1–9. The most recent file has no number suffix (e.g., vmanage.log).

• discovery.log.* - Discovery Source Logs
  • Helpful for understanding automatic discovery through discovery sources (WSUS, AWS, vCenter, Azure, Active Directory).
• patching.log.* - Patching Logs
  • Helpful for understanding problems related to remediation plans and patching.
• vmanage.log.*
  • Logs for applicative logic executed by the Manager server.
• worker.log.*
  • Useful for connector issues.
• Apache Tomcat logs - useful for application server failures:
  • access_tomcat.<date>.log.*, catalina.<date>.log.*, localhost.<date>.log.*
• files folder (manifest and servermeta): includes JetPatch build, Tomcat version, Linux version, Java version, memory, and disk info.

Additional Configuration (before version 5.0)

Properties in intigua.properties (/usr/share/tomcat/default/conf/):

By default, each manager's log has 20 files, each sized at 10 MB.

To override default settings for a specific log type (e.g., patching.log), modify the log4j.xml file at:

Example: Increasing file size to 30 MB and maintaining up to 25 files for patching.log, while keeping default settings for events.log: