Patchadd problem

hi guys.... when i do a patchadd... i met this:
patchadd 118207-42
Validating patches...
Loading patches installed on the system...
Cannot open pkginfo file /var/sadm/pkg/ps/pkginfo
how to solve this ?

i had similar problem
1st patches i applied by smpatch
and after that i tried to use patchadd
just for one patch, but it did NOT work
so i did
smpatch add -i 118822-23 -d /export/patche
where
/export/patche is pwd where are the patches
downloaded before
this way i successfully applied patches which require
reboot, immediate reboot or single user mode
it appears like some incompatibility between
smpatch and patchadd

Similar Messages

Patchadd problem: Cannot lock all zones

I cannot add patch 138889-03 because the patchadd returns an error: Cannot lock all zones. I have no log-files found, which explain anything. In the process list I have found a hanging command:
9720 patchadd 138889-03
9726 /usr/bin/pkgadm lock -a -q -o zone.*/patch.* -w -W 300
Unfortunatly the man page knows no subcommand lock for pkgadm.
Can anybody explain what Solaris 10 138889-02 is donig there?
Thanks

I also faced same problem when installing vxvm patch 123220-04. At that time I simply halted the all non-global zones. After that it succeeded the installation.

Patchadd problem - ifp, A5000

I try to configure A5000 under E450 host with Solaris 8. According patch_pro I have to install patches :109189-04 and 109399-03. When I try install direct patch 109189, I obtain below message
# patchadd -u 109189-04
Checking installed patches...
One or more patch packages included in
109189-04 are not installed on this system.
Patchadd is terminating.
How to install it or how to find a reason that patch fails. Where is the install log or how to debug patchadd process?

Since this patch only include 3 files:
/kernel/drv/ifp
/kernel/drv/sparcv9/ifp
/usr/include/sys/scsi/adapters/ifpvar.h
I would think it is looking for the packages SUNWifp and SUNWifpx to be installed.
You may have a log in /var/sadm/patch/109189-04 directory

Problem with upgrading the dsee to 6.3.1

Hello
I have to upgrade the version of directory server from 6.2 to 6.3.1
when i am upgrading the shared components
there is the patch 125446-13
i follow the procedure
unzip the patch
cd into it and launch
patchadd .
but i get the followign error :
bash-3.00# patchadd .
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Cannot open pkginfo file /mnt/global/125446-13/packages/pkginfo
Cannot open pkgmap file /mnt/global/125446-13/packages/pkgmap
there is indded not such files in the patch only a 'pkg' file
bash-3.00# ls packages/
servicetags.i386.5.10.pkg
how can i solve this problem? can i just install the servicetags pkg? and that's it?
thank you for your help
Mario G.

