Troubleshooting Jobs

In the Jobs panel, you might see that a job failed on a host. There are various reasons for a failed job, and different ways in which you can handle the issue.

To which troubleshooting procedure is most relevant, open the Job Log (see To Monitor a Current Job).

Procedures in this section include the following:

• Handling Resolve Failures

• Handling Failures Due to Cost

• Handling Missing Components

• Handling Installation Issues

Handling Resolve Failures

If a job failure occurs during the resolve stage, troubleshoot the solution offered by the Dependency Resolver with these checks.

• Open the Host Progress window of a failed host and check for manual intervention points. Handle the manual procedures and rerun the job.

• Open the Job Log of a failed host. Carefully check components and actions in the job. For example, you might have created a profile that demanded conflicting actions on some components. Recreate the job without the problematic components.

• Change or create a policy that causes the agent to look for a different DR for the job. The confirmation policy should Not Allow the components listed under the failure reason to receive the failed actions.

  You might find it helpful to review the Resolve Log of the failed host. Open the Preferences window of the selected host to find the directory and file name of this log (see Host Preferences – Logs).

Handling Failures Due to Cost

Sometimes a failed DR cannot be fixed. The message cost in change too high indicates that the DR found so many components that would have had to be changed, that it will not go on.

• If you requested many components, break up your request into smaller jobs.

• If you requested only a few components, try making a job of each component separately. You will probably find one that demands too many dependency fixes. Perhaps you can select an alternative component.

Handling Missing Components

Sometimes a component cannot be installed or uninstalled. One of the following errors might appear to explain the DR failure:

• component is not installable by current KB

• component is not removable by current KB

Only Local components may be not installable or not removable. To handle these issues, open the Local category in the Components list of the main window. Expand the subcategories until you find the problematic components.

• The Components list might include listings for which you do not have the software component: an NCO without an attached software, a 3rd-Party application for which you do not have a license, a tool without an uploaded script, and so on.

  If this is the problem, the package will be marked with an empty software icon.

  If you see one of these icons, upload the required software component.

  See Fixing Local Dependencies.

• The local component might be in the knowledge base, but missing dependencies according to the deployment rules.

  If this is the problem, the package will be marked with an exclamation point in a red circle.

  Right-click the component and choose Component Details.

  The Component Information window opens, displaying the missing requirements in the Dependencies tab.

Handling Installation Issues

If the job failed during installation, use these checks to find a solution.

• Check the permissions needed by the component for install. The permissions might conflict with the permissions of the logged-in user. The Job Log of the failed host will show permissions as the reason for failure.

• Try to install the component manually with Linux terminal commands. Afterwards, run a Check System (see Running Predefined Profiles) to handle dependency issues.

  If the installation fails for an NCO (non-certified component), the Job Log might provide one of the following reasons.

  • Conflict with. Listed NCO has possible conflicts with a component from the To Do list.

  • Downgrade. Listed NCO appears to be a newer version of a component from the To Do list.

  • Possible Unavailability. Installing one of the components from the To Do list might cause the listed NCO to become inoperable.

• Run the Local Software Review predefined profile and replace NCOs with COs, or uninstall the NCOs.

• Make sure that the NCO has been detected and added to the components list. If the local software package is not under Local RPMs or Local PKGs, search for it under a CO listing in Software (see To Find Components). If the NCO is not in the components list, add it (see Adding Undetected Linux Software).