Linux:
- Patch installation requires a dependency from a disable 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 Repository server (if it's a local repository) and that the repo conf file on client-server, has repo 'Two' and it's enabled)
- Couldn't connect to server - so all patching cycle will fail
- SELinux blocking installation: download connector logs and look for the following message:
- For example, if you see ‘ERROR: ld.so: object ‘.../lib_${PLATFORM}/libintcore.so' from LD_PRELOAD cannot be preloaded: ignored.’, then a SELinux configuration is causing the problem (known issue - fix in 4.2)
- Workaround: modify SELinux to either permissive or disabled
Windows:
- Communication issue between endpoint and WSUS
In General
In addition to the output provided in the activities log, you can get simplified output via Logs & Alerts.
- Go to Platform configuration
- Click on Logs & Alerts and filter Type on Error
- Filter Description on "Patch installation failed on 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.