Home.... | log in.... | Pub my question! | Sign-up....

Java-index >> Administration Tools >> Sun Update Connection-System

Why is getting patches so slow

We have a patch proxy setup to speed up installation of patches.

But it struck me that downloading a patch for the first time to cache it is surprisingly slow.

So I looked into it and observed that patch 113886-34 which was downloading at the time had taken 40 minutes to download about 25 Megs (of the 45 meg patch size). A speed which worked out at about 10k per second.

So as a comparison I manually downloaded the jar file from sunsolve and it came through at about 300k per second.

So why is downloading patches through smpatch update and a local patch proxy 30 times slower than downloading them manually.?

[643 byte] By [robert.cohen] at [2007-11-26 6:05:22]

«« Can't find a patch
»» In Progress Jobs

# 1

smpatch gets its patches from getupdates.sun.com, whereas patches from sunsolve come from patches.sun.com.Depending on the load on each server, different download speeds will be observed.

ForumModerator at 2007-7-6 13:32:43 >

top of Java-index,Administration Tools,Sun Update Connection-System...

# 2

Fair enough, but a factor of 30 seems extreme.Perhaps you need to allocate a bit more bandwidth to getpdates.sun.comIts normally the exteral internet connection thats the bottleneck.That would normally effect both servers equally, assuming they share a server room...

robertcohen at 2007-7-6 13:32:43 >

# 3

Testing today at approximately 12:00GMT, the download speed was 60Kb/s versus 250Kb/s. We do not have specific information regarding whether the servers are in different data centres and have differing outgoing bandwidth.

We have raised a query and this post should be updated when we receive an appropriate response.

ForumModerator at 2007-7-6 13:32:43 >

# 4

The main reason why the first download is slow is that the proxy must download the patch, validate it and then forward it to the smpatch client. It may not explain the full slow down, but it certainly does slow things down a lot. It's worth noting that once the patch is downloaded, your other update manager clients should be able to access it much faster.

This is an area that is being worked on right now. There are also other performance and capacity improvements coming up. I'll post more information to the forum once we can go public with them.

-- Fred

LostInColorado at 2007-7-6 13:32:43 >

# 5

I was measuring the speed that the patch proxy was downloading the patch, not the speed that the downstream client was getting it...

robertcohen at 2007-7-6 13:32:43 >

# 6

I'm seeing the exact same problem, in the "past" I was able to download patches with several hundred KB/sec, but now it crawls at 10-30k/sec which isn't really acceptable if you have to download a whole slew of patches totalling maybe 100MB.

It must be a bandwidth issue somewhere.

- Lasse

Lasse_Osterild at 2007-7-6 13:32:43 >

# 7

The SunSolve servers and the getupdates.sun.com servers are indeed located in different datacenters with differing bandwidths. However development is underway to improve the speed in a future release of Update Connection.

ForumModerator at 2007-7-6 13:32:43 >

# 8

Any updates on this ? Literally can't download anything via update connection due to slow links...

su_A_ve at 2007-7-6 13:32:43 >

# 9

Hi again.Can you tell us what patch source you are using(i.e. getupdates.sun.comor getupdates1.sun.com/solaris/or getupdates1.sun.com/ )Mod.

ForumModerator at 2007-7-6 13:32:43 >

# 10

Well, which one should it be ?

By default, I have:

patchpro.patch.sourcehttps://getupdates1.sun.com/

Once in a while it complains due to a connection reset (it's a slow link on our end as well at this point but still)

Since I have several systems with the same hardware, I've tried to set up a patch server. That one points to:

Patch source URL: https://getupdates1.sun.com/solaris/

But I also pointed to (as the instructions mention) to getupdates.sun.com

At that time, I pointed the clients to:

patchpro.patch.sourcehttp://xxx.xxx.xxx:3816/solaris/

Yesterday afternoon all I would get where connection resets.Now it starts to download a couple of patches but eventually it dies.

But I also noticed that some have it set to:

patchpro.patch.source - https://updateserver.sun.com/solaris/

So, which one should it be, a) for a direct connection and b) for the patch server.

All boxes are solaris 10, and the ones I've tested do have the latest (rev. 8) update manager patch.

Note that we have a SunSpectrum silver contract, so I'm not sure if we should be pointing this to somewhere else instead...

