Linux:
- Patch installation requires a dependency from a disabled repository: (for example, patch A is stored in repo 'One' but it also needs patch B to complete the installation, but it's in repo 'Two', if the repo is not enabled I won't be able to install. Thus, in order to install it you will have to check that repo is enabled on the Repository server (if it's a local repository) and that the repo conf file on the client-server, has repo 'Two' and is enabled)
- Couldn't connect to the server - so all patching cycles will fail
Windows:
- Communication issue between endpoint and WSUS. Verify the patching checklist. If there is still an issue, look at an in-depth patching log.
- Verify Time, Date, and Timezone on Windows Server and JetPatch Server.
In General
In addition to the output provided in the activities log, you can get simplified output via Logs and alerts.
- Go to Platform configuration
- Click on Logs & Alerts and filter Type on Error
- Filter Description on "Patch installation failed on a computer"
- Click on Details
to view the message
Note
Pre-patching is expected to run again whenever patching fails.
Example Scenario:
- Pre-patching succeeds, so it moves to patching
- patching fails
- Post-patching skips (by default)
- Pre-patching will start again.
Comments
0 comments
Please sign in to leave a comment.