Peculiar change in available patches
in [Solaris]
|
Prev: difference between sun cluster "/dev/did" and "/dev/global" devices
Next: 10_patch_report and other similar files from sunsolve.sun.com
From: Martin Paul on 15 Feb 2010 03:00 Gary Mills wrote: > I discovered that my entitlement had been changed to public: > > # cat cache/entitlement/https%3A%2F%2Fgetupdates1.sun.com%2F%2Fentitlement_client > ----START-ENTITLEMENT-TOKENS---- > Public > -----END-ENTITLEMENT-TOKENS----- Last Friday there was a period of about 12 hours where a faulty system caused the same problem for many (all?) SunSolve users. See: SunSolve forgot about contract http://www.mail-archive.com/pca(a)lists.univie.ac.at/msg01612.html Maybe this was part of your problem, too, besides the DHCP/Java issue. Martin. -- SysAdmin | Institute of Scientific Computing, University of Vienna PCA | Analyze, download and install patches for Solaris | http://www.par.univie.ac.at/solaris/pca/
From: Andrew Gabriel on 15 Feb 2010 04:03 In article <hl9qp5$ku8$1(a)canopus.cc.umanitoba.ca>, Gary Mills <mills(a)cc.umanitoba.ca> writes: > In <hl9ph8$cgu$1(a)news.eternal-september.org> andrew(a)cucumber.demon.co.uk (Andrew Gabriel) writes: > >>In article <hl6fau$mrd$1(a)canopus.cc.umanitoba.ca>, >> Gary Mills <mills(a)cc.umanitoba.ca> writes: >>> >>> I discovered that my entitlement had been changed to public: > [..] >>> One problem was that my ISP had changed my IP address through DHCP, >>> but had kept the same hostname. Sun's DHCP client left the old IP >>> address in /etc/inet/hosts . This has caused registration to fail in >>> the past. I corrected that and attempted to reregister: it never >>> completed. Curiously, `cacaoadm' had changed its java-home setting: >>> >>> # cacaoadm get-param java-home >>> java-home=/usr/jdk/jdk1.5.0_14 >>> # sconadm register -a -r RegistrationProfile.properties >>> sconadm is running >>> /* Never completes */ >>> # cacaoadm get-param java-home >>> java-home=/usr/jdk/jdk1.6.0_18 >>> >>> I knew there were problems with Java 1.6, so I set it back to my >>> /usr/java value: > [..] >>> After that, `smpatch analyze' showed a whole bunch of patches again. > >>Could I ask you to raise a bug on this please? >>(Or if you can send me all the necessary details, I can do it.) > > Which part? There were several problems, some of which are already > well known. cacaoadm not working with Java 6. Some colleagues are looking into things that don't work with Java 6. Thanks. -- Andrew Gabriel [email address is not usable -- followup in the newsgroup]
From: Andrew Gabriel on 15 Feb 2010 11:59 In article <hlb2lr$ql5$1(a)news.eternal-september.org>, andrew(a)cucumber.demon.co.uk (Andrew Gabriel) writes: > In article <hl9qp5$ku8$1(a)canopus.cc.umanitoba.ca>, > Gary Mills <mills(a)cc.umanitoba.ca> writes: >> In <hl9ph8$cgu$1(a)news.eternal-september.org> andrew(a)cucumber.demon.co.uk (Andrew Gabriel) writes: >> >>>In article <hl6fau$mrd$1(a)canopus.cc.umanitoba.ca>, >>> Gary Mills <mills(a)cc.umanitoba.ca> writes: >>>> >>>> I discovered that my entitlement had been changed to public: >> [..] >>>> One problem was that my ISP had changed my IP address through DHCP, >>>> but had kept the same hostname. Sun's DHCP client left the old IP >>>> address in /etc/inet/hosts . This has caused registration to fail in >>>> the past. I corrected that and attempted to reregister: it never >>>> completed. Curiously, `cacaoadm' had changed its java-home setting: >>>> >>>> # cacaoadm get-param java-home >>>> java-home=/usr/jdk/jdk1.5.0_14 >>>> # sconadm register -a -r RegistrationProfile.properties >>>> sconadm is running >>>> /* Never completes */ >>>> # cacaoadm get-param java-home >>>> java-home=/usr/jdk/jdk1.6.0_18 >>>> >>>> I knew there were problems with Java 1.6, so I set it back to my >>>> /usr/java value: >> [..] >>>> After that, `smpatch analyze' showed a whole bunch of patches again. >> >>>Could I ask you to raise a bug on this please? >>>(Or if you can send me all the necessary details, I can do it.) >> >> Which part? There were several problems, some of which are already >> well known. > > cacaoadm not working with Java 6. > Some colleagues are looking into things that don't work with Java 6. Don't worry, there already is one... CR 6921997 cacao service fails to start with Java 1.6.0_18 -- Andrew Gabriel [email address is not usable -- followup in the newsgroup]
From: Gary Mills on 15 Feb 2010 12:07
In <hlbuh1$se1$1(a)news.eternal-september.org> andrew(a)cucumber.demon.co.uk (Andrew Gabriel) writes: >In article <hlb2lr$ql5$1(a)news.eternal-september.org>, > andrew(a)cucumber.demon.co.uk (Andrew Gabriel) writes: >> In article <hl9qp5$ku8$1(a)canopus.cc.umanitoba.ca>, >> Gary Mills <mills(a)cc.umanitoba.ca> writes: >>> In <hl9ph8$cgu$1(a)news.eternal-september.org> andrew(a)cucumber.demon.co.uk (Andrew Gabriel) writes: >>>>In article <hl6fau$mrd$1(a)canopus.cc.umanitoba.ca>, >>>> Gary Mills <mills(a)cc.umanitoba.ca> writes: >>>>> >>>>> One problem was that my ISP had changed my IP address through DHCP, >>>>> but had kept the same hostname. Sun's DHCP client left the old IP >>>>> address in /etc/inet/hosts . This has caused registration to fail in >>>>> the past. I corrected that and attempted to reregister: it never >>>>> completed. Curiously, `cacaoadm' had changed its java-home setting: >>>>> >>>>> # cacaoadm get-param java-home >>>>> java-home=/usr/jdk/jdk1.5.0_14 >>>>> # sconadm register -a -r RegistrationProfile.properties >>>>> sconadm is running >>>>> /* Never completes */ >>>>> # cacaoadm get-param java-home >>>>> java-home=/usr/jdk/jdk1.6.0_18 >>> >>>>Could I ask you to raise a bug on this please? >>>>(Or if you can send me all the necessary details, I can do it.) >>> >>> Which part? There were several problems, some of which are already >>> well known. >> >> cacaoadm not working with Java 6. >> Some colleagues are looking into things that don't work with Java 6. >Don't worry, there already is one... >CR 6921997 cacao service fails to start with Java 1.6.0_18 Good. I discovered that when I tried it this morning: # cacaoadm stop # cacaoadm get-param java-home java-home=/usr/jdk/jdk1.5.0_23 # cacaoadm set-param java-home=/usr/jdk/jdk1.6.0_18 # cacaoadm start Error when trying to start SMF service: [svc:/application/management/common-agent-container-1:default]. Please check the SMF log file for more information: [/var/svc/log/application-management-common-agent-container-1:default.log]. There was not much of interest in the log. -- -Gary Mills- -Unix Group- -Computer and Network Services- |