Even with our slow link, I never have problems downloading patches via RHN for our other servers... I thought after 1.5 years this would be 'useful'

In any case, smpatch get output is:

patchpro.backout.directory-""

patchpro.baseline.directory-/var/sadm/spool

patchpro.download.directory-/var/sadm/spool

patchpro.install.types -rebootafter:reconfigafter:standard

patchpro.patch.sourcehttp://xxx.xxx.xxx:3816/solaris/ https://getupdates1.sun.com/

patchpro.patchset-current

patchpro.proxy.host -""

patchpro.proxy.passwd********

patchpro.proxy.port -8080

patchpro.proxy.user -""

su_A_ve at 2007-7-6 13:32:43 >

# 11

For Update Connection 1.0.8 (with patch 121118-08 on Sparc) the default patch source is now "https://getupdates1.sun.com/" whereas previously for Update Connection 1.0.6 (with patch 121118-06 for Sparc) it was "https://getupdates1.sun.com/solaris/".

The getupdates1.sun.com address is now used for authentication but the patches and metadata are now downloaded from Akamai distributed servers. The same setting should be used on the Update Connection Proxy (patchsvr) also.

ForumModerator at 2007-7-6 13:32:43 >

# 12

If you set the proxy patch source to https://getupdates1.sun.com/ it breaks any solaris 9 hosts that are using the proxy.

robertcohen at 2007-7-6 13:32:43 >

# 13

Well, I can't update anything at this point. I just get "no patches required" after clearing the cache...

su_A_ve at 2007-7-6 13:32:43 >

# 14

Dear AllRegarding the slow response times are these still occurring please , the patches are now being downloaded via load balancing and the Akami distribution.Regarding the failure to download at all please see the other posts dealing with this issue.

ForumModerator at 2007-7-6 13:32:43 >

# 15

You havent addressed the issue of setting the patch source for a patch proxy tohttps://getupdates1.sun.com breaking solaris 9 clients.I thought you had to set it to that value to take advantage of the new akamai based fastness factor.

robert.cohena at 2007-7-21 14:58:56 >

# 16

HiDo you Solaris 9 clients have 112945 installed as detailed on the Patchmanager 2.0 web page (can be reached via SunSolve) ?Mod.

ForumModeratora at 2007-7-21 14:58:56 >

# 17

Yes. 112945-44

robert.cohena at 2007-7-21 14:58:56 >

# 18

May we have a fresh view of the output of ;

# smpatch get

SPARC:

# showrev -p | awk '/Patch: (121453|121118|120335|121081|121563|122231|119788)/ {print $2}'

x86:

# showrev -p | awk '/Patch: (121454|121119|120336|121082|121564|122232|119789)/ {print $2}'

# cat /etc/release

# cat /var/sadm/system/admin/CLUSTER

# /usr/lib/cc-ccr/bin/ccr -g cns.assetid

Thank you

ForumModeratora at 2007-7-21 14:58:56 >

# 19

I presume you mean on the proxy.

smpatch get

patchpro.backout.directory-""

patchpro.baseline.directory-/var/sadm/spool

patchpro.download.directory-/var/sadm/spool

patchpro.install.types -rebootafter:reconfigafter:standard

patchpro.patch.sourcehttp://bondi.anu.edu.au:3816/solaris/https://getupdates1.sun.com/

patchpro.patchset-current

patchpro.proxy.host -""

patchpro.proxy.passwd********

patchpro.proxy.port -8080

patchpro.proxy.user -""

showrev -p | awk '/Patch: (121453|121118|120335|121081|121563|122231|119788)/ {print $2}'

121453-02

121081-03

121081-04

121081-05

121081-02

121563-02

122231-01

121118-03

119788-02

121118-05

121118-06

121118-08

120335-04

cat /etc/release

Solaris 10 1/06 s10s_u1wos_19a SPARC

Use is subject to license terms.

Assembled 07 December 2005

cat /var/sadm/system/admin/CLUSTER

CLUSTER=SUNWCXall

bondi# /usr/lib/cc-ccr/bin/ccr -g cns.assetid

693338986

robert.cohena at 2007-7-21 14:58:56 >

# 20

Hello Robert,

The output which have provided shows that you have the most recent client patch installed, and that you have the proxy configured to point at itself for the patch source,

This is quite a commone configuration and would not cause the issue which you have described on your Solaris 9 clients.

