This site requires JavaScript to be enabled
Welcome Guest|
Recent searches
IE BUMPER
KB0018151

How to check automated patching in Satellite

Number of views : 2
Article Number : KB0018151
Published on : 2020-03-30
Last modified : 2020-03-30 22:07:05
Knowledge Base : ESM External

How to check automated patching in Satellite

 

While automated patching normally runs without any problems, daily checking should be done to ensure issues are detected and resolved. There are several ways to accomplish this task, but the fastest is as follows.

  1. Log into the Satellite (https://itsy-satellite.austin.utexas.edu) and go to Monitor/Dashboard.
  2. Locate the Task Status group and select the No. of Tasks associated with stopped/error. (It can be bookmarked for future reference.)
  3. Review the Actions list (should default to order started most recently) look for systems belonging to your department.
    • This shows all task related to the Satellite not just one department.
    • For automated patching, look for “Remote Actions”

  1. Opening one of the action items allows you to look at what occurred on the system when it tried to run the patch script. There are multiple possibilities of what could have gone wrong. Some common errors are:
    • Yum has a lock. – Solution: check the system to see if it still has a lock, and investigate why yum may have been running at that time.
    • Cannot retrieve repository metadata. – Solution: Bad repo. See why what is wrong with the repo and correct it.
    • SSH::AuthenticationFailed – Solution: Some issue with contacting the system. Is the firewall blocking it? SSH key working?
    • Initializing command: SocketError – Solution: Some issue with contacting the system. Is it up?
    • Common on RHEL 6 “Unexpected disconnect” just as it reboots. This can be ignored.

Each issue needs to be looked at and evaluated. Is it an issue that will correct itself? Is there manual intervention required? One thing to watch is if patching is stopped after evaluation and the patch count is set to 1 or more it needs to be reset to 0 in the parameters on the host.

Thank You! Your feedback has been submitted.

Feedback