Help with SUN Update client
Hi
I have setup a SUN Update Connection Proxy and SUN Update Manager in the same server (bdmdev) at Solaris 10 6/06 and have patched successfully. This is still working.
I am really struggling (probably lack of understanding) to sort out a 2nd client (bdmprod) to use the SUN Update Connection proxy as it doesnt have a direct connection to the web. The issue is probably complicated by the fact I used the disks from the SUN Update Connection Proxy to build the 2nd client, so I had to reconfigure the patch update side of things.
Anyway:
I know my 2nd client (bdmprod) has to point to the Update proxy (bdmdev), to check for its uopdates from there (if they have been downloaded) and then the web via the Update Proxy (bdmdev). Well I hope all the is correct.
So for my setup I have:
bdmprod# patchsvr setup -l
Patch source URL: http://bdmdev:3816/solaris/
Cache Location: /var/sadm/spool/patchsvr
Web proxy host name:
Web proxy port number: 8080
Web proxy user:
bdmprod#
bdmprod# smpatch get
patchpro.backout.directory"" ""
patchpro.download.directory/var/sadm/spool /var/sadm/spool
patchpro.install.types -rebootafter:reconfigafter:standard
patchpro.patch.sourcehttp://bdmdev:3186/solaris/https://getupdates1.sun.com/solaris/
patchpro.patchsetcurrent current
patchpro.proxy.host "" ""
patchpro.proxy.passwd********
patchpro.proxy.port 80808080
patchpro.proxy.user "" ""
bdmprod#
I suppose the only other source of information is that entered for Registration via the GUI or sconadm. I am not sure how I retrieve the current settings, perhaps you cannot. Anyway when I have gone to Register though the GUI ( File, 'Manage Subscription') after adding a sunsolve username and password and a Contract number I get:
-
In order to register this system with Sun, your computer must be
connected to the internet. etc
-
Do I really need access to the Internet? Can it not go through the Update Proxy for Registration? Does anything need to be done on the Update manager to allow connection? I expect the issue is my lack of understanding and therefore setup.
Any help appreciated.
Thanks
Trevor
# 1
A proxy client doesnt need to be registered.
Only the proxy itself needs to be registered.
You shouldnt need to put any patchsvr settings on the proxy client either.
patchsvr is only used on the proxy.
You smpatch get settings look fine.
What do you get when you run smpatch analyze on the proxy client.
# 2
Hi Robert
Thanks for the quick reply.
> A proxy client doesnt need to be registered.
> Only the proxy itself needs to be registered.
I hadnt appreciated that, that helps my understanding.
> You shouldnt need to put any patchsvr settings on the proxy client either.
> patchsvr is only used on the proxy.
Ok, that is useful.
> You smpatch get settings look fine.
> What do you get when you run smpatch analyze on the proxy client.
bdmprod# smpatch analyze
Failure: Cannot connect to retrieve detectors: Connection refused
bdmprod#
and only 4 (2 each way) packets are sent between the 2 hosts using snoop.
Do you think because I have the Update proxy installed its complicating the issue?
bdmprod# pkginfo -i | grep -i patch
system SUNWgpch The GNU Patch utility
system SUNWinstall-patch-utils-root Install and Patch Utilities (root)
system SUNWpmgr Solaris Patch Management Applications
system SUNWppro-plugin-sunos-base PatchPro SunOS Base plugin
system SUNWppror PatchPro core functionality (Root)
system SUNWpprou PatchPro core functionality (Usr)
system SUNWpsvrr Patch Server Deployment (Root)
system SUNWpsvru Patch Server Deployment (Usr)
system SUNWswmt Install and Patch Utilities
bdmprod#
Perhaps I need to get rid of:
system SUNWpsvrr Patch Server Deployment (Root)
system SUNWpsvru Patch Server Deployment (Usr)
and perhaps even:
system SUNWppror PatchPro core functionality (Root)
system SUNWpprou PatchPro core functionality (Usr)
and add these 2 back.
Cheers
Trevor
# 3
Hello Trevor,
The first thing that I would like you to do is download and apply the most recent "Sun Update Connection System Client 1.0.8" patch:
121118-08 - Sparc
121119-08 - x86
Currently you have the patchsvr pointing to itself as the "Patch source URL":
bdmprod# patchsvr setup -l
Patch source URL: http://bdmdev:3816/solaris/
Cache Location: /var/sadm/spool/patchsvr
Web proxy host name:
Web proxy port number: 8080
Web proxy user:
bdmprod#
Which is why you are getting the errors when attemptng register.
I also see that you have a http proxy port defined, however you do not have a "proxy host name". Do you use an internal http proxy?
Please can you run the following command:
patchsvr setup -p https://getupdates1.sun.com
Only run the command below if you use a internal http proxy!
patchsvr setup -x <name_of_webproxy>:<port_number>
patchsvr setup -l
Then attempt to register this system again.
Please contact us if you experience any problems.
Regards,
# 4
Have up started the patchsvr.Runpatchsvr enablepatchsvr startif you do a /usr/ucb/ps -auxww | grep patch it should show the patchsvr process.
# 5
> Hello Trevor,
> The first thing that I would like you to do is download and apply the most recent "Sun Update Connection System Client 1.0.8" patch:
> 121118-08 - Sparc
OK will do, we are at -06 of this patch.
> Currently you have the patchsvr pointing to itself as the "Patch source URL":
> bdmprod# patchsvr setup -l
> Patch source URL: http://bdmdev:3816/solaris/
> Cache Location: /var/sadm/spool/patchsvr
> Web proxy host name:
> Web proxy port number: 8080
> Web proxy user:
> bdmprod#
> Which is why you are getting the errors when attemptng register.
My initial description of the issue was correct, but because of my lack of understanding I was focusing on the wrong area. Robert pointed out I dont need patchsvr on my client, just the Update Connection Proxy. My setup is:
bdmdev - Update Connection Proxy and a Client
bdmprod - A client.
> I also see that you have a http proxy port defined, however you do not have a "proxy host name". Do you use an internal http proxy?
I was thinking that this made it go through the Update Connection Proxy, in fact I dont need patchsvr at all on this system as it is just a client (I am learning).
> Please can you run the following command:
> patchsvr setup -p https://getupdates1.sun.com
I will do this on my Update Connection Proxy.
> Only run the command below if you use a internal http proxy!
> patchsvr setup -x <name_of_webproxy>:<port_number>
patchsvr setup -l
Will do.
> Then attempt to register this system again.
OK.
This and Roberts emails have probably got me on the right track. I was thinking I had my connection proxy setup correctly, I may do, but I certainly dont have the client on the same system pointing at it, I am by passing it: As Robert asked me to check I dont even have the patchsvr process running which is totally fundemental. So no chance of getting a client going till I have resolved this.
So on my Update Conection Proxy 'bdmdev'
bdmdev# smpatch get
patchpro.backout.directory"" ""
patchpro.download.directory/var/sadm/spool /var/sadm/spool
patchpro.install.types -rebootafter:reconfigafter:standard
patchpro.patch.source-https://getupdates1.sun.com/solaris/
patchpro.patchsetcurrent current
patchpro.proxy.host X.X.X.X ""
patchpro.proxy.passwd********
patchpro.proxy.port 80808080
patchpro.proxy.user "" ""
bdmdev#
(I replaced the IP I put in with X.X.X.X, and below)
So I see I am bypassing the Connection Proxy on this server, and going straight to SUN. But I now I know this I am struggling to get my proxy working.
bdmdev# patchsvr setup -l
Patch source URL: https://getupdates.sun.com/solaris/
Cache Location: /var/sadm/spool/patchsvr
Web proxy host name: X.X.X.X
Web proxy port number: 8080
Web proxy user:
bdmdev# ps -eaf | grep patch
root 50298840 09:59:25 pts/10:00 grep patch
bdmdev#
bdmdev# patchsvr setup -p https://getupdates1.sun.com
bdmdev# patchsvr setup -x X.X.X.X:8080
bdmdev#
bdmdev# patchsvr enable
bdmdev# ps -eaf | grep patch
root 61338840 10:03:07 pts/10:00 grep patch
bdmdev# patchsvr disable
bdmdev# patchsvr enable
bdmdev# ps -eaf | grep patch
root 61688840 10:03:58 pts/10:00 grep patch
bdmdev#
So no patch server process running. No point in pointing my client on this server or the other server (bdmprod) to the Connection Proxy until I have fixed this. I'll work at this, but any help appreciated.
I am out of the Office tomorrow (in Australia), but will work on his today.
Thanks for all the help so far, Ricahrd too.
Thanks
Trevor
# 6
patchsvr enable just enables it to start at the next boot.If you want to start it now use patchsvr start
# 7
Hi
Yes sorry I do agree the command on the Update Connection Proxy is:
patchsvr start
Not that is makes any difference to me on 2 fronts:
1/
If I run this on my Update Connection proxy 'bdmdev':
bdmdev# patchsvr setup -l
Patch source URL: https://getupdates1.sun.com
Cache Location: /var/sadm/spool/patchsvr
Web proxy host name: X.X.X.X
Web proxy port number: 8080
Web proxy user:
bdmdev#
(I replaced the IP with X.X.X.X in the output above)
bdmdev# patchsvr enable
bdmdev# patchsvr start
Starting Local Patch Server
bdmdev#
bdmdev# ps -eaf | grep -i patch
root 15811 245680 14:35:02 pts/40:00 grep -i patch
bdmdev#
So still no 'patch' process running.
2/
I now have the patch client on another server working I believe, though perhaps only partially.
bdmprod# smpatch get
patchpro.backout.directory"" ""
patchpro.download.directory/var/sadm/spool /var/sadm/spool
patchpro.install.types -rebootafter:reconfigafter:standard
patchpro.patch.sourcehttp://bdmdev:3816/solaris/https://getupdates1.sun.com/solaris/
patchpro.patchsetcurrent current
patchpro.proxy.host "" ""
patchpro.proxy.passwd********
patchpro.proxy.port 80808080
patchpro.proxy.user "" ""
bdmprod#
If I run:
updatemanager
I get the GUI and it reports on the patches I need, and I can read READMEs.
But there is no patch process running on the Update Connection Proxy, so why it it working?
It still works doing this on the Update Connection Proxy, not that the patcsvr is running any way:
bdmdev# patchsvr stop
Shutting down Local Patch Server
bdmdev# patchsvr disable
bdmdev#
Eg a test is I can view a readme of a patch that I know I have never looked at before on any of the 2 servers running 10.
This server doesnt have access to the internet. It is not even allowed access via the site proxy that is used by Update Connection Proxy (it is allowed through).
So though my understanding was growing, I have no idea why this would work?
PS: Is it just me that thinks the spell checker here is broken?
Cheers
Trevor
# 8
The Update Connection Proxy is a Java process which can be identified by the following options;/usr/java/bin/java -Djava.library.path=/usr/lib/cc-ccr/lib -Djava.endorsed.dirs
# 9
Hi
I was looking at applying patch 121118-08, as suggested and we are at patch level 06.
1/
I tried through the GUI (Update Manager) initially. It downloaded it, but couldnt apply the patch. Perhaps that makes sense if I am running the GUI, so fair enough.
2/
I then tried:
patchadd ./121118-08
and it reports:
Patchadd is terminating.
WARNING: patchadd returned <5> for global zone
and the log file says:
more /var/sadm/patch/121118-08/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.
pkgadd: ERROR: The package <SUNWppror> is currently installed on the system in the
global zone. To install the new instance of this package in the global
zone only, you must specify the -G option. To install the new instance
of this package in all zones you must first remove the existing instance
of this package from the global zone first (via pkgrm) and then install
the new instance of this package in all zones.
pkgadd: ERROR: package <SUNWppror> cannot be installed on this system/zone
bdmprod#
3/
I then tried:
patchadd -G ./121118-08
and get:
Global patches.
0 Patch 121118-08 is for global zone only - cannot be installed on non-global zone.
No patches to install.
I do have sparse zones installed on this server.
Do I have to remove patch:
121118-06
Thanks
Trevor
# 10
Hi
> The Update Connection Proxy is a Java process which can be identified by the following options;
> /usr/java/bin/java -Djava.library.path=/usr/lib/cc-ccr/lib -Djava.endorsed.dirs
Thanks, so thats why there is no patch process.
I have multiple running:
bdmdev# ps -eafZ | grep java
globalroot68210Nov 11 ? 11:13 /usr/java/bin/java -Djava.library.path=/usr/lib/cc-ccr/lib -Djava.endorsed.dirs
globalroot 1178010 10:41:03 pts/10:14 /usr/java/bin/java -Djava.library.path=/usr/lib/cc-ccr/lib -Djava.endorsed.dirs
globalroot 1200710 10:43:34 pts/10:14 /usr/java/bin/java -Djava.library.path=/usr/lib/cc-ccr/lib -Djava.endorsed.dirs
globalroot 1131210 10:40:19 pts/10:14 /usr/java/bin/java -Djava.library.path=/usr/lib/cc-ccr/lib -Djava.endorsed.dirs
globalroot 27106 245680 15:38:33 pts/40:00 grep java
globalroot 1127410 10:39:45 pts/10:14 /usr/java/bin/java -Djava.library.path=/usr/lib/cc-ccr/lib -Djava.endorsed.dirs
bdmdevaproot 2893810 09:19:09 ? 223:14 java -Dorg.mortbay.xml.XmlParser.NotValidating=true -Djavax.net.ssl.trustStore=
globalroot 1354910 10:45:18 pts/10:14 /usr/java/bin/java -Djava.library.path=/usr/lib/cc-ccr/lib -Djava.endorsed.dirs
globalroot 1771110 11:11:17 pts/40:13 /usr/java/bin/java -Djava.library.path=/usr/lib/cc-ccr/lib -Djava.endorsed.dirs
globalroot 1350610 10:44:29 pts/10:14 /usr/java/bin/java -Djava.library.path=/usr/lib/cc-ccr/lib -Djava.endorsed.dirs
globalroot 1418310 10:47:34 pts/10:14 /usr/java/bin/java -Djava.library.path=/usr/lib/cc-ccr/lib -Djava.endorsed.dirs
globalroot 1197210 10:42:53 pts/10:15 /usr/java/bin/java -Djava.library.path=/usr/lib/cc-ccr/lib -Djava.endorsed.dirs
bdmdev#
and multiple:
patchsvr stop
I gather a few:
kill <pid>
are in order.
Thanks, this explains how I was able to patch my client that is seperate to the Update Connect Proxy server, when I thought the patchsvr process was stopped or disabled.
I am getting there, thanks for your patience.
Cheers
Trevor
# 11
Hello Trevor,
Please can you run the following commands on your patchsvr " bdmdev":
showrev -p | egrep -i '121453|121118|120335|121081|121563|122231|119788'
smpatch get
smpatch analyze
patchsvr setup -l
Please contact us once this has been done.
Regards,
# 12
Hi
I was thinking I was making progress on this, but perhaps not.
The patches I was trying to apply were to the client not the patchsvr (I would have done that next), but they are at the same patchlevel.
So the commands you asked me to run:
======================================
# showrev -p | egrep -i '121453|121118|120335|121081|121563|122231|119788'
Patch: 121453-02 Obsoletes: 120776-03, 121086-02, 119107-07 Requires: 119574-02, 119254-06 Incompatibles: Packages: SUNWcsu, SUNWcsr, SUNWccccrr, SUNWccccr, SUNWccfw, SUNWccsign, SUNW
cctpx, SUNWccinv, SUNWcsmauth, SUNWppror, SUNWpprou, SUNWupdatemgru, SUNWupdatemgrr, SUNWswupcl, SUNWccccfg, SUNWccfwctrl, SUNWppro-plugin-sunos-base
Patch: 121081-05 Obsoletes: Requires: 121453-02 Incompatibles: Packages: SUNWccccrr, SUNWccccr, SUNWccfw, SUNWccsign, SUNWcctpx, SUNWccinv, SUNWccccfg, SUNWccfwctrl
Patch: 122231-01 Obsoletes: Requires: 121453-02 Incompatibles: Packages: SUNWcctpx
Patch: 121118-06 Obsoletes: Requires: 121453-02 Incompatibles: Packages: SUNWppror, SUNWpprou, SUNWupdatemgru, SUNWupdatemgrr, SUNWppro-plugin-sunos-base
Patch: 119788-02 Obsoletes: Requires: 119107-02 Incompatibles: Packages: SUNWppror, SUNWpprou, SUNWpsvrr, SUNWpsvru
Patch: 120335-04 Obsoletes: Requires: 121453-01 Incompatibles: Packages: SUNWpprou
#
#
# smpatch get
patchpro.backout.directory"" ""
patchpro.download.directory/var/sadm/spool /var/sadm/spool
patchpro.install.types -rebootafter:reconfigafter:standard
patchpro.patch.source-https://getupdates1.sun.com/solaris/
patchpro.patchsetcurrent current
patchpro.proxy.host 131.242.45.141 ""
patchpro.proxy.passwd********
patchpro.proxy.port 80808080
patchpro.proxy.user "" ""
#
#
# smpatch analyze
119252-15 SunOS 5.10: System Administration Applications Patch
124188-01 SunOS 5.10: Trusted Solaris Attributes Patch
121308-08 SunOS 5.10: Solaris Management Console Patch
119313-08 SunOS 5.10: WBEM Patch
119963-08 SunOS 5.10: Shared library patch for C++
120753-03 SunOS 5.10: Microtasking libraries (libmtsk) patch
123494-03 X11 6.6.2: fontconfig patch
119812-02 X11 6.6.2: Freetype patch
119578-30 SunOS 5.10: FMA Patch
124237-01 SunOS 5.10: ftp patch
124444-01 SunOS 5.10: mountd patch
119685-09 SunOS 5.10: svc.startd patch
124235-01 SunOS 5.10: libpam.so.1 patch
120050-04 SunOS 5.10: usermod patch
122525-03 SunOS 5.10: Sun Fire V445 patch
124614-01 SunOS 5.10: sconadm proxy: UnknownHostException
120824-06 SunOS 5.10: Sun Fire (T1000, T2000) platform patch
124171-03 SunOS 5.10: flash issue with SUNWscn-base due to broken package
122517-03 SunOS 5.10: Sun Fire V215/V245 platmod patch
122513-02 SunOS 5.10: devfsadm SUNW_cfg_link.so patch
123334-04 SunOS 5.10: e1000g_transition patch
118367-04 SunOS 5.10: csh Patch
118557-07 SunOS 5.10: platform/sun4u/kernel/drv/sparcv9/su patch
123301-01 SunOS 5.10: i2c_svc patch
124327-02 SunOS 5.10: libpcp patch
124282-01 SunOS 5.10: init patch
122183-02 SunOS 5.10: logadm timestamp patch
118918-22 SunOS 5.10: Solaris Crypto Framework patch
123809-01 SunOS 5.10: rpcsec_gss patch
124280-01 SunOS 5.10: libkdb.so.1 patch
121944-02 SunOS 5.10: libpsvcpolicy and libpsvcpolicy_psr patch
123256-02 SunOS 5.10: eri patch
120629-05 SunOS 5.10: libpool patch
124442-01 SunOS 5.10: ssh patch
118666-09 J2SE 5.0: update 9 patch (5.0u9)
118667-09 J2SE 5.0: update 9 patch (5.0u9), 64bit
119845-04 SunOS 5.10: Patch for Australasia Region locale issues
123005-05 SunOS 5.10: Basic Registration Update
123011-01 SunOS 5.10: BR desktop icon patch
118777-08 SunOS 5.10: Sun GigaSwift Ethernet 1.0 driver patch
121118-08 SunOS 5.10: Sun Update Connection System Client 1.0.8
124393-01 CDE 1.6: Dtlogin smf patch
124405-01 CDE1.6: sdtfprop patch
124403-01 CDE1.6: dtstyle patch
124401-01 CDE1.6: dtpad patch
124399-01 CDE1.6: dtfile patch
124395-01 CDE1.6: dtaction patch
119117-24 Evolution 1.4.6 patch
119418-03 GNOME 2.6.0: Gnome On-screen Keyboard Patch
119414-12 GNOME 2.6.0: Gnome Accessibility Libraries Patch
119598-08 GNOME 2.6.0: Gnome Screen Reader and Magnifier Patch
120460-10 GNOME 2.6.0: Gnome libs Patch
120284-03 GNOME 2.6.0: GNOME CORBA ORB and component framework
119548-06 GNOME 2.6.0: Gnome multi-protocol instant messaging client patch
120288-03 GNOME 2.6.0: Gnome terminal Patch
119906-07 Gnome 2.6.0: Virtual File System Framework patch
122958-02 GNOME 2.6.0: RealPlayer media application
119059-20 X11 6.6.2: Xsun patch
123611-01 X11 6.6.2: X11 Trusted Extensions patch
124457-01 X11 6.6.2: xdm patch
#
# patchsvr setup -l
Patch source URL: https://getupdates1.sun.com
Cache Location: /var/sadm/spool/patchsvr
Web proxy host name: 131.242.45.141
Web proxy port number: 8080
Web proxy user:
#
========================================
As I realised late on Thursday (not in on Friday) the update manager on the patchsvr was pointing to the web and not the patcsvr, OOOPs, sorry everyone.
I tried to correct this with:
==================
bdmdev# smpatch set patchpro.proxy.host=""
bdmdev# smpatch set patchpro.patch.source=http://bdmdev:3816/solaris/
bdmdev# smpatch get
patchpro.backout.directory"" ""
patchpro.download.directory/var/sadm/spool /var/sadm/spool
patchpro.install.types -rebootafter:reconfigafter:standard
patchpro.patch.sourcehttp://bdmdev:3816/solaris/https://getupdates1.sun.com/solaris/
patchpro.patchsetcurrent current
patchpro.proxy.host "" ""
patchpro.proxy.passwd********
patchpro.proxy.port 80808080
patchpro.proxy.user "" ""
bdmdev#
bdmdev# smpatch get
patchpro.backout.directory"" ""
patchpro.download.directory/var/sadm/spool /var/sadm/spool
patchpro.install.types -rebootafter:reconfigafter:standard
patchpro.patch.sourcehttp://bdmdev:3816/solaris/https://getupdates1.sun.com/solaris/
patchpro.patchsetcurrent current
patchpro.proxy.host 131.242.45.141 ""
patchpro.proxy.passwd********
patchpro.proxy.port 80808080
patchpro.proxy.user -""
bdmdev#
bdmdev# smpatch analyze
Failure: Cannot connect to retrieve detectors: Internal Server Error
bdmdev# updatemanager
Java Accessibility Bridge for GNOME loaded.
< - I then updated "Manage Subscription" Just in case it needed it.
bdmdev#
bdmdev# smpatch analyze
Failure: Cannot connect to retrieve Database/current.zip: Proxy Error ( Host was not found. For more information about this event, see ISA Server Help. )
bdmdev#
================
So I have not even been using the patchsvr, OOOps, and now I am trying to use it I have a setup issue somewhere..
How does the patchsvr authenticate to the SUN site with the Sunsolve username? Is it the client that holds this and not the patchsvr, and it just passes through the patchsvr connection?
I do have a copy of "Sun Update Manager 1.0 Administrator Guide" in front of me, incase it appears that I am just getting the forum to do everything. I just seemed to miss the logic of how this sofware hangs together. I expect its straight forward but I have struggles with it.
Thanks
Trevor
# 13
Since the Sun UC proxy server has an internet connection the settings were correct the you had them, i.e. it should be pointing to the web. It is only the clients that need to be pointing to the Sun UC proxy URL.
Before anything else it is essential that you first upgrade the proxy to the latest the Sun UC version so that we are working with the most up-to-date version of the software.
Unset the patchpro source to the default:
$ smpatch unset patchpro.patch.source
Patch analysis should work again:
$ smpatch analyze
Apply the latest Sun UC patch:
$ smpatch update -i 121118-08
The "smpatch get" output should now show that the default URL is different than before.
https://getupdates1.sun.com/
Instead of
https://getupdates1.sun.com/solaris/
By the way the patch source in your "patchsvr setup -l" output has a trailing / missing. If applying the latest patch does not correct it then please correct it manually.
# 14
Hi
Thanks for not giving up on me.
I tried what you suggested:
bdmdev# smpatch unset patchpro.patch.source
bdmdev# smpatch analyze
119252-15 SunOS 5.10: System Administration Applications Patch
124188-01 SunOS 5.10: Trusted Solaris Attributes Patch
121308-08 SunOS 5.10: Solaris Management Console Patch
119313-08 SunOS 5.10: WBEM Patch
119963-08 SunOS 5.10: Shared library patch for C++
etc
etc
121118-08 SunOS 5.10: Sun Update Connection System Client 1.0.8
124393-01 CDE 1.6: Dtlogin smf patch
124405-01 CDE1.6: sdtfprop patch
124403-01 CDE1.6: dtstyle patch
124401-01 CDE1.6: dtpad patch
124399-01 CDE1.6: dtfile patch
124395-01 CDE1.6: dtaction patch
119117-24 Evolution 1.4.6 patch
119418-03 GNOME 2.6.0: Gnome On-screen Keyboard Patch
119414-12 GNOME 2.6.0: Gnome Accessibility Libraries Patch
119598-08 GNOME 2.6.0: Gnome Screen Reader and Magnifier Patch
120460-10 GNOME 2.6.0: Gnome libs Patch
120284-03 GNOME 2.6.0: GNOME CORBA ORB and component framework
119548-06 GNOME 2.6.0: Gnome multi-protocol instant messaging client patch
120288-03 GNOME 2.6.0: Gnome terminal Patch
119906-07 Gnome 2.6.0: Virtual File System Framework patch
122958-02 GNOME 2.6.0: RealPlayer media application
119059-20 X11 6.6.2: Xsun patch
123611-01 X11 6.6.2: X11 Trusted Extensions patch
124457-01 X11 6.6.2: xdm patch
bdmdev# smpatch update -i 121118-08
121118-08 has been validated.
Installing patches from /var/sadm/spool...
Failed to install patch 121118-08.
patchadd utility failed. Reason code :0
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:121118-08 Preparing checklist for non-global zone check...Checking non-global zones...This patch passes the non-global zone check.121118-08 Summary for zones:Zone bdmdevtestRejected patches:None.Patches that passed the dependency check:121118-08 Zone bdmdevdbRejected patches:None.Patches that passed the dependency check:121118-08 Zone bdmdevappRejected patches:None.Patches that passed the dependency check:121118-08 Zone bdmdevwebRejected patches:None.Patches that passed the dependency check:121118-08 Patching global zoneAdding patches...Checking installed patches...Verifying sufficient filesystem capacity (dry run method)...Patch 121118-08 failed to install due to a failure produced by pkgadd.See /var/sadm/patch/121118-08/log for detailsPatchadd is terminating. Restoring state for non-global zone bdmdevtest...WARNING: patchadd returned <5> for global zone
ALERT: Failed to install patch 121118-08.
/var/sadm/spool/patchpro_dnld_2006.11.27@16:58:09:EST.txt has been moved to /var/sadm/spool/patchproSequester/patchpro_dnld_2006.11.27@16:58:09:EST.txt
bdmdev#
bdmdev# more /var/sadm/patch/121118-08/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.
pkgadd: ERROR: The package <SUNWppror> is currently installed on the system in the
global zone. To install the new instance of this package in the global
zone only, you must specify the -G option. To install the new instance
of this package in all zones you must first remove the existing instance
of this package from the global zone first (via pkgrm) and then install
the new instance of this package in all zones.
pkgadd: ERROR: package <SUNWppror> cannot be installed on this system/zone
bdmdev# smpatch get
patchpro.backout.directory"" ""
patchpro.download.directory/var/sadm/spool /var/sadm/spool
patchpro.install.types -rebootafter:reconfigafter:standard
patchpro.patch.source-https://getupdates1.sun.com/solaris/
patchpro.patchsetcurrent current
patchpro.proxy.host 131.242.45.141 ""
patchpro.proxy.passwd********
patchpro.proxy.port 80808080
patchpro.proxy.user -""
bdmdev#
I looked back at my 2nd and last set of patch installs (about a month ago), and I added every single patch there was, but 2 failed to install, out of the 25:
1/ 123301-01
The log said:
The following requested patches do not update any packages installed on the system Packages from patch 123301-01 are not installed on the system. No patches to check dependency.
Surprising since I had done a dependecy check:
smpatch analyze -x idlist=patch_list_reqd
and
2/ 121118-08
The log was:
Dryrun complete.
No changes were made to the system.
pkgadd: ERROR: The package <SUNWppror> is currently installed on the system in the
global zone. To install the new instance of this package in the global
zone only, you must specify the -G option. To install the new instance
of this package in all zones you must first remove the existing instance
of this package from the global zone first (via pkgrm) and then install
the new instance of this package in all zones.
pkgadd: ERROR: package <SUNWppror> cannot be installed on this system/zone
I was using a script to install (in single user):
cat patch_list_reqd_ordered | while read f
do
echo ">>> $f <<<"
patchadd $f
echo " ======================================="
done
I'll look round more.
When I ran the:
I see the following was logged to: /var/adm/messages
Nov 27 16:58:14 bdmdev genunix: [ID 408114 kern.info] /pseudo/zconsnex@1/zcons@1 (zcons1) online
Nov 27 16:58:26 bdmdev root: [ID 702911 user.error] => Thread[Thread-20,5,main] <=Problem installing patches: Received a Manipulable event.
Nov 27 16:58:27 bdmdev root: [ID 702911 user.alert] => com.sun.patchpro.util.PatchBundleInstaller@151ac10 <=Failed to install patch 121118-08.
Nov 27 16:58:27 bdmdev patchadd utility failed. Reason code :0
Nov 27 16:58:27 bdmdev 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:121118-08 Preparing checklist for non-global zone check...Checking non-global zones...This patch passes the non-global zone check.121118-08 Summary for zones:Zone bdmdevtestRejected patches:None.Patches that passed the dependency check:121118-08 Zone bdmdevdbRejected patches:None.Patches that passed the dependency check:121118-08 Zone bdmdevappRejected patches:None.Patches that passed the dependency check:121118-08 Zone bdmdevwebRejected patches:None.Patches that passed the dependency check:121118-08 Patching global zoneAdding patches...Checking installed patches...Verifying sufficient filesystem capacity (dry
Nov 27 16:58:27 bdmdev root: [ID 702911 user.error] => Thread[Thread-20,5,main] <=Problem installing patches: ALERT: Failed to install patch 121118-08.
I also corrected the source URL for the patchsvr patch source manually (as I havent managed to patch yet):
bdmdev# patchsvr setup -p https://getupdates1.sun.com/
# 15
Please add 121118-08 in the global zone:root@global# patchadd -G /var/sadm/spool//121118-08-- Modski
# 16
bdmdev# zonename
global
bdmdev#
bdmdev# patchadd -G ./121118-08
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
Checking patches that you specified for installation.
Done!
Global patches.
0 Patch 121118-08 is for global zone only - cannot be installed on non-global zone.
No patches to install.
bdmdev#
So I still cannot install the latest version of the patch. Is it time to 'patchrm 121118-06'?
Is my patching issue anything to do with the way I initially installed 119788-02:
patchadd -G 119788-02
the 1st time though it installed:
SUNWppror - PatchPro core functionality (Root)
SUNWpprou - PatchPro core functionality (Usr)
When I ran it again, it installed:
SUNWpsvrr - Patch Server Deployment (Root)
SUNWpsvru - Patch Server Deployment (Usr)
# 17
It's certainly worth trying - if -06 was installed in a non-global zone (although I don't believe that would normally be possible), it would result in what you are seeing.Let us know how you get on.
# 18
Hi
OK, bad news for me, I tried to:
patchrm 121118-06
in the global zone.
But it came up with:
Cannot find the backout packages for 121118-06.
121118-06 cannot be backed out.
I checked through the patches I have applied to the system and this wasnt one of them. This is a Solaris 10 6/06 build that I jumpstarted. I see that this patch exists in the jumpstart area under:
<...>/install/sol10_606/Solaris_10/UpgradePatches
so it should have been installed at build.
I guess its time to log a job with SUN.
I'll be back :-). If I need to get help from the forum I'll probably log a new item as this dragged on a bit and I was thinking I had a remote client issue, but then found it was with my SUN Update Connection proxy and now a patching issue too.
Thanks for the help.
Trevor
# 19
We'll keep an eye out for your support case.
# 20
I've found that a Gnome login session can set TMPDIR to /tmp/USERNAME.. If you then su (rather than su - ) TMPDIR can be set to an unwritable (but existing) directory and you can get results like those above.
You may wish to consider su - when changing to root, or alternatively unsetting TMPDIR prior to adding the patch.
Regards,
-ethan