Maybe you don't have to cd IN the patch
I followed the installation instructions for 6 -> to 7 without any problem:
[http://docs.sun.com/app/docs/doc/820-4807/dsee-native-install?l=en&a=view|http://docs.sun.com/app/docs/doc/820-4807/dsee-native-install?l=en&a=view]
[http://docs.sun.com/app/docs/doc/820-4808/upgrade7?l=en&a=view|http://docs.sun.com/app/docs/doc/820-4808/upgrade7?l=en&a=view]
Also check that you have the correct patch
125446-13 is Monitoring Framework 2.1 Solaris_10_x86_amd64: Minor Release patch
according to Sunsolve
regards,
Giannis

Problem with kernel patch 127128-11

I am a bit stomped trying to install this patch successfully.
I log into single user mode.
The patch file is currently located in "/var/sadm/spool"
when I run "patchadd 127128-11" i get the following:
"Patch 127128-11 failed to install due to a failure produced by pkgadd."
============================================================
When I try installing the patch using smpatch with: "smpatch add -i 127128-11"
I get the following error:
"Patch 127128-11 failed to install due to a failure produced by pkgadd."
"PaTch_MsG 23 Patch number 127128-11 cannot be applied until all restricted patches are backed out."
"warning: /usr/bin/disable <no longer a symbolic link>
"warning: /usr/bin/enable <no longer a symbolic link>
"warning: /usr/sbin/reject <no longer a symbolic link>
"warning: /usr/lib/print/psm-lpd.so <no longer a regular file>
"warning: /usr/ucb/lpc <no longer a regular file>
"warning: /usr/ucb/lptest <no longer a regular file>
====================================================
I am still troubleshooting but does anyone have any pointers they would like to share?
Thanks and look forward to your replies

Hi,
I have the same problem and was wondering if anyone had a resolution to it?
Thanks
John

Patchadd interrupted - now failing to install patch correctly

I had started a patch installation when one of my kind users compromised the system by filling all available swapspace.
I tried tto get into the system but failed. After about 10 minutes I did - what I should have avoided to do - a control C on the
unresponsive patchadd command.
The result is that the patch is not committed, but also not removed. The system's response to a patchrm is
beron# patchrm 127144-03
Validating patches...
Loading patches installed on the system...
Done!
Checking patches that you specified for removal.
Done!
Approved patches will be removed in this order:
127144-03
The installation of patch 127144-03 was interrupted.
Patchadd needs to be re-invoked to ensure proper installation of the patch.
Patchrm is terminating.
WARNING: patchrm returned <14>
And if I intend to do a re-install on the patch itself I get
oberon# patchadd 127144-03
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
The following requested patches are already installed on the system
Requested to install patch 127144-03 is already installed on the system.
No patches to check dependency.
Any suggestion on what I could do to tidy the system up, would be very welcome.

lance is already taken wrote:
I have uninstalled and reinstalled some more.
The following do not work:
Apple Bluetooth
Apple Trackpad
Apple Keyboard
Apple Remote (IR Receiver)
I still cannot use the F keys.
Also, OS X does not seem to recognize that I have bootcamp: I cannot select it in the start up disk area. VMWare cannot prepare my Boot Camp partition as a virtual machine. Why am I encountering so many problems?
Edit: Oh and the Built in iSight doesn't work either. Awesome.
You should solve one problem at a time.
If your system does not recognize Windows, don't start playing with VM ware or Parallels. You don't fix something by bypassing it.
If you cannot boot into your Windows partition using bootcamp, that that's the first thing to fix.

PROBLEM PATCHING SOLARIS 10 FOR DST

OK - I messed up installing the DST patch, but now I cannot reinstall.
I used "pkgadd" to install the patch 122032-04. It went fine into the global zone, but "partially failed" going into my other 4 zones.
NOW - using "date" gives the correct time zone and time in all zones (including global), but my TOMCAT/SERVLETS do not get the correct time zone.
So - I read more and installed the mega-patch (fixes a zone bug): 119254-35. This patch was also installed with "pkgadd" (that's what the readme said).
Then I tried to reinstall the failed DST patch - 122032-04, but it won't go past the first dialog. It fails with "ld.so.1: patchadd: fatal: relocation error: file patchadd: symbol zonecfg_set_root: referenced symbol not found.
Note that the above latest error says "patchadd" that's because I've tried pkgadd AND patchadd - neither works but both give the same reference symbol not found error.
NOW WHAT??? I tred uninstalling the patch, but that failed as well - said it could not even find the package. (pkgrm).
Thanks in advance.
-Richard

Thanks. The DST patch actually was complete enough to work after reboot.
It's just the inability to remove the bad patch for now. I suspect there's a problem with the patches in that they want you to be in maintenance mode, but they also want the zones to be booted.
I wish they would either
a) figure this out and make single-user mode patches work when you are IN single user mode (without requiring other steps which ARE NOT SPECIFIED in the readme), or
b) Allow these zone patches to be applied in normal operation mode (multi-user mode).
-R

Patchadd and zones??

I feel dumb asking this question especially since I think its due to my lack of knowledge with zones. I am using Solaris 10 with only a global zone, at least thats what I think? I ran a "zoneadm list" and only listed "global".
I have downloaded uwc [yes I posted something similar on the JMS forum] patch 118540-42 and have tried to add it with patchadd. I get an error saying " Package SUNWuwc from directory SUNWuwc in patch 118540-42 is not installed on the system" and the patch does not install [I can not see it with showrev -p nor in /var/sadm/patch]. I also tried the "-G" option but no difference.
Then I tried using Solaris Management Console 2.1 using its patch tool. Action -> add patch and I get an error saying "Some or all of the software packages that patch 118540-42 patches are not installed on the target host.".
So I decided to look for SUNWuwc with pgkinfo and there is no listing, in fact none of the Java comm suite is found [nor most of the stuff in /opt and /usr/local ]. Yet I know JES is all in /opt and is working fine. I have never created a zone on this system and thought I had installed everything to just a global zone. I have had this system running for over a year and some updates have happened [just not sure what changed].
So I am wondering is there another way to add patches with Sol 10? another flag or utility? Is there a way to know what zone one is working in? or has installed stuff to. Is there a way at this point to stop using zones altogether?
Maybe I am missing a Sol 10 patch?
I had also run into a file /var/sadm/install/gz-only-packages and sure enough all my installed packages were listed here [all the JES stuff and web server etc]. I thought this meant "global zone only" and I only have a global zone??? so why can I not patch??
Apologies for the confusion [and lack of more details], although I have worked with Solaris for years this new 10 version and zones is a bit confusing for me. Plus the problem might not be zones related at all :^)
Thanks in Advance
-James