Please can you run the following command on your Solaris 9 client system:

uname -a

showrev -p | grep 112945

smpatch get

date ; smpatch analyze ; date

tail -50 /var/adm/messages

On your patchsvr:

uname -a

smpatch get

patchsvr setup -l

date ; smpatch analyze ; date

tail -50 /var/adm/messages

Regards,

ForumModeratora at 2007-7-21 14:58:56 >

# 21

On sol9 client which has been freshly patched

mildura# uname -a

SunOS mildura 5.9 Generic_118558-35 sun4u sparc SUNW,Sun-Fire-V210

mildura# showrev -p | grep 112945

Patch: 112945-39 Obsoletes: 113829-04, 114724-01 Requires: Incompatibles: Packages: SUNWmccom, SUNWmcc, SUNWwbapi, SUNWwbcor, SUNWwbcou, SUNWwbmc, SUNWwbpro, SUNWmga, SUNWdclnt, SUNWlvma, SUNWpmgr, SUNWwbdev

Patch: 112945-40 Obsoletes: 113829-04, 114724-01 Requires: Incompatibles: Packages: SUNWmccom, SUNWmcc, SUNWwbapi, SUNWwbcor, SUNWwbcou, SUNWwbmc, SUNWwbpro, SUNWmga, SUNWdclnt, SUNWlvma, SUNWpmgr, SUNWwbdev

Patch: 112945-42 Obsoletes: 113829-04, 114724-01 Requires: Incompatibles: Packages: SUNWmccom, SUNWmcc, SUNWwbapi, SUNWwbcor, SUNWwbcou, SUNWwbmc, SUNWwbpro, SUNWmga, SUNWdclnt, SUNWlvma, SUNWpmgr, SUNWwbdev

Patch: 112945-43 Obsoletes: 113829-04, 114724-01 Requires: Incompatibles: Packages: SUNWmccom, SUNWmcc, SUNWwbapi, SUNWwbcor, SUNWwbcou, SUNWwbmc, SUNWwbpro, SUNWmga, SUNWdclnt, SUNWlvma, SUNWpmgr, SUNWwbdev

Patch: 112945-44 Obsoletes: 113829-04, 114724-01 Requires: Incompatibles: Packages: SUNWmccom, SUNWmcc, SUNWwbapi, SUNWwbcor, SUNWwbcou, SUNWwbmc, SUNWwbpro, SUNWmga, SUNWdclnt, SUNWlvma, SUNWpmgr, SUNWwbdev

Patch: 112945-35 Obsoletes: 113829-04, 114724-01 Requires: Incompatibles: Packages: SUNWmcc, SUNWwbapi, SUNWwbcor, SUNWwbcou, SUNWwbpro, SUNWmga, SUNWdclnt, SUNWlvma, SUNWpmgr, SUNWwbdev

Patch: 112945-14 Obsoletes: 113829-04 Requires: Incompatibles: Packages: SUNWwbapi, SUNWwbcor, SUNWwbcou, SUNWwbpro, SUNWmga, SUNWpmgr, SUNWwbdev

Patch: 112945-19 Obsoletes: 113829-04, 114724-01 Requires: Incompatibles: Packages: SUNWwbapi, SUNWwbcor, SUNWwbcou, SUNWwbpro, SUNWmga, SUNWdclnt, SUNWlvma, SUNWpmgr, SUNWwbdev

Patch: 112945-21 Obsoletes: 113829-04, 114724-01 Requires: Incompatibles: Packages: SUNWwbapi, SUNWwbcor, SUNWwbcou, SUNWwbpro, SUNWmga, SUNWdclnt, SUNWlvma, SUNWpmgr, SUNWwbdev

Patch: 112945-24 Obsoletes: 113829-04, 114724-01 Requires: Incompatibles: Packages: SUNWwbapi, SUNWwbcor, SUNWwbcou, SUNWwbpro, SUNWmga, SUNWdclnt, SUNWlvma, SUNWpmgr, SUNWwbdev

Patch: 112945-26 Obsoletes: 113829-04, 114724-01 Requires: Incompatibles: Packages: SUNWwbapi, SUNWwbcor, SUNWwbcou, SUNWwbpro, SUNWmga, SUNWdclnt, SUNWlvma, SUNWpmgr, SUNWwbdev

