Unknown HTTP status code returned - Again
My SunUC clients are having problem in download several patches. A typical example is
This collection of patches is incomplete due to problems in downloading. It is advisable to retry the download later and see if the remaining patches can be downloaded. If they can, then the new download summary file will show the patches required and the order in which to install them. The patches failing to install are listed here:
119213-11 Unknown HTTP status code returned.
118666-11 Unknown HTTP status code returned.
118667-11 Unknown HTTP status code returned.
121118-10 Unknown HTTP status code returned.
118712-13 Unknown HTTP status code returned.
119117-28 Unknown HTTP status code returned.
122212-17 Unknown HTTP status code returned.
119115-22 Unknown HTTP status code returned.
119059-21 Unknown HTTP status code returned.
I tried to download patches in different days and time but the problem still persist.
However, I didn't have any problem in patching the SunUC proxy servers themselves. All patches on these servers were downloaded and applied successfully.
Only, the SunUC clients are having problem in downloading the patches listed above.
All my servers are running Solaris 10 3/05.
[1293 byte] By [
shena] at [2007-11-26 18:48:47]
# 1
Ensure you have patch 12111[8|9]-10 installed on all hosts, and patch 11978[8|9]-07 on your patchserver. Then observe this:
-
sol10sunucproxy # patchsvr setup -l
Patch source URL: https://getupdates1.sun.com/
Cache location: /var/sadm/spool/patchsvr
Web proxy host name: <your web proxy>
Web proxy port number: <your web proxy port>
sol10sunucproxy # smpatch get
...
patchpro.patch.source - http://sol10sunucproxy:3816/
patchpro.patchset - current
...
--
sol10client # smpatch get
...
patchpro.patch.source - http://sol10sunucproxy:3816/
patchpro.patchset - current
...
--
sol8or9client # smpatch get
...
patchpro.patch.source - http://sol10sunucproxy:3816/solaris/
patchpro.patchset - patchdb1
...
--
If that does not solve your issue, raise a Radiance case via your Customer Contact Centre, using your support contract.
--
Modski
# 2
I have patch 119788-02 and 121118-10 installed on my SunUC proxy servers.
From the README file of 119788-07:
The Sun Update Connection Proxy requires that the pkgs SUNWtcatu and
SUNWtcatr (Tomcat Servlet/JSP Container) be installed. This patch will
not be recommended for install by smpatch or Updatemanager if these
packages are not installed.
Packages SUNWtcatu and SUNWtcatr are installed on my SunUC proxy servers. However, when I run smpatch analyze on those servers, patch 119788-07 is not recommended. Shouldn't smpatch recommend and install patch 119788-07 since pre-req packages are installed?
shena at 2007-7-9 6:22:49 >
# 3
Could you post the contents of the following file (or a similarly named file in or under the same directory):/var/sadm/spool/patchsvr/%2Fentitlement%2F
# 4
Here they are
# pwd
# /var/sadm/spool/patchsvr/entitlement
# ls -l
ls -l
total 2
-rw-r--r--1 rootroot 187 Feb 18 11:12 https%3A%2F%2Fgetupdates1.sun.com%2F%2Fentitlement_lps
-rw-r--r--1 rootroot0 Feb 18 11:14 https%3A%2F%2Fgetupdates1.sun.com%2F%2Fentitlement_lps3060
# more https%3A%2F%2Fgetupdates1.sun.com%2F%2Fentitlement_lps
-START-ENTITLEMENT-TOKENS-
Solaris10Security
SolarisSecurityUpdates
SolarisDataIntegrityUpdates
SolarisHardwareUpdates
SolarisUtilityUpdates
Public
--END-ENTITLEMENT-TOKENS--
#
shena at 2007-7-9 6:22:49 >
# 5
From the entitlement contents, it looks like you are registered without a contract.Since patch 119788-07 isn't a 'free' patch, it won't be recommended.If you have a support contract, please try re-registering the patch server using the contract ID as the registration
# 6
So, what should I expect to see if registered WITH a contract ?
My local patch server is registered with a contract, and my
entitlement file contains exactly the same as previous posting.
At least I got no error registering the server with my
contract number. But I have not yet run that patch server long
enough too really see if I get all available patches. But it
would be useful to know what should be there.
Having issues right now, worked fine last Friday, broken now,
but that is so common, I will wait a few days and see what
happens ..
# 7
I would expect to see the following entries on a fully registered host:
-START-ENTITLEMENT-TOKENS-
Solaris10
SolarisAllUpdates
SolarisSecurityUpdates
Solaris10Security
SolarisDataIntegrityUpdates
SolarisHardwareUpdates
SolarisUtilityUpdates
Public
--END-ENTITLEMENT-TOKENS--
# 8
Re-registered some servers, I still do not get this list of
entitlements, despite entering a valid contract.
Some very old servers used to have this set, but
after re-register them, I get the incomplete list.
Are you sure Soalris10 and SolarisAllUpdates are still in use ?
Good to know before I attempt to log a service request.
# 9
Yes, those parameters and the entitlement file are still in use.
I would suggest as a test you try downloading the 119788-07 patch for Sparc else 119789-07 for X86 from SunSolve and install it on one of your Update Connection Proxy servers. Then update the patch source used by patchsvr to https://getupdates1.sun.com/ and then restart patchsvr to use the new setting.
$ patchsvr setup -p https://getupdates1.sun.com/
$ patchsvr stop
$ patchsvr start
# 10
I already have all current patches, and the correct patchsvr setup
when I did my last few tests.
Its probably errors in the Sun databases as usual relating
to my SunSolve account and contracts. Never worked very
smooth. I will have support look into it, nothing I can do
about it.
