Patchadd failed

Posted on 2003-03-19
Medium Priority
Last Modified: 2013-12-27


I`v tried to install patch on Solaris8 with:
patchadd /path/to/patches/112396-02

action failed with error:
Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...

Patch 112396-02 failed to install due to a failure produced by pkgadd.

See /var/sadm/patch/112396-02/log for details

Patchadd is terminating

Looking at log, I find out, that there is problem with accessing some file:
This appears to be an attempt to install the same architecture and
version of a package which is already installed.  This installation
will attempt to overwrite this package.

/path/to/patches/112396-02/SUNWcsr/install/checkinstall: /path/to/patches/112396-02/SUNWcsr/install/checkinstall: cannot open
pkgadd: ERROR: checkinstall script did not complete successfully
Dryrun complete.
No changes were made to the system.

All files exists, so I don`t really understand, where is the problem?

Thanks in advance.

Btw, If i need to instal several patches, where one depends from other. Is there any efficient way, how to make them installing in proper order?
Question by:shifted
  • 5
  • 2
  • 2
  • +2

Expert Comment

ID: 8165652
1. You must root
2. Check you disk space df -k /
3. Check if the patch is insatlled.

Author Comment

ID: 8167400
*) Disk space is more than enough.

*) with "patchadd -p | grep 112396" no results were returned. So this package is not installed.

Author Comment

ID: 8167412
Interesting, that checkinstall calls himself. Maybe this is the problem?

/path/to/patches/112396-02/SUNWcsr/install/checkinstall: /path/to/patches/112396-02/SUNWcsr/install/checkinstall: cannot open
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.


Author Comment

ID: 8167686
So the actual problem is, that installing everything I got error about "cannot open" on file ".../checkinstall"
Why it so? The file actually exists!

Any ideas?
LVL 18

Expert Comment

ID: 8167705
Don't know whether it helps, but the readme says

Problem Description:

This revision was created to enable installation of the
        108528-14 patch that depends on this patch for installation.
        No additional bug fixes were integrated into this patch.

This is the kernal patch, - are you running a much later kernel patch?
LVL 18

Expert Comment

ID: 8168017
just re-installed it (with patchadd -u) and got no problems at all on system:
SunOS 5.8 Generic_108528-18 sun4u sparc SUNW,Ultra-5_10

Author Comment

ID: 8169035
Unfortunately patchadd -u didn`t helped.

I starting to think, that there is some different problem than only patchadd. Why it is pkgadd, who produces a problem? Maybe som system environment have some misconfigurations?

Accepted Solution

jwelter earned 750 total points
ID: 8169084
Does showrev -p | grep 112396 indicate any rev of the patch?

I always cd to the parent directory of the patch, and do patchadd -d patch_number, FYI.

Is the patch unbundled/untarred/uncompressed?

Maybe download it again -did you get a signed or regualr patch?



Expert Comment

ID: 8170346
correction: cd to patch parent & patchadd patch_number

Author Comment

ID: 8172083
I didn`t find theoretical base of solution, but everythig goes well, when I copied patches from deep internal catalogue of my home directory (/export/home/myaccount/long/path/patches) to /var/spool/patches an as I copyying as a root - ownership of that patch although changed to root (it was downloaded as ordinary user account).

Thanks anyway.

Expert Comment

ID: 8182934
I've run into this a few times now this week.  Let me report on some of the things I've tried.  I've probably
installed patches on 30 or so boxes in the last two weeks.  I've had patches fail with this error on 3 so far.

On the first two that failed I was successful at installing the patch by simply moving it to a different partition.  (from /export to /) Some partitions seemed to work, and others didn't.  I don't know why (yet).

I have boxes which should be identical, and it will work on one, and not the other.  Same patch sets, same packages, the file systems were even constructed the same way.

I noticed this first with patches for Solaris 8, on Veritas Volume Managed slices off of the local disk.  It was broken on a vxfs filesystem but worked on a ufs filesystem.  The Veritas patches seem to be up to date.

Just a couple hours ago I ran into the same problem on a Solaris 7 box with DiskSuite.  I tried installing off of a non-DiskSuite managed partition, to no avail.

You can edit /usr/sbin/patchadd, look for the line which says "pkgadd_DEBUG="no"" and change it to a yes.

It doesn't really tell you anything more.

I agree that the force and the no backup options don't help with patchadd.

truss -f patchadd <patchnumber>  does reveal a little more
interesting data.  Grepping for checkinstall I get this:
# grep checkinstall truss.out
22794:  access("7_Recommended/106541-23/FJSVhea/install/checkinstall", 0) = 0
22800:  open64("7_Recommended/106541-23/FJSVhea/install/checkinstall", O_RDONLY) Err#13 EACCES

So - interestingly the parent process can access the file, but the child process fails.

I ran some scripts to create and destroy and open files in the same directory, set them in an infinite loop - and never had an error.

The problem is consistent on the boxes where it is broken.
The problem never appears on the boxes where it isn't.

Googling I came across your post hoping to find an answer.  I'm glad I'm not the only one battling this issue though.


Expert Comment

ID: 8183005
The next link down in my google search showed me the answer.  From 1998 on the SunManagers list...

"The path to the patch has to be accessible to the user 'Nobody'".  

A quick check and one of the upper trees had no x bit for the world.  I changed it, and voila!  It works.

Here was the next link down:

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In tuning file systems on the Solaris Operating System, changing some parameters of a file system usually destroys the data on it. For instance, changing the cache segment block size in the volume of a T3 requires that you delete the existing volu…
My previous tech tip, Installing the Solaris OS From the Flash Archive On a Tape (http://www.experts-exchange.com/articles/OS/Unix/Solaris/Installing-the-Solaris-OS-From-the-Flash-Archive-on-a-Tape.html), discussed installing the Solaris Operating S…
Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
Learn how to find files with the shell using the find and locate commands. Use locate to find a needle in a haystack.: With locate, check if the file still exists.: Use find to get the actual location of the file.:
Suggested Courses
Course of the Month12 days, 17 hours left to enroll

578 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question