Update manager dose not want to register
Hi
I have downloaded and installed the DVD version of solaris (sol-nv-b36-x86-dvd.iso). I have registered on Update connection and can login to the site. When I try to register my solaris box using sconadm I get the following from the log file.
Jun 29, 2006 8:30:35 PM com.sun.cns.basicreg.BasicReg loadPropertiesFromHomeDir
INFO: properties file loaded from the default config.properties
Jun 29, 2006 8:30:36 PM com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: userName = **********
Jun 29, 2006 8:30:36 PM com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: password = *****
Jun 29, 2006 8:30:36 PM com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: hostName =kotr-solaris
Jun 29, 2006 8:30:36 PM com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: subscriptionKey = ********
Jun 29, 2006 8:30:36 PM com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: portalEnabled =false
Jun 29, 2006 8:30:36 PM com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: proxyHost =
Jun 29, 2006 8:30:36 PM com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: proxyPort =
Jun 29, 2006 8:30:36 PM com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: proxyUsername =
Jun 29, 2006 8:30:36 PM com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: proxyPassword = ****
Jun 29, 2006 8:30:36 PM com.sun.cns.basicreg.BasicRegCLI run
INFO: Authenticating user ...
Jun 29, 2006 8:30:36 PM com.sun.cns.basicreg.cacao.ClientLoginCacaoAdapter getSCNClientSession
INFO: CREATING SCNClientSession
Jun 29, 2006 8:30:36 PM com.sun.cns.basicreg.cacao.ClientLoginCacaoAdapter$LoginAccountCallbackHandler handle
INFO: account callback setting username: louisnolan
Jun 29, 2006 8:30:41 PM com.sun.cns.basicreg.cacao.ClientLoginCacaoAdapter loginAccount
SEVERE: Error: login account exception: UserID not found.
Jun 29, 2006 8:30:41 PM com.sun.cns.basicreg.cacao.ClientLoginCacaoAdapter loginAccount
SEVERE:
com.sun.scn.jmx.impl.UISClientLoginModule.login(UISClientLoginModule.java:218)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja va:25)
java.lang.reflect.Method.invoke(Method.java:585)
javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
javax.security.auth.login.LoginContext$5.run(LoginContext.java:706)
java.security.AccessController.doPrivileged(Native Method)
javax.security.auth.login.LoginContext.invokeCreatorPriv(LoginContext.java:703)
javax.security.auth.login.LoginContext.login(LoginContext.java:575)
com.sun.scn.jmx.impl.UISClientLogin.login(UISClientLogin.java:198)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja va:25)
java.lang.reflect.Method.invoke(Method.java:585)
com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:4 14)
javax.management.StandardMBean.invoke(StandardMBean.java:323)
com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213 )
com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServer Interceptor.java:815)
com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
com.sun.jdmk.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServe rInterceptor.java:203)
com.sun.cacao.agent.DispatchInterceptor.invoke(DispatchInterceptor.java:662)
com.sun.cacao.agent.auth.impl.AccessControlInterceptor.invoke(AccessControlInte rceptor.java:618)
com.sun.jdmk.JdmkMBeanServerImpl.invoke(JdmkMBeanServerImpl.java:764)
com.sun.cacao.common.instrum.impl.InstrumDefaultForwarder.invoke(InstrumDefault Forwarder.java:106)
javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.jav a:1408)
javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java :81)
javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnec tionImpl.java:1245)
java.security.AccessController.doPrivileged(Native Method)
javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnecti onImpl.java:1348)
javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782 )
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.ja va:25)
java.lang.reflect.Method.invoke(Method.java:585)
sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:294)
sun.rmi.transport.Transport$1.run(Transport.java:153)
java.security.AccessController.doPrivileged(Native Method)
sun.rmi.transport.Transport.serviceCall(Transport.java:149)
sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
java.lang.Thread.run(Thread.java:595)
Jun 29, 2006 8:30:41 PM com.sun.cns.basicreg.cacao.ClientLoginCacaoAdapter getLoginResult
INFO: SCN Fault: UserID not found.
Jun 29, 2006 8:30:41 PM com.sun.cns.basicreg.BasicRegCLI run
SEVERE: Sun On-line Account authentication failed
I thought that the registration process might take a while before it sees my username and password but it has been more than a week since I registered on update connection. I have received mails from Sun thanking me for registering Solaris but the machine is still not registered.
[6229 byte] By [
louisnolan] at [2007-11-26 8:23:15]
# 1
Hi.Does the username you are using contain uppercase characters?
# 2
No, the username is all lowercase.
# 3
What was the URL of the site in which you registered on (the update connection site) and what username did you use?
# 4
I registered on this site with user name louisnolanhttps://sunconnection.sun.com/portal/index.jsp
# 5
We would first like to make sure you have all the latest patches. Can you post the output of:$ showrev -p | egrep -e '119575|119255|121119|121454|121082|121564|122232|120336'Also for reference provide the output of:$ cat /etc/release$ smpatch get
# 6
The output of the commands provided.
# showrev -p | egrep -e '119575|119255|121119|121454|121082|121564|122232|120336'
# cat /etc/release
Solaris Nevada snv_36 X86
Copyright 2006 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 20 March 2006
# smpatch get
patchpro.backout.directory"" ""
patchpro.download.directory/var/sadm/spool /var/sadm/spool
patchpro.install.types -rebootafter:reconfigafter:standard
patchpro.patch.sourcehttps://getupdates.sun.com/solaris/https://getupdates.sun.com/solaris/
patchpro.patchset-current
patchpro.proxy.host "" ""
patchpro.proxy.passwd********
patchpro.proxy.port -8080
patchpro.proxy.user -""
#
Thanks for all the assistance, I have been trying to get this working for weeks with no success, and being a complete noob in solaris is not helping a lot.
# 7
The showrev command didn't show the expected results. Perhaps the shell you're using couldn't interpret the command syntax correctly. Instead can you check for yourself whether the following X86 patches are installed and let us know:
121119-06 Sun Update Connection Client System Edition 1.0.4
121082-05 Connected Customer Agents 1.1.0
121564-02 Sun Update Connection Registration, version 1.0.3
122232-01 Sun Connection agents, transport certificate update
121454-02 Sun Update Connection Client Foundation
119255-24 Install & Patch Utilities Patch
119575-02 SU Patch
120336-04 Sun Update Connection Client Localization
Also provide the output of the following pkginfo commands:
$ pkginfo -l SUNWupdatemgru SUNWupdatemgrr
$ pkginfo -l SUNWpprou SUNWppror
# 8
The only way I know of to show patch information is showrev. Here is the output of showrev -a.
# showrev -a
Hostname: kotr-solaris
Hostid: 13c07233
Release: 5.11
Kernel architecture: i86pc
Application architecture: i386
Hardware provider:
Domain:
Kernel version: SunOS 5.11 snv_36
OpenWindows version:
Solaris X11 Version 6.6.3 9 March 2006
Patch: 118668-05 Obsoletes: Requires: Incompatibles: Packages: SUNWj5rt, SUNWj5cfg, SUNWj5dev, SUNWj5man, SUNWj5dmo
Patch: 116299-08 Obsoletes: Requires: Incompatibles: Packages: SUNWxsrt, SUNWjaxp, SUNWxrgrt, SUNWxrpcrt
Patch: 118669-05 Obsoletes: Requires: Incompatibles: Packages: SUNWj5rtx, SUNWj5dmx, SUNWj5dvx
Patch: 116303-02 Obsoletes: Requires: Incompatibles: Packages: SUNWxrpcrt
Patch: 121613-01 Obsoletes: Requires: Incompatibles: Packages: SUNWvts, SUNWvtsts
The output of the other commands :
# pkginfo -l SUNWupdatemgru SUNWupdatemgrr
PKGINST: SUNWupdatemgrr
NAME: Update Manager GUI (root)
CATEGORY: system
ARCH: i386
VERSION: 0.1,REV=2005.05.20.11.37
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: Update Manager GUI (root)
PSTAMP: azrael.20050829205814
INSTDATE: May 20 2006 09:21
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES:11 installed pathnames
5 shared pathnames
8 directories
PKGINST: SUNWupdatemgru
NAME: Update Manager GUI
CATEGORY: system
ARCH: i386
VERSION: 1.0,REV=2005.12.22.12.05
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: Update Manager GUI
PSTAMP: azrael.20051222143906
INSTDATE: May 20 2006 08:45
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES:69 installed pathnames
31 shared pathnames
40 directories
13 executables
1950 blocks used (approx)
# pkginfo -l SUNWpprou SUNWppror
PKGINST: SUNWppror
NAME: PatchPro core functionality (Root)
CATEGORY: system
ARCH: i386
VERSION: 5.0,REV=2006.01.20.22.46
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: PatchPro core functionality (Root)
PSTAMP: unknown20060120224642
INSTDATE: May 20 2006 08:45
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES:15 installed pathnames
8 shared pathnames
3 linked files
9 directories
1 executables
7 blocks used (approx)
PKGINST: SUNWpprou
NAME: PatchPro core functionality (Usr)
CATEGORY: system
ARCH: i386
VERSION: 5.0,REV=2006.01.20.22.46
BASEDIR: /
VENDOR: Sun Microsystems, Inc.
DESC: PatchPro core functionality (Usr)
PSTAMP: unknown20060120224642
INSTDATE: May 20 2006 08:45
HOTLINE: Please contact your local service provider
STATUS: completely installed
FILES:27 installed pathnames
7 shared pathnames
10 directories
6 executables
1 setuid/setgid executables
2373 blocks used (approx)
# 9
OK, so the previous showrev command did work, it just didn't return any output as none of the patches looked for were installed.
Since you are using 5.11 we are not actually sure what the situation is exactly with what patches you would require as haven't had any dealings yet with 5.11 and Sun UC. However looking at this again, the authentication error won't be related to the patches, you should still be able to register right now.
Can you create a new user account and try registering that (without specifying any subscription key), so that we can rule out any issue with a specific user account.
# 10
Created a new account using update manager and went through the registration process without any problems. At the end the wizard stated that the system is now registered.
Account name is louisnolan-za.
I am still getting "Authentication failed due to bad credentials" when checking for any available patches in update manager or when using smpatch.
# 11
I am getting the exact same error when I run smpatch. Is there a way to debug smpatch? I don't see a verbose or debug option, and the errors / stack traces in /var/adm/messages aren't all that useful.Thanks,- Ryan
# 12
Dear Louis / Ryan
Please try the following command , then grep the output file for various forms of erros. It can be quite large hence the redirection.
# smpatch analyze -@ > /tmp/smpatch.output
Let us know if you see anything of interest or that might alert you to a potential problem.
# 13
I am still getting the same messag when attempting to analyze my system:
$ smpatch analyze -@
Failure: Cannot connect to retrieve Database/current.zip: This system is currently unregistered and is unable to retrieve patches from the Sun Update Connection. Please register your system using the Update Manager.
Any thoughts what might be going on? Adding "-@" didn't increase the verbosity.
- Ryan
# 14
> $ smpatch analyze -@This command should be run as root, in the global zone, not as a user, and not in a local zone.
# 15
I did run smpatch as root from the global zone. Here is a sample session:
$ su
Password:
# smpatch analyze -@
Failure: Cannot connect to retrieve detectors: This system is currently unregistered and is unable to retrieve patches from the Sun Update Connection. Please register your system using the Update Manager.
Any idea why it's not printing verbose data? Also, do you happen to know why it's saying my system is unregistered (I ran sconadm, and that completed successfully according to the console output).
- Ryan
# 16
Run the command below -
# /usr/lib/cc-ccr/bin/ccr -g cns.assetid
If it returns a blank line then the system is not registered and you should run through the registration process again. If whoever it returns an integer value the system should be registered. You can also check the /tmp/basicreg*.log file from the time when you performed the registration...look towards the end of it to see if it reports any failures or success.
# 17
When I run ccr, it retuns an integer value:
$ /usr/lib/cc-ccr/bin/ccr -g cns.assetid
1XXXXXXXXXX
But when I run smpatch, it says my system is not registered:
# smpatch analyze
Failure: Cannot connect to retrieve Database/current.zip: This system is currently unregistered and is unable to retrieve patches from the Sun Update Connection. Please register your system using the Update Manager.
Any thoughts why smpatch thinks it's not regsitered?
- Ryan
# 18
Firstly, SunUC requires the end user version of Solaris 10 installed as a minimum requirement. If you have only the core or custom build it may not work and is not supported.
In your case the presence of an assetid does seem to indicate that the host is registered but the system is not recognised by the sun servers. Assuming the condition above has been satisfied try the following procedure -
Remove the current assetid
# /usr/lib/cc-ccr/bin/ccr -r cns.assetid
Re-register host
Attempt analysis again
# smpatch analyze
# 19
I would also note you are running a Nevada version of Solaris (Solaris.next) version. Although this should work for registration, please do not apply any patches. This may cause issues.
# 20
This is a Nevada build (OpenSolaris? SX? SXCR?) - does Sun even provide patches for those?