try zoneadm list -vc
this shows all zones on the system, whether they are configured, running or not running.
Next, try to get the 10-recommended patches from sunsolve.sun.com and add those, but do it in single-user mode.
/tony

StarOffice 8 U6 (Solaris 10 x86) problem upgrading to U7

hello all,
i have problem installing the new StarOffice 8 U7 patch (120186-11) on Solaris 10 x86 3/05. my current installation of StarOffice 8 is patched up to U6 (120186-10) and has the "ARCH patch to enable install of >= Update 6" patch 126411-01 installed.
the errors that i get from patchadd are:
Architecture for package SUNWstaroffice-core01 from directory SUNWstaroffice-core01.i in patch 120186-11 differs from the package installed on the system.
<snipped other output>
0 Patch 120186-11 is declared as incompatible by 122365-01, which has already been installed on the system.
any help will be appreciated.
greetings,
Stoyan

hello all,
finally found the solution for this problem. thanks to Willi Burmeister who posted a simiral question and a summary to the sunmanagers mailing list:
this was triggered by bug 6404527. It's a missing blank in the pkginfo file of nearly all
staroffice packages.
here is a quick workaround:
# cd /var/sadm/pkg
# grep -l ": R" */pkginfo | xargs perl -pi'.bak' -e 's/: R/: R/'i am happily running U9 now :P
cheers,
Stoyan

Problem: installing Recommend Patch Cluster: patch 140900-10 fails

