Cleaning up failed package installations

While attempting to install a Sun package this week, I encountered the following error:

$ pkgadd -d . MYpackage

## Waiting for up to <300> seconds for package administration commands to become available (another user is administering packages on zone <zoneA>)


1 package was not processed!

After a bit of truss’ing, I noticed that the pkgadd commands were checking for the existence of files with the name<DYNAMICALLY_GENERATED_STRING> in /tmp. Based on a cursory inspection of the package utility source code, it appears these files are used as lock files to prevent multiple package commands from running at the same time. Since this was the only package installation running on the system, I logged into the zone and removed the stale lock file:

$ zlogin zoneA

$ rm /tmp/

Once I removed this file, the package installed like a champ! Nice!

7 thoughts on “Cleaning up failed package installations”

  1. Hey, I just want you to know your blog has been very helpful to me!!! I found my problem and solution from your page several times and it really saved my time!!


  2. Thank you very much…I encountered the same problem and issue is fixed by deleting the lock file from /tmp

Leave a Reply

Your email address will not be published. Required fields are marked *