i believe this is a side effect of patch 119108-03 look at the patch details. i'm not sure myself how to resolve this issue. and i've got the problem now on 2 Sun v40z and a W2100z. here's the relevant information hopefully someone is watching this list!
[ninesixeight]
[/root]
[root-137]:smpatch get
patchpro.backout.directory-""
patchpro.download.directory-/var/sadm/spool
patchpro.install.types -rebootafter:reconfigafter:standard
patchpro.patch.source-https://updateserver.sun.com/solaris/
patchpro.patchset-patchdb
patchpro.proxy.host -""
patchpro.proxy.passwd********
patchpro.proxy.port -8080
patchpro.proxy.user -""
patchpro.sun.passwd ********
patchpro.sun.user-""
[ninesixeight]
[/root]
[root-138]:smpatch analyze
120132-01 SunOS 5.10_x86: patch e1000g driver
119108-03 SunOS 5.10_x86, Sun Update Connection Client, System Edition 1.0
118993-03 SunOS 5.10_x86: /kernel/misc/scsi patch
119688-01 SunOS 5.10_x86: /usr/lib/inet/in.mpathd patch
120252-01 SunOS 5.10_x86: st & mt patch
118860-01 SunOS 5.10_x86: usbkbm patch
119857-01 SunOS 5.10_x86: pboot hangs on memory check
120102-01 SunOS 5.10_x86: patch usr/lib/libsmedia.so.1
120202-01 X11 6.8.0_x86: Xorg client libraries patch
119118-03 Evolution 1.4.6_x86 patch
119541-02 GNOME 2.6.0_x86: Gnome Dtlogin configuration Patch
119413-04 GNOME 2.6.0_x86: Nautilus libraries Patch
119116-08 Mozilla 1.7_x86 patch
119904-01 Openwindows 3.7.3_x86: Xview Patch
[ninesixeight]
[/root]
[root-139]:smpatch update
119108-03 has been validated.
119118-03 has been validated.
119116-08 has been validated.
119904-01 has been validated.
Installing patches from /var/sadm/spool...
WARNING: The installer cannot find the patch.
119108-03 has been applied.
WARNING: The installer cannot find the patch.
WARNING: The installer cannot find the patch.
WARNING: The installer cannot find the patch.
WARNING: The installer cannot find the patch.
WARNING: The installer cannot find the patch.
WARNING: The installer cannot find the patch.
WARNING: The installer cannot find the patch.
119118-03 has been applied.
WARNING: The installer cannot find the patch.
WARNING: The installer cannot find the patch.
119116-08 has been applied.
119904-01 has been applied.
/var/sadm/spool/patchpro_dnld_2005.07.26@16:42:17:EDT.txt has been moved to /var/sadm/spool/patchproSequester/patchpro_dnld_2005.07.26@16:42:17:EDT.txt
[ninesixeight]
[/root]
[root-140]:smpatch analyze
Failure: Cannot connect to retrieve Database/current.zip: Server returned HTTP response code: 403 for URL: https://getupdates.sun.com/solaris/
[ninesixeight]
[/root]
[root-141]:smpatch get
patchpro.backout.directory-""
patchpro.download.directory-/var/sadm/spool
patchpro.install.types -rebootafter:reconfigafter:standard
patchpro.patch.source-https://getupdates.sun.com/solaris/
patchpro.patchset-current
patchpro.proxy.host -""
patchpro.proxy.passwd********
patchpro.proxy.port -8080
patchpro.proxy.user -""
Joe:
You need to register your system after installing the patch. Before you installed the Sun Update Connection patch, you were running Patch Manager 2.0, which doesn't require registration. After you installed the patch in question, you were running the Sun Update Connection, which does require registration.
You will need to run the updatemanager command. Make sure to set the DISPLAY command so the GUI can be displayed. This will launch the Basic Registration client. Once your system is registered, you'll be able to retrieve updates and metadata.
Frederic Jean
Same thing happened to me with a W1100z, Sun support referenced has a post describing the issue, however this is not acceptable, I was using a documented command and it "broke" my stock sun system. By upgrading smpatch from Patch Manager 2.0 to Sun Update Connection patch e.g. "the evil patch 119108-03 pushed on unsuspecting users".
http://forum.sun.com/thread.jspa?threadID=25610&tstart=0
[root-140]:smpatch analyze
Failure: Cannot connect to retrieve Database/current.zip: Server returned HTTP response code: 403 for URL: https://getupdates.sun.com/solaris/
***
You need to register your system after installing the patch. Before you installed the Sun Update Connection patch, you were running Patch Manager 2.0, which doesn't require registration. After you installed the patch in question, you were running the Sun Update Connection, which does require registration.
You will need to run the updatemanager command. Make sure to set the DISPLAY command so the GUI can be displayed. This will launch the Basic Registration client. Once your system is registered, you'll be able to retrieve updates and metadata.
Note, I am not crazy about registering every box that comes through with Sun as I am a reseller and configure and ship systems. smpatch worked great for Solaris 5.8, 5.9, and 5.10 until now.
Rave,
Steve Campbell here from the University of Victoria.
We are in the process of testing Solaris 10 with the
idea of deploying it to our 100 or so Sun platforms.
We are trying to download the latest patch cluster
for Solaris 10 from the Sun website:
http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-access
but it appears that there are currently no patches available.
The message that comes up is;
"Sorry, the patch you requested could not be found."
Question: Are there patches available and, if so, where can
they be found?
Also, I heard a rumor that customers wishing to get the
latest and greatest patch cluster for Solaris 10 will need
a service contract. Is this correct?
Steve Campbell
Will this work if you don't run X on the machine you are trying to patch (e.g. setting your DISPLAY enviroment variable)?
I seem to recall you need to have both an X server and the pre-requsite of a frame buffer (or xvfb software) to run the X server on a Sparc server machine in order to do this.
You don't need to run an X server on the machine you are trying to patch. Just on the machine where you are displaying the results.
All you need on the server being patched is the X libraries.
Which are a standard part of solaris.
But there is no need to have any kind of graphics hardware there.
Right, I am of the same opinion! That SUCKS!
Desktop or server - I CAN'T go to every Workstation or log in to every server to start the Update Manager!
Here at the University of Erlangen - Nuernberg we, the Computing Center, provide a centralized Patch Service for every institute running Solaris. And we have no further acces to all the hosts (a few hundred outside of the Computing Center).
So it's a VERY bad Idea!!!
smpatch would be nice, but I suppose, we cannot use it as expected. We have to find a way or use the old patch mechanism running for years since Solaris 2.5.x
A CLI method of registering was introduced a month or 2 ago.
Its installed by 120776 on sparc at least. Not sure what the x86 version is.
Also, its not necessary to register all systems.
One nice feature of the updatemanager software is the ability to run a local patch caching proxy. Only the proxy needs to be registered, then you can point all the rest of your servers at it.
setup one or two solaris 10 boxes as a patch proxy
register the boxes and point all the other solaris 8/9/10 sparc and x86/x64 boxes at them.
That's it!
On the clients I do this after pointing to the patch proxy.
smpatch analyze
smpatch download
smpatch <however you prefer to install>
The point is do the download first so all the patches will be on the client. If it's a desktop or other machine you want to do smpatch update on, then you are ready. If you have dev/test/prod boxes, then download on all the related boxes the same day (so the patchdb will be the same) and apply them using the download order file written.
on another note... Sun Update Connection Client v1.0, command line registration (see patch readme for full syntax) partial listing from readme file.
####
#
# The Register Subcommand
#
####
The CLI can be executed with parameters (optional) such a
/usr/sbin/sconadm register -a -r <registration profile> -u <user name> -h <host name> -e softwareUpdate -p <proxy host>[:proxy port] -x <proxy uile>
-a : Accept Terms of Use and Binary Code License (no arg, -a means "agree", lack of -a means "disagree")
-e : Enable local client to be managed at the Sun-hosted Update Connection Service (the valid argument is softwareUpdate)
-E : Disable local client to be managed at the Sun-hosted Update Connection Service (the valid argument is softwareUpdate)
-h : Host name (Portal Common Name)
-l:location of log file
-N:Never register
-p : Proxy host:Proxy port
-r : The full path (or relative path) of a proposed registration profile
-s : Failsafe mode (no arg, -s means "fail-safe", lack of -s means "normal operation")
-u : User name (Sun Online Account)
-x : Proxy user name
The -u, -h, -e, -E, -p, -x parameters will override the values
specified in the registration profile.
If a particular parameter is specified in the profile or on the command line,
it is set as specified. If it is not specified in the profile, or on
the command line, then it is left alone.
==============================================================================
Register a New System
==============================================================================
1.) As a superuser, create a registrationprofile.properties file in the
/tmp directory.
For example, /tmp/registrationprofile.properties
userName=user123
password=abc123
hostName=
subscriptionKey=
portalEnabled=false
proxyHostName=
proxyPort=
proxyUserName=
proxyPassword=
2.) Run the following command to register a new system:
/usr/sbin/sconadm register -a -r /tmp/registrationprofile.properties
patch proxy setup: it's installed as patches now (two pkgs). Look for them with smpatch analyze or patchdiag -l
use "patchsvr setup -l" to list.
If it's running, stop it.
run "patchsvr" for syntax
run "patchsvr setup" for setup syntax.
takes about two minutes to do the setup and start it.
If you decide to cache all the signed files (*.jar), then you will need about 18.2GB for the 9,442 files.