It is possible to configure for both internal (built-in) and external (uploaded by user) scripts a timeout, a specified period of time until JetPatch terminates the task (5-hour maximum).
- Requires JetPatch connector version 220.127.116.11 and later
- Maximum timeout value for 'vm-max-in-process interval' is 21600
- Maximum timeout value for timeout_sec parameter is 17880
- The configured value in intigua.config.xml should be higher than the 'timeout_sec' parameter value for the built-in script
Connect to JetPatch Manager (application server) and configure intigua.config.xml file:
insert the timeout property 'vm-max-in-process interval' inside the 'system' parameter.
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 / set of endpoints.
To set timeout for external scripts:
- Create a script
- Go to System > Tasks
- Click the 'Add Task' Button
- Fill in all task details and insert a value to the timeout parameter (default is 300 sec)
- Run task (either as part of a remediation plan or run tasks manually on a set of server
Configure Script timeout for built-in scripts
The task 'Execute Patch installation' is a built in scripts which installs patches for every activated remediation plan. The default timeout value is 1h.
Example: Configure timeout for 'Execute Patch Installation for Single Computer'
1. 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'
2. Restart the Manager (service tomcat restart)
Note: for the other built-in scripts, change the SQL setting name condition from 'execute patch installation for single computer' to 'other built in script'