Patch: 112945-27 Obsoletes: 113829-04, 114724-01 Requires: Incompatibles: Packages: SUNWwbapi, SUNWwbcor, SUNWwbcou, SUNWwbpro, SUNWmga, SUNWdclnt, SUNWlvma, SUNWpmgr, SUNWwbdev

mildura# smpatch get

patchpro.backout.directory-""

patchpro.download.directory-/var/sadm/spool

patchpro.install.types -rebootafter:reconfigafter:standard

patchpro.patch.sourcehttp://bondi.anu.edu.au:3816/solaris/https://updateserver.sun.com/solaris/

patchpro.patchsetpatchdb1patchdb1

patchpro.proxy.host -""

patchpro.proxy.passwd********

patchpro.proxy.port -8080

patchpro.proxy.user -""

patchpro.sun.passwd ********

patchpro.sun.user-""

mildura# date ; smpatch analyze ; date

Mon Nov 13 15:40:48 EST 2006

No patches required.

Mon Nov 13 15:41:41 EST 2006

mildura# tail -50 /var/adm/messages

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: wrsmd6

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] wrsmd6 is /pseudo/wrsmd@6

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: wrsmd7

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] wrsmd7 is /pseudo/wrsmd@7

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: wrsmd8

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] wrsmd8 is /pseudo/wrsmd@8

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: wrsmd9

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] wrsmd9 is /pseudo/wrsmd@9

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: wrsmd10

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] wrsmd10 is /pseudo/wrsmd@10

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: wrsmd11

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] wrsmd11 is /pseudo/wrsmd@11

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: wrsmd12

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] wrsmd12 is /pseudo/wrsmd@12

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: wrsmd13

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] wrsmd13 is /pseudo/wrsmd@13

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: wrsmd14

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] wrsmd14 is /pseudo/wrsmd@14

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: wrsmd15

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] wrsmd15 is /pseudo/wrsmd@15

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: llc10

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: pm0

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] pm0 is /pseudo/pm@0

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: tod0

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] tod0 is /pseudo/tod@0

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: lofi0

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: fcp0

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp@0

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: rsm0

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] rsm0 is /pseudo/rsm@0

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: trapstat0

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] trapstat0 is /pseudo/trapstat@0

Nov 13 10:59:10 mildura pseudo: [ID 129642 kern.info] pseudo-device: rmcadm0

Nov 13 10:59:10 mildura genunix: [ID 936769 kern.info] rmcadm0 is /pseudo/rmcadm@0

Nov 13 10:59:16 mildura pseudo: [ID 129642 kern.info] pseudo-device: fcode0

Nov 13 10:59:16 mildura genunix: [ID 936769 kern.info] fcode0 is /pseudo/fcode@0

Nov 13 10:59:16 mildura pseudo: [ID 129642 kern.info] pseudo-device: tsalarm0

Nov 13 10:59:16 mildura genunix: [ID 936769 kern.info] tsalarm0 is /pseudo/tsalarm@0

Nov 13 10:59:33 mildura ntpdate[203]: [ID 774510 daemon.notice] step time server 150.203.22.28 offset 0.611256 sec

Nov 13 10:59:33 mildura syslog: [ID 522582 daemon.notice] /usr/sbin/pmconfig: /etc/power.conf line (18) failed to convert mount point /dev/md/dsk/d12 to prom name

Nov 13 10:59:34 mildura root: [ID 702911 daemon.error] PROVIDER RUNNER INFO: This is a normal reboot

Nov 13 10:59:35 mildura xntpd[378]: [ID 702911 daemon.notice] xntpd 3-5.93e Mon Sep 20 15:47:11 PDT 1999 (1)

Nov 13 10:59:36 mildura xntpd[378]: [ID 301315 daemon.notice] tickadj = 5, tick = 10000, tvu_maxslew = 495, est. hz = 100

Nov 13 10:59:36 mildura xntpd[378]: [ID 798731 daemon.notice] using kernel phase-lock loop 0041

Nov 13 10:59:36 mildura last message repeated 1 time

Nov 13 11:00:53 mildura SRS Proxy[620]: [ID 893007 daemon.notice] srsproxy started

Nov 13 11:00:55 mildura pseudo: [ID 129642 kern.info] pseudo-device: devinfo0

Nov 13 11:00:55 mildura genunix: [ID 936769 kern.info] devinfo0 is /pseudo/devinfo@0

