Linux OS Update Deployment Failures

This section provides solutions for the following categories of failures that can occur during Linux OS update deployment:

• Failures that Occur Before the Job is Submitted

• Load Update Job Failures

• Unload Update Job Failures

• Stop Job Failures for Load and Unload Update

• Unload Server and Unload Group Failures

Failures that Occur Before the Job is Submitted

The following common failures can occur before the job is submitted:

Target server is not initialized

Solution:

Check whether the add server feature osmonitor command was issued and whether it succeeded.

Another running job on the target server

Solution:

Only one job is allowed at a time on a server. Try again after the job completes.

Update is incompatible with operating system on target server

Solution:

Check whether the OS type of the target server matches one of the update OS types. Type show update update-name at the N1–ok> prompt to view the OS type for the update.

Target server is not in a good state or is powered off

Solution:

Check whether the target server is up and running. Type show server server-name at the N1–ok> prompt to view the server status. Type reset server server-name force to force a reboot.

Load Update Job Failures

The following are possible causes for Load Update job failures:

error: Failed dependencies:

A prerequisite package should be installed

Description:

Sometimes, Load Update jobs fail because either the same package already exists or because a later version of the package exists. Ensure that the package does not already exist on the target server if the job fails.

Solution:

Use an RPM tool to address and resolve Linux OS RPM dependencies.

Preinstall or postinstall scripts failure: Non-zero status

ERROR: ... script did not complete successfully

Solution:

Check the preinstallation or postinstallation scripts for possible errors to resolve this error.

Insufficient diskspace

Solution:

Load Update jobs might fail due to insufficient disk space. Check the available disk space by typing df -k. Also check the package size. If the package size is too large, create more available disk space on the target server.

Unload Update Job Failures

In the following unload command, update could be either the update name that appears in the list when you type show update all, or the actual package name on the target server.

N1-ok> unload server server update update

Stop Job Failures for Load and Unload Update

The following are stop job failures for loading or unloading update operations:

If you stop a Load Update or Unload Update job and the job does not stop, manually ensure that the following process is killed on the management server:

# ps -ef |grep swi_pkg_pusher
# ps -ef |grep rpm

Then, check any processes that are running on the manageable server:

# ps -ef |grep rpm, ...

Unload Server and Unload Group Failures

The following are possible causes for failures related to the commands unload server server-name update update-name and unload group group-name update update-name.

Job step failure without error details

Solution:

This message might indicate that the job was not successfully started internally. Contact a Sun Service Representative for more information.

Job step failure with vague error details: Connection to 10.0.0.xx

Solution:

This message might indicate that the uninstall failed because some RPMs were not fully installed. In this case, manually install the package in question on the target server. For example:

To manually install an RPM, type the following command:

# rpm -Uvh rpm-name

Then, run the unload command again.

Job hangs

Solution:

If the job appears to hang, type n1sh stop job job-ID to stop the job.

Next, find the PID of the RPM and use the pkill command to kill the RPM process. For example:

# ps -ef |grep rpm-name root 1235 913 0 Jun 07 ? 0:0 rpm-name # pkill 1235

Then run the unload command again.