In addition to this article, more detailed logging can be found on an endpoint's connector logs. If you are seeing an issue on multiple machines, take a look at the manager logs.
JetPatch Built-In Scripts
The following table is fit for JetPatch built-in scripts
| Script (OS) | Exit Code | Description | Meaning and Next Step | |
| execute patch (All) | 1 |
{"Installations": [{"UpdateId":"", "KB":"",
"status":"install/remove/download_ fail","transactionId":""}]}
|
|
|
| execute patch (Linux) | 5 | Could not get script file output | Check the endpoint's date and time settings, it may be incorrect. | |
| Check if Linux Reboot is Required... | 10 |
|
No Restart Required | |
| execute patch (Linux) | 11 | Could not get script file output | The script didn't get the MW to start time from the Manager | |
| execute patch (Linux) | 12 | Could not get script file output | The script didn't get the MW end time from the Manager. Retry | |
| Collect Endpoint Updates (Linux) | 13 | This endpoint is not registered to Red Hat Subscription Management (the status is <SUBSCRIPTION_STATUS>). please check the Red Hat subscription. |
There is no subscription to the endpoint Check RHEL subscription Please run the following commands: yum repolist |
|
| execute patch (Linux) | 13 | Could not get script file output | The script didn't get package/advisories to install/remove | |
| Collect Endpoint Updates (Linux) | 62 | The system is busy with other YUM command/s (running for the last <TIME_OF_OTHER_YUM_PROCESS>). Please consider checking the yum service on the endpoint. | There is another process that is locking the YUM command | |
| All Scripts (Linux) |
62 | Timeout reached from the Connector side. The script was executed more than the expected time |
||
| Collect Endpoint Updates (Linux) | 85 |
{ "Packages" :[]} { "Advisories" :[]} |
The output has empty data. Linux: Likely an endpoint issue (network problem or incorrect proxy settings, especially if there are 403 errors). Please troubleshoot the endpoint. (1) Configure Endpoint Readiness and verify 100% success. (2) Check if advisories/packages are pulling properly SUSE: zypper pch
For RHEL/OL/Amazon - you should see advisory data like: RHSA-2014:1031 Important/Sec. 389-ds-base-1.3.1.6-26.el7_0.x86_64 RHSA-2015:0416 Important/Sec. 389-ds-base-1.3.3.1-13.el7.x86_64 RHBA-2015:0626 bugfix 389-ds-base-1.3.3.1-15.el7_1.x86_64 If you do not see advisory data, then verify repo xml. If repo xml file is correct, yum clean all
(3) If advisories and packages are being pulled properly, then run the following command: rm -rf /var/cache/JetPatch/scan_result.txt && /usr/local/scan_updates.sh true null null
Note: this command will clear the local updates file and will create a new one,
which will be pulled in the next scan. The result of this command should be a list of all the advisories/packages. For more SUSE help, see this cheat sheet |
|
| Collect Endpoint Updates (Linux) | 95 | No message |
Unsupported OS |
|
|
Linux Reboot Command (Linux) |
127 | If the error message appears as follows "...at command not found", the at command needs to be installed on the system |
|
|
| execute patch (Windows) | 216 | Powershell version ( <POWERSHELL_VERSION> ) is not supported - Please upgrade to Powershell 3 |
Powershell version not compatible with JetPatch script Upgrade endpoint Powershell version to 3+ |
|
|
All Scripts (Windows) |
258 | Timeout reached from the Connector side. The task was executed more than the expected time |
Contact JetPatch support for troubleshooting and extend the built-in timeout for needed | |
|
All JetPatch built-in scripts |
340 | The output of the script could not be parsed |
Most of the time it's pointing to the bad behavior of WSUS. Please follow the steps in |
|
| Pre/Post Patching scripts (All) | 340 | The word "Exception" is in the output |
for example - an exception of Powershell script or another kind of script Windows: Verify that the PowerShell policy is enabled properly. |
|
| execute patch (All) | 341 | { "Installations": [ ] } |
The output has empty data Linux: Likely endpoint issue. Please troubleshoot the endpoint. Windows: See article |
|
| Collect Endpoint Updates (Linux) | 341 | The output of the script as expected |
1. Check that basic package manager commands are working on the machine (yum, apt-get, etc) 2. Issue is that the JetPatch server is unable to access the appropriate advisory mailing list (relevant for CentOS).
If a proxy needs to be configured, see this article To test for CentOS, login to the JetPatch server and run the following command: curl -kv https://lists.centos.org/pipermail/centos-announce/ |
|
| Collect Endpoint Updates (AIX) | 341 | The output of the script as expected |
There are no patches yet on the NIM repository that are relevant for this device. Next Steps: Download the Patches to the NIM server and wait for another collection to run / run it manually. Read more on working with the NIM repository here |
|
|
execute patch (All) |
342 | The output of the script was not changed from the previous execution. |
The execution didn't change any status of a patch on an endpoint.
|
|
|
All scripts (All) |
-1 | Error creating virtual process | Sign that the connector was unable to create the process. This could be due to machine resources issues. |
Common Exit Codes for Windows User Scripts
The following table is the most common exit codes for Windows. More information can be found here
| Exit Code | Description | Next Step |
| -1 |
JetPatch fails scripts that do not have any output
|
Change the script that will print a line at the beginning/end. |
| 1 |
Incorrect function / General error
|
Check which command raise this error |
| 2 |
The system cannot find the file specified.
|
Check the script code where it searches for files |
| 3 |
The system cannot find the path specified.
|
Check the script code where it searches for paths |
| 5 |
Access is denied
|
Check Connector user permissions for operations and relevant access for files/folders |
| 258 |
The wait operation timed out from the OS or the Connector
|
Extend the task timeout in JetPatch |
| 340 |
The operation has timed
out (External timeout - in WSUS server) |
Perform Maintenance activities on WSUS server, see article on this subject: |
Common Exit Codes for Linux User Scripts
The following table is the most common exit codes for Linux. More information can be found here
| Exit Code | Description | Next Step |
| -1 |
JetPatch fails scripts that do not have any output
|
Change the script that will print a line at the beginning/end. |
| 1 |
General error
|
Check which command raise this error |
| 2 |
Custom script issue
|
Missing keyword or command, format issue (including hidden characters), or file permission problem |
| 62 |
The wait operation timed out from the Connector
|
Extend the task timeout in JetPatch |
| 127 |
Command not found
|
The script could not find the required command. Check which command raise this error and install/fix the required action |
| 3 |
The system cannot find the path specified.
|
Check the script code where it searches for paths |
| 5 |
Access is denied
|
Check Connector user permissions for operations and relevant access for files/folders |
| 258 |
The wait operation timed out
|
Extend the task timeout in JetPatch |
Note - Linux supports exit codes between 0-255. An exit value greater than 255 returns an exit code modulo 256. For example, exit 3809 gives an exit code of 225 (3809 % 256 = 225).
User Scripts Information
It is recommended to check if Exit Codes were configured for the script:
- In JetPatch, go to System -> Scripts.
- Find the required script (filters can be used) and choose "Edit".
- In the script configuration, go to "Exit Codes" tab and look for configured exit codes.
Comments
0 comments
Please sign in to leave a comment.