mildura#

On the patchsvr

bondi# uname -a

SunOS bondi 5.10 Generic_118833-24 sun4u sparc SUNW,Sun-Fire-V240

bondi# smpatch get

patchpro.backout.directory-""

patchpro.baseline.directory-/var/sadm/spool

patchpro.download.directory-/var/sadm/spool

patchpro.install.types -rebootafter:reconfigafter:standard

patchpro.patch.sourcehttp://bondi.anu.edu.au:3816/solaris/https://getupdates1.sun.com/

patchpro.patchset-current

patchpro.proxy.host -""

patchpro.proxy.passwd********

patchpro.proxy.port -8080

patchpro.proxy.user -""

bondi# patchsvr setup -l

Patch source URL: https://getupdates1.sun.com/solaris/

Cache Location: /var/sadm/spool/patchsvr

Web proxy host name:

Web proxy port number: 8080

Web proxy user:

bondi# date ; smpatch analyze ; date

Mon Nov 13 15:43:12 EST 2006

120199-07 SunOS 5.10: sysidtool patch

119252-15 SunOS 5.10: System Administration Applications Patch

121430-12 SunOS 5.8 5.9 5.10: Live Upgrade Patch

124188-01 SunOS 5.10: Trusted Solaris Attributes Patch

119254-28 SunOS 5.10: Install and Patch Utilities 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

122535-01 SunOS 5.10: llib-lcrypto patch

124206-02 SunOS 5.10: libtsol 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

120845-03 SunOS 5.10: auditd 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

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

122658-03 SunOS 5.10: zonecfg patch

123911-01 SunOS 5.10: pam patch

118557-07 SunOS 5.10: platform/sun4u/kernel/drv/sparcv9/su patch

124327-02 SunOS 5.10: libpcp patch

124325-01 SunOS 5.10: rcm modules patch

124282-01 SunOS 5.10: init patch

123252-01 SunOS 5.10: platform/SUNW,Netra-T2000 patch

117463-03 SunOS 5.10: passwdutil Patch

122183-02 SunOS 5.10: logadm timestamp patch

118918-21 SunOS 5.10: Solaris Crypto Framework patch

122363-02 SunOS 5.10: fru_container.conf and libfruaccess.so.1 patch

123809-01 SunOS 5.10: rpcsec_gss patch

124280-01 SunOS 5.10: libkdb.so.1 patch

121947-01 SunOS 5.10: New Keyboards software needed

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

122856-03 SunOS 5.10: sendmail patch

119213-10 NSS_NSPR_JSS 3.11.3: NSPR 4.6.3 / NSS 3.11.3 / JSS 4.2.4

118666-09 J2SE 5.0: update 9 patch (5.0u9)

118667-07 J2SE 5.0: update 8 patch (5.0u8), 64bit

122119-05 SunOS 5.10: Patch for Arabic Fonts

119845-04 SunOS 5.10: Patch for Australasia Region locale issues

119703-07 SunOS 5.10: Patch for localeadm issues

118777-08 SunOS 5.10: Sun GigaSwift Ethernet 1.0 driver patch

118712-11 SunOS 5.10: Sun XVR-100 Graphics Accelerator Patch

118708-14 SunOS 5.10: Sun XVR-1200 and Sun XVR-600 Graphics Accelerator Patch

120928-12 SunOS 5.10: Sun XVR-2500 Graphics Accelerator Patch

124393-01 CDE 1.6: Dtlogin smf patch

119280-08 CDE 1.6: Runtime library patch for Solaris 10

119278-12 CDE 1.6: dtlogin 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

122669-01 Evolution 1.4.6: Cryptographic Library patch

119418-03 GNOME 2.6.0: Gnome On-screen Keyboard Patch

119414-11 GNOME 2.6.0: Gnome Accessibility Libraries Patch

120460-10 GNOME 2.6.0: Gnome libs Patch

120284-03 GNOME 2.6.0: GNOME CORBA ORB and component framework

122212-12 GNOME 2.6.0: GNOME Desktop Patch

119548-06 GNOME 2.6.0: Gnome multi-protocol instant messaging client patch

119906-07 Gnome 2.6.0: Virtual File System Framework patch

119115-20 Mozilla 1.7 patch

123611-01 X11 6.6.2: X11 Trusted Extensions patch

124457-01 X11 6.6.2: xdm patch