I don't know if this is correct location for this thread (admin/moderator move as required).
We have a number of Solaris x86 hosts (ie 4) and I'm trying to get the patched and up to date.
I obtained the latest Recommended Patch Cluster (dated 28Sep2010).
I installed it on host A yesterday, 2 hours 9 mins, no problems.
I tried to install it on host B today, and that was just a critical failure.
Host B failed to install 140900-01, because the non global zones rejected the patch because dependancy 138218-01 wasn't installed in the non global zones.
Looking closer, it appears that 138218-01 is for global zone installation only; so it makes sense that the non global zones rejected it.
However, both hosts were in single user mode when installing the cluster and both hosts have non global zones.
140900-01 installed on host A with log:
| 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.
|
| Dryrun complete.
| No changes were made to the system.
|
| 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.
|
|
| Installation of <SUNWcsu> was successful.
140900-1 failed on host B with this log:
| Validating patches...
|
| Loading patches installed on the system...
|
| Done!
|
| Loading patches requested to install.
|
| Done!
|
| Checking patches that you specified for installation.
|
| Done!
|
|
| Approved patches will be installed in this order:
|
| 140900-01
|
|
| Preparing checklist for non-global zone check...
|
| Checking non-global zones...
|
| Checking non-global zones...
|
| Restoring state for non-global zone X...
| Restoring state for non-global zone Y...
| Restoring state for non-global zone Z...
|
| This patch passes the non-global zone check.
|
| None.
|
|
| Summary for zones:
|
| Zone X
|
| Rejected patches:
| 140900-01
| Patches that passed the dependency check:
| None.
|
|
| Zone Y
|
| Rejected patches:
| 140900-01
| Patches that passed the dependency check:
| None.
|
|
| Zone Z
|
| Rejected patches:
| 140900-01
| Patches that passed the dependency check:
| None.
|
| Fatal failure occurred - impossible to install any patches.
| X: For patch 140900-01, required patch 138218-01 does not exist.
| Y: For patch 140900-01, required patch 138218-01 does not exist.
| Z: For patch 140900-01, required patch 138218-01 does not exist.
| Fatal failure occurred - impossible to install any patches.
| ----
| patchadd exit code : 1
| application of 140900-01 failed : unhandled subprocess exit status '1' (exit 1 b
| ranch)
| finish time : 2010.10.02 09:47:18
| FINISHED : application of 140900-01
It looks as if the patch strategy is completely different for the two hosts; both are solaris x86 (A is a V40z; B is a V20z).
Trying to use "-G" with patchadd crabs the patch is for global zones only and stops (ie it's almost as if it thinks installation is being attempted in a non global zone).
Without "-G" same behavior as patch cluster install attempt (no surprise there).
I have inherited this machines; I am told each of these machines were upgraded to Solaris 10u6 in June 2009.
Other than the 4-5 months it took oracle to get our update entitlement to us, we've had no problems.
I'm at a loss here, I don't see anyone else having this type of issue.
Can someone point the way...?
What am I missing...?

Well, I guess what you see isn't what you get.
Guess I'm used to the fact USENET just left things formatted the way they were :-O

Patchadd ignores patch_list in Solaris 10 8/07?

Hello,
I have noticed that after upgrading to 8/07 I cannot patch multiple patches using a form of command:
patchadd -M /mnt patch_order
The output I get is:
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
No patches to check dependency.
However, patchadd -M /mnt works perfectly. That is, if patch_order is provided command fails but if its ommited it works fine. I have read somewhere that now patchadd is smart enough to sort everything out and figure out the right order in patch cluster.
I specifically checked in 11/06 and that form of patchadd command providing patch_list works perfectly.
Moreover, if jumpstarting 8/07 and using "patch" directive in the profile it does not work anymore displaying same messages as above. I am sure it's because of the same problem of the "new" patchadd behaviour in 8/07. I wouldn't be worried that much since manually there is always a workaround but it's disappointing that this very useful feature of specifying a patch cluster in jumpstart profile doesn't work anymore. One would need to get around with finish_script.
I am wondering did anyone notice the same thing and perhaps found and explanation/solution?
/M.

I assume that the FX update is grayed out because your login does not have permissions to write to the install directory.
Release of patch updates for FX/TB "when Sun deems it necessary" is EXACTLY what I am afraid of and want to avoid. Mozilla releases rather frequent updates with important security fixes. I want those updates immediately, not when Sun deems it necessary. Based on the performance of patches for Adobe Acrobat Reader and Adobe Flash, Sun is woefully slow on patch update releases for bundled third party software.
Mozilla releases s/w updates in Sun package format. Will there be some conflict with the Sun Update Manager/smpatch processes if I install the Mozilla packages over the bundled Mozilla software?
Another way to ask this question: Will Sun release patch updates for EVERY FX/TB release (e.g. 2.0.0.8, 2.0.0.9, etc.) or just releases that they deem important? Secondly, how long after Mozilla releases an update can we expect to receive a Solaris patch with that update?

Problem in Reducing the root file system space

Hi All ,
The root file system is reached 86%. We have cleared 1 GB data in /var file system. But the root file system still showing 86%. Please note that the /var file is not seprate file system.
I have furnished the df -h output for your reference. Please provide solution as soon as possible.
/dev/dsk/c1t0d0s0 2.9G 2.4G 404M 86% /
/devices 0K 0K 0K 0% /devices
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 30G 1.0M 30G 1% /etc/svc/volatile
objfs 0K 0K 0K 0% /system/object
/dev/dsk/c1t0d0s3 6.7G 3.7G 3.0G 56% /usr
/platform/SUNW,Sun-Fire-T200/lib/libc_psr/libc_psr_hwcap1.so.1
2.9G 2.4G 404M 86% /platform/sun4v/lib/libc_psr.so.1
/platform/SUNW,Sun-Fire-T200/lib/sparcv9/libc_psr/libc_psr_hwcap1.so.1
2.9G 2.4G 404M 86% /platform/sun4v/lib/sparcv9/libc_psr.so.1
fd 0K 0K 0K 0% /dev/fd
swap 33G 3.5G 30G 11% /tmp
swap 30G 48K 30G 1% /var/run
/dev/dsk/c1t0d0s4 45G 30G 15G 67% /www
/dev/dsk/c1t0d0s5 2.9G 1.1G 1.7G 39% /export/home
Regards,
R. Rajesh Kannan.

I don't know if the root partition filling up was sudden, and thus due to the killing of an in-use file, or some other problem. However, I have noticed that VAST amounts of space is used up just through the normal patching process.
After I installed Sol 10 11/06, my 12GB root partition was 48% full. Now, about 2 months later, after applying available patches, it is 53% full. That is about 600 MB being taken up by the superseded versions of the installed patches. This is ridiculous. I have patched using Sun Update Manager, which by default does not use the patchadd -d option that would not back up old patch versions, so the superseded patches are building up in /var, wasting massive amounts of space.
Are Solaris users just supposed to put up with this, or is there some other way we should manage patches? It is time consuming and dangerous to manually clean up the old patch versions by using patchrm to delete all versions of a patch and then using patchadd to re-install only the latest revision.
Thank you.

Patch problem in SUNWappserver under Solaris 10

When attempting to install the patch 119166-15 for AppServer 8.1, I get the following info and error:
<--- Begin Session text --->
# patchadd -G 119166-15.jar
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
The following requested patches have packages not installed on the system
Package SUNWaslb from directory SUNWaslb in patch 119166-15 is not installed on the system.
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
119166-15
Verifying signed patch <119166-15>...
Verifying digital signature for signer <es-signature>
ERROR: Signature verification failed while verifying certificate <subject=Sun Microsystems Inc Root CA, issuer=GTE CyberTrust Root>:<unable to get local issuer certificate>.
ERROR: Unable to verify signature for signer <es-signature>
Signature invalid on signed patch <119166-15>.
Patchadd is terminating.
<---End Session test --->
Also having problems running "asadmin" ; I cannot determine which port the Admin Server is running on or needs to be running on. Fairly new to SUN OS, so any "dummy" pointers would probably help...
Regatds...
Texas Mike....

You might want to ask about patching issue on Solaris update forums since as far as I can tell issue is not related to the fact that patch is for Application Server - it seems to be generic problem with patch signature verification. Solaris update and patching forum URL:
http://forum.sun.com/jive/forum.jspa?forumID=316
As for the asadmin question: first you need to start your server using 'asadmin start-domain' command and you do not need to know the port number to do that. After that you can try accessing https://localhost:4849 (4849 is the default value for admin application URL port number).

Patchadd failure - non-global zones

Hi there
Having issues running patchadd. Can't find libcrypto.so.0.9.7. The file exists and have attempted using crle and LD_LIBRARY_PATH to point patchadd in the right direction. This occurs when zones in a halted state. If I start zones then patchadd works OK, however not an option when trying to install patch bundle.
Note, we do have openssh & openssl installed which use libcrypto.so.0.9.8
Preparing checklist for non-global zone check...
Checking non-global zones...
ld.so.1: pdo: fatal: libcrypto.so.0.9.7: open failed: No such file or directory
Non-global zone check failed. No change made to the System.
Patchadd exiting. Any suggestions?
Cheers
Garry

After much trial and error located the problem.
It would seem that when patching non-global zones, Solaris 10 sets up a "live upgrade environment" in which various directories are mounted over temporary "lu" mount points. Sorry, no longer have a screen dump. When patchadd was failing the zone was left in a state of "mounted" - (rectified by running zoneadm -z zonename unmount). While in this mounted state, I could zlogin and run an ldd on patchadd (ldd `which patchadd`). This resulted in libcrypto.so.0.9.7 pointing to "file not found".
The cause of this was due to Openssh & Openssl being installed over the standard distribution. Copied libcrypto.so.0.9.7 from /usr/sfw/lib to /usr/lib and problem went away

Problem applying patches on Sol10

I must be doing something guffy but can't figure out what...
I am trying to apply patch on Sol 10x86 box. patchadd is failing siliently with no indication on what might be the problem. I tried on two different machines with identical results. Any ideas on what might be the problem or how to debug it.
Thanks,
/Oleg
# patchadd -g 118344-07
Patches Validation...
Loading patches installed on the system...
Done.
Loading patches requested to install.
Done.
Checking patches requested to install.
Done.
Approved patches will be installed in this order:
118344-07
Checking installed patches...
Patchadd is terminating.

I am assuming you want to only apply this patch in a specific Zone? If that is the case you would want to use -G instead of -g as the option.
"Add patch(es) to packages in the current zone only. When used in the global zone, the patch is added to packages in the global zone only and is not propagated to pack-ages in any existing or yet-to-be-created non-global zone. When used in a non-global zone, the patch is added to packages in the non-global zone only."
DP

Patchadd problem

Similar Messages

Maybe you are looking for