Generating & Download JetPatch (Manager) Logs from the UI

If you are experiencing any issues with the JetPatch manager console,  please follow the below steps 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 

Please note: 

If you are not able to generate the manager logs, you will need to clean the log files in your core server, which are under /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 there are still issues, set the following properties to false in intigua.properties (/usr/share/tomcat/default/conf), and 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 the logs from the UI, you can alternatively get the manager logs via

/usr/share/tomcat/default/logs/*

In addition, to grab the NGINX logs, we need the following files:

/var/log/nginx/access.log
/var/log/nginx/error.log

Setting Manager Logs to Debug

Note: You should only do this when asked by a JetPatch team member.

• Changing the Manager’s logging level can be done by setting the logging level in the file called: /usr/share/tomcat/default/conf/log4j2.xml 
• For example, setting the log level to debug, you just need to uncomment the two debug lines

<!--Property name="LEVEL">DEBUG</Property>
<Property name="DEBUG_FILE">debugFileAppender</Property-->

Replace with:

<Property name="LEVEL">DEBUG</Property>
<Property name="DEBUG_FILE">debugFileAppender</Property>

• After setting the logging level, tomcat needs to be restarted.  
• Once in debug mode, please reproduce the issue and then gather the logs.
  • If the issue is not easily reproducible, leave DEBUG logs on for 60 mins.
• Once you gather the logs, comment out the debug lines again, and restart Tomcat again.

Troubleshooting Manager Logs

See the attached pdf (JetPatch Log Files) in how to use the manager logs.

More Information about Manager Logs

Each log has up to 10 files (by default - this is configurable), overwritten, Ordered from 1 to 9, such as the most recent is named without the number (e.g. vmanage.log)

• Discovery Source Logs: discovery.log.*
  • These logs are helpful in understanding automatic discovery thru discover sources (e.g. WSUS, AWS, vCenter, Azure, Active Directory)
• Patching Logs: patching.log.*
  • These are helpful in understanding problems related to remediation plans / patching
• vmanage.log.*
  • These are the logs used for aplicative logic done by the Manager server
• worker.log.*
  • Useful for connector issues
• Apache Tomcat (Application Server) Logs: Can be useful in cases of application server failures.
  • In cases of network problems or Java problems - access_tomcat.<date>.log.*, catalina.<date>.log.*, localhost.<date>.log.*
• Within the files folder (manifest and servermeta file): includes JetPatch build, tomcat version, linux version, java version, memory free/full, disk free and more 

Additional Configuration

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

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

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

//indicate number of activities that should be added to single file
download.activity.log.chunk.size=5000 

//indicate period in days from current moment, all finished activities in that period should be added to log file)
download.activity.log.period.days=2