Mon Nov 13 15:43:58 EST 2006

bondi# tail -50 /var/adm/messages

Nov 11 05:05:45 bondi SRS Proxy[27248]: [ID 663108 daemon.error] Could not upload bulk message

Nov 11 05:10:29 bondi last message repeated 4 times

Nov 11 05:16:31 bondi SRS Proxy[27248]: [ID 663108 daemon.error] Could not upload bulk message

Nov 11 15:36:09 bondi sshd[8399]: [ID 140027 auth.error] warning: can't verify hostname: gethostbyname(hn.kd.dhcp) failed

Nov 11 15:46:39 bondi sshd[8683]: [ID 140027 auth.error] warning: can't verify hostname: gethostbyname(hn.kd.dhcp) failed

Nov 12 00:08:41 bondi ufs: [ID 845546 kern.notice] NOTICE: alloc: /export/stats: file system full

Nov 12 17:14:01 bondi explorer: [ID 702911 daemon.notice] Explorer started

Nov 12 17:24:51 bondi explorer: [ID 702911 daemon.notice] Explorer finished

Nov 12 17:25:53 bondi srsxfer[2861]: [ID 304048 daemon.error]

Nov 12 17:25:53 bondi Error: couldn't send message to proxy

Nov 12 17:25:53 bondi root: [ID 702911 daemon.error] ERROR: srsxfer returned an error (1)

Nov 13 00:03:47 bondi ufs: [ID 845546 kern.notice] NOTICE: alloc: /export/stats: file system full

Nov 13 02:00:32 bondi ufs: [ID 845546 kern.notice] NOTICE: alloc: /export/stats: file system full

Nov 13 05:23:59 bondi sshd[22596]: [ID 140027 auth.error] warning: can't verify hostname: gethostbyname(www.theboxnetwork.ie) failed

Just to be absolutely specific what I am talking about.

If I set the patch source on the patchsvr

patchsvr setup -p https://getupdates1.sun.com/

Then on the sol9 client I get

mildura# rm -rf /var/sadm/spool/*

mildura# smpatch analyze

Cannot connect to retrieve patchdb1: Server returned HTTP response code: 500 for URL: http://bondi.anu.edu.au:3816/solaris/

robert.cohena at 2007-7-21 14:58:56 >

# 22

Hello Robert,

Whilst there are no patches being recommended, this can not be automatically taken as being a problem or that some thing is broken.

The first thing that I need to ask is whether this system requires and patches?

From the output I can see that you are currently using the "patchdb1" patchset. Please can you try setting this to another patch set and running smpatch analyze as below:

smpatch set patchpro.patchset=patchdb

smpatch get

smpatch analyze

smpatch set patchpro.patchset=current

smpatch get

smpatch analyze

smpatch set patchpro.patchset=patchdb1

Please return the output generated.

Regards,

ForumModeratora at 2007-7-21 14:58:56 >

# 23

Sorry the output I sent last time was with the "working" settings.

With the broken (recommended) settings I get

Then on the sol9 client I get

mildura# rm -rf /var/sadm/spool/*

mildura# smpatch analyze

Cannot connect to retrieve patchdb1: Server returned HTTP response code: 500 for URL: http://bondi.anu.edu.au:3816/solaris/

robert.cohena at 2007-7-21 14:58:56 >

# 24

Ok I am confused now.

In the case where you have an Update Connection Proxy , the patch source on this proxy should be getupdates1 both in the output of smpatch get , and patchsvr setup -l . The patch source for any clients regardless of there o/s level should be <proxy>:3816 etc.

The patchset in the systems should normally be "current" not patchdb1 afaik.

ForumModeratora at 2007-7-21 14:58:56 >

# 25

Well, now I'm confused.

Even ignoring the local patch proxy and going straight to the sun server, solaris 9 hosts don't appear to be able to use patchset "current". The only values for patchset that appear to work for a solaris 9 server are patchdb1 (the default) and patchdb.

And when going to a sun server, the only value that seems to work for patch source is the default value of https://updateserver.sun.com/solaris/

Dropping the solaris off the end or changing the server name to getupdates1.sun.com doesnt seem to work.

And on the configuration of the local proxy. I presumed that the values set by "smpatch set" for the proxy machine only affected how that machine itself would get patches for patching itself.

