Generating 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 

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/log4j.properties
• Remember to save the original values somewhere (either in a separate document are commented out), because you will need to revert back to the original values after generating the manager logs in debug mode.
• For example, setting the log level to debug:

LOG_LEVEL=debug
DEBUG_FILE=DEBUGFILE

MAX_FILE_SIZE=50MB
MAX_FILE_INDEX=20

• After setting the logging level, tomcat needs to be restarted.  
• Once in debug mode, please reproduce the issue and then gather the logs.
• Once you gather the logs, the LOG_LEVEL back to normal and restart tomcat again.

Troubleshooting Manager Logs

See attached pdf (JetPatch Log Files)

Additional Configuration

Available only in 4.2.4 UR3 and above (defaults below)

//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=7