Overview

This article explains how to configure timeouts for all tasks scheduled by the JetPatch manager using the manager watchdog. 

Timeouts can be configured for both internal (built-in) and external (user-uploaded) tasks, with a maximum timeout period of 5 hours.

Manager Properties with Defined Timeout

Configuring intigua.config.xml File

Connect to JetPatch Manager (application server) and configure the intigua.config.xml file:

Insert the timeout property 'vm-max-in-process-interval' inside the 'system' parameter. 

This property ensures that after the configured time, a command will fail if it is not yet completed.

Example configuration:

Configurable the intigua.properties file:

Connect to JetPatch Manager (application server) and configure intigua.properties  file: 

for versions before 5.0

 vi /usr/share/tomcat/default/conf/intigua.properties

for versions post 5.0

 vi /usr/share/intigua/services/data/intigua-main/conf/intigua.properties

You can add the following properties and configure timeouts:

pg.wsus.fail-unfinished-tasks-timeout.min - Fail the WSUS related task after X minutes if it is not yet completed. 

# 3 hours by default for each of the WSUS tasks :
# 'WSUS get groups and computers in group','WSUS get update summaries per computer','WSUS get update summaries per group','WSUS get updates'
# If the property is changed between restarts, the WSUS scripts will use the new value
pg.wsus.fail-unfinished-tasks-timeout.min=180

# 5 minutes by default to get response for the finished task from the connector
# If the property is changed between restarts, the manager will wait for the response for this much seconds
automation.task.completion.timeout.sec=300

Configure Script timeout for built-in scripts

For built-in tasks, setting a timeout requires executing a database instruction. 

The 'timeout_sec' column in the database stores timeout values for both built-in and non-built-in tasks.

The task 'Execute Patch installation' is a built-in task that installs patches for every activated remediation plan. The default timeout value is 3 hours.

Example: Configure timeout for 'Execute Patch Installation for Single Computer' 

• Perform the following SQL setting :

# 17880 seconds is approx. 5h

update automation_task set timeout_sec = '17880' where name = 'execute patch installation for single computer'

• Restart the Manager (connect to JetPatch manager via SSH and run service tomcat restart for versions before 5.0 and restart Docker for post 5.0)

More on Built-in Tasks

• The "Collect Endpoints updates" task has a default non-configurable timeout of 1 hour. 
• A DB update is needed to change this value
• Every other built-in task has a default non-configurable timeout of 3 hours. 
• A DB update is needed to change this value.

Configure Script Timeout for External Scripts

The timeout is an external parameter that can be set to a different value every time you run a task on an endpoint or set of endpoints. 

For non-built-in tasks, it is possible to set the timeout parameter via the JetPatch GUI.

Steps to Set a Timeout for External Scripts

1. Create a script
2. Go to System > Tasks
3. Click the 'Add Task' Button
4. Fill in all task details and insert a value to the timeout parameter (default is 300 sec) 
5. Save
6. Run task (either as part of a remediation plan or run tasks manually on a set of servers)