I presumed that values set with "smpatch set" wouldnt effect the operation of the patch proxy as seen by other hosts.

And doing some experiments, as far as I have seen, changing values with "smpatch set" hasnt changed the behaviour of other hosts using it as a proxy.

But, using the values you have suggested...

On the patch proxy

bondi# smpatch get

patchpro.backout.directory-""

patchpro.baseline.directory-/var/sadm/spool

patchpro.download.directory-/var/sadm/spool

patchpro.install.types -rebootafter:reconfigafter:standard

patchpro.patch.source-https://getupdates1.sun.com/

patchpro.patchset-current

patchpro.proxy.host -""

patchpro.proxy.passwd********

patchpro.proxy.port -8080

patchpro.proxy.user -""

bondi# patchsvr setup -l

Patch source URL: https://getupdates1.sun.com/

Cache Location: /var/sadm/spool/patchsvr

Web proxy host name:

Web proxy port number: 8080

Web proxy user:

And on the solaris 9 client

smpatch get

patchpro.backout.directory-""

patchpro.download.directory-/var/sadm/spool

patchpro.install.types -rebootafter:reconfigafter:standard

patchpro.patch.sourcehttp://bondi.anu.edu.au:3816/solaris/https://updateserver.sun.com/solaris/

patchpro.patchsetpatchdb1patchdb1

patchpro.proxy.host -""

patchpro.proxy.passwd********

patchpro.proxy.port -8080

patchpro.proxy.user -""

patchpro.sun.passwd ********

patchpro.sun.user-""

mildura# smpatch analyze

Cannot connect to retrieve patchdb1: Server returned HTTP response code: 500 for URL: http://bondi.anu.edu.au:3816/solaris/

smpatch set patchpro.patchset=patchdb

mildura# smpatch analyze

Cannot connect to retrieve patchdb: Server returned HTTP response code: 500 for URL: http://bondi.anu.edu.au:3816/solaris/

smpatch set patchpro.patchset=current

mildura# smpatch analyze

Cannot connect to retrieve current: Server returned HTTP response code: 500 for URL: http://bondi.anu.edu.au:3816/solaris/

robert.cohena at 2007-7-21 14:58:56 >

# 26

And one last point.

On the patch proxy if I use

patchsvr setup -p https://getupdates1.sun.com/solaris/

then solaris 9 hosts can get patches ok. But solaris 10 hosts, while they don't get an error, they arent seeing any new patches either.

And if I use the value of

patchsvr setup -p https://getupdates1.sun.com/

Then solaris 10 hosts work correctly. But solaris 9 hosts get the error you say in the previous message.

So currently, I am having to switch the proxy back and forth between the 2 values..

robert.cohena at 2007-7-21 14:58:56 >

# 27

Robert,Please raise a support case with Sun on this issue. We'll need to collect data not suitable for collection on a forum (ie. the tomcat logs and possibly some snoop output).

ForumModeratora at 2007-7-21 14:58:56 >

# 28

I'd like to chime in on this.

Since the sun provided patching utilities have been very , well, let's just say, difficult, in the past, I am using pca v5.4. Even getting patches via pca or smpatch for me is pathetic slow.

Someone PLEASE fix the trickle bandwidth we are seeing.

Solaris 11/06 - U3 and Studio 11 have a TON of updates now, and updating a fresh system is bloody painful.

mickrussoma at 2007-7-21 14:58:57 >

# 29

A novel idea: Why doesn't sun just provide weekly rollups of all patches since the last update/point release so can get all patches mirrored locally and not have to talk to sun server from each updating machine. (Please also stop trying to charge for patches, charge for support, don't charge for patches).

- Mar 11, 2007 12:05 PM

mickrussoma at 2007-7-21 14:58:57 >

# 30

The SunUC proxy feature already provides a "download once, use on many clients" facility.

Additionally, Solaris 10 recommended patch clusters are still available and are updated monthly for those that wish to patch this way.

If you have issues you'd like to bring up regarding the way the service is delivered then I'd recommend bringing them up with your Sun Account Manager who can pass them on to the relevant teams.

ForumModeratora at 2007-7-21 14:59:01 >

Java programming resources: FAQs, tutorials, compiler and browser download sites, documentation, books lists, IDEs, etc.

Why is getting patches so slow

Administration Tools New Topic

Administration Tools Hot Topic

Administration Tools

All Classified