sconadm register - exception in web communication
I'm trying to use sconadm to register a machine.
It is failing, which is not great, but what is most annoying is that I cannot get it to output any useful error message.
All I get is:
# sconadm register -a -r ./registrationProfile.properties
sconadm is running
Authenticating user ...
Exception in web service communication
I have set the web proxy in the properties file (and tried on the command line). Even if I hadn't I would expect an error indicating that communication could not be established with the web server if that was the problem.
I have tried using the -l flag to specify a log file but I get this message (e.g):
The location of log file ./scon.log doesn't exist
(where ./scon.log is the arg I passed to -l)
I have got patch 121454-02 installed.
How do I go about diagnosing what is going wrong?
Thanks,
Robert
# 1
Hi Robert,
The error indicates that there is some problem connection to the Update Connection server at Sun. You are right, it is not very helpful in diagnosing the specific problem.
Things you can check are,
* look at the /tmp/basicreg<year><date><timestamp>.log. on the client box and see if this gives you further details of the error
* ensure that you can telnet to the server at Sun
# telnet cns-services.sun.com 443
This error has also been logged as bug 6348265. This bug describes the fact that sometimes repeated registration attempts are required before registration is successful.
Regards,
ForumModerator
# 2
Aha. The log file provides a little bit extra information although not quite enough I think.
Here is the extract from the end of the log:
INFO: setting secure proxyPort:8000
12-Jan-2006 10:41:48 com.sun.cns.basicreg.common.ProxyManager setProxySettings
INFO: new proxy setting is OK !
12-Jan-2006 10:41:48 com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: userName = rgreig
12-Jan-2006 10:41:48 com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: password = *****
12-Jan-2006 10:41:48 com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: hostName =rosenberg
12-Jan-2006 10:41:48 com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: subscriptionKey = ********
12-Jan-2006 10:41:48 com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: portalEnabled =false
12-Jan-2006 10:41:48 com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: proxyHost = webproxy.uk.jpmorgan.com
12-Jan-2006 10:41:48 com.sun.cns.basicreg.BasicRegCLI printRegistrationProfile
INFO: proxyPort = 8000
12-Jan-2006 10:41:48 com.sun.cns.basicreg.BasicRegCLI run
INFO: Authenticating user ...
12-Jan-2006 10:41:48 com.sun.cns.basicreg.adapter.eCRAdapter <init>
INFO: Using eCRAdapter endpoint := https://cns-services.sun.com/UserInformationS
ervice/UserInformationService
12-Jan-2006 10:42:51 com.sun.cns.basicreg.common.ProxyManager isSecureProxyEnabl
ed
INFO: secure proxy is enabled
12-Jan-2006 10:42:51 com.sun.cns.basicreg.adapter.Adapter connectToSun
INFO: secure proxy tested OK !
12-Jan-2006 10:42:51 com.sun.cns.basicreg.adapter.eCRAdapter authenticateUser
SEVERE: Exception in web service communication
12-Jan-2006 10:42:51 com.sun.cns.basicreg.adapter.eCRAdapter authenticateUser
SEVERE: java.lang.NullPointerException
12-Jan-2006 10:42:51 com.sun.cns.basicreg.adapter.eCRAdapter authenticateUser
SEVERE:
com.sun.cns.basicreg.adapter.eCRAdapter.authenticateUser(eCRAdapter.java:82)
com.sun.cns.basicreg.BasicRegCLI.authenticateUser(BasicRegCLI.java:1016)
com.sun.cns.basicreg.BasicRegCLI.run(BasicRegCLI.java:653)
com.sun.cns.basicreg.BasicRegCLI.main(BasicRegCLI.java:548)
12-Jan-2006 10:42:51 com.sun.cns.basicreg.BasicRegCLI run
SEVERE: Exception in web service communication
12-Jan-2006 10:42:51 com.sun.cns.basicreg.BasicRegCLI run
SEVERE: Exception in web service communication
Any idea what the NullPointer actual results from? It does appear that it can connect to the web server. Is there any way to get it do output a stack trace?
I can't use telnet since I need to go via a web proxy.
Is the -l option to sconadm supposed to allow you to change the location of the logfile from the default in /tmp? If so, that's another bug since it does not appear to work.
Thanks for your help,
Robert
# 3
The register Subcommand
The synopsis of the sconadm register command is as follows:
# /usr/sbin/sconadm register [ -a ] [ -r <reg-profile> ] [ -u <user-name> ] [ -h <host-name> ] [ -e softwareUpdate ] [ -p <proxy-host>[:proxy-port] ] [ -x <proxy-user-name> ] [ -l <log-file> ] [ -s ] [ -N ]
The register subcommand uses the following command-line options:
-a
Agree to the Terms of Use and the Binary Code License. When omitted, you disagree with the Terms of Use and the Binary Code License.
-e softwareUpdate
Enable this system to be managed by the Sun Update Connection web application.
-E softwareUpdate
Disable this system from being managed by the Sun Update Connection web application.
-h host-name
Specify the host name, host-name, of this system (Portal Common Name).
-l log-file
Specify the location of the log file, log-file.
-N
Declare that you will never register this system.
-p proxy-host[:proxy-port]
Specify the host name and optional port number of the network proxy if your system connects to the Internet through a network proxy.
-r reg-profile
Specify the full or relative path to the registration profile to use.
-s
Register the system in failsafe mode.
-u user-name
Specify the user name of your Sun Online Account.
-x proxy-user-name
Specify the user name for the network proxy. This user name is only needed if your network proxy requires authentication.
When you specify any of the -u, -h, -e, -E, -p, and -x options, the values specified on the command line override the values you specified in the registration profile.
If you specify a parameter value in the profile or on the command line, the value is set as specified. If you did not specify a value in the profile or on the command line, the value is unchanged.
bug 6348265 explains whya you have not been succesful registering.
# 4
Thanks for the response.Dumb question of the day: how do I view bug report 6348265?I have searched all over the sunsolve site and I cannot find this bug.Thanks,Robert
# 5
Hello,Bug 6348265 is being reviewed by engineering, the information about this bug is not publicly available yet.
# 6
Hi,OK, then I am confused. What was the meaning of your post caguaedson?Is there no way I can find out why this doesn't work for me?Thanks,Robert
# 7
Hi,
we suggest that you can try registering this host bypassing your proxy and then changing the proxy settings back to normal
after the registration process has completed.
This workaround has worked for other customers with the same problem and may help you until a proper bug fix has been released.
Thank you.
Vanessa
# 8
I'm afraid this won't be possible - we are behind a firewall and don't have direct internet access except via the proxy.I suppose I'll just have to wait until a patch is released. Do you have an ETA on a patch?Thanks,Robert
# 9
There is currently no ETA on the patch as the bug report is still being reviewed by the engineering team (which is why it is not publicly viewable).
We have had some customers who have reported that uninstallling and re-installing the software has resolved the issue for them and allowed them to register and some have even reported that freshly downloading the install package has helped but I would stress that this has not worked in the majority of cases.
Sorry we couldnt be more help at this time.
# 10
Nice thread.So how are customers behind a firewall supposed to get Solaris 10 patches in the meantime?
# 11
Solaris 10 patches can still be downloaded manually from http://sunsolve.sun.com .
# 12
Understood. But not in "clusters".Is there an alert list to find out when this patch is released?
# 13
Patch clusters can still be downloaded, after logging on to SunSolve, go to "Patches and Updates" and then "Recommended and Security Patches ". You will find patch clusters available for download.
At the moment we don't know the patch number that will fix this issue. When bug 6348265 becomes publicly available you will be able to follow the progress via the bug report.
# 14
Thanks for clarification. I didn't realize the Recommended clusters were still awailable for Solaris 10 -- the 11/29/05 patch policy announcement threw me off.
# 15
Any updates on this issue?I opened a support case last week on this problem, and there is apparently no fix released yet. Unfortunately I cannot avoid using a proxy, so it's the Recommended bundle for now. Thanks...
cbella at 2007-7-21 14:58:41 >
# 16
TTT - any updates on the registration bug?Thanks...
cbella at 2007-7-21 14:58:41 >
# 17
The reason I ask is because the 10_Recommended bundle no longer appears on patches.sun.com (the README files are there, but neither the SPARC nor x86 zip files are there, for some reason).
So, I don't have either method available at this point. I simply cannot bypass our proxy environment. My service request didn't go anywhere. How should I go about patching?Thanks...
cbella at 2007-7-21 14:58:41 >
# 18
Please let us know what errors you recieve whilst attempting to download: 10_Recommended.zipI have tested this locally without any issues.
# 19
I'm trying to download from ftp://patches.sun.com/patchroot/clustersThe 10_Recommended.zip file doesn't appear in the directory listing -- just the accompanying README file. It has been this way for a while now. -c
cbella at 2007-7-21 14:58:41 >
# 20
Under the new patch policy, access to patches, or what we now call Software Updates, is restricted. Security fixes and hardware driver updates are publicly available for free, but access to all other software updates (including patch clusters) requires a Sun Service Plan.
Since ftp only allows for anonymous access it is not possible to have the clusters available via ftp. To get these login to Sunsolve.
# 21
Great, thanks for the tip on bundles. It's manual, but it works.
Regarding the sconadm register bug -- will this be fixed someday? It's been broken here for two months, and my local reps still tell me that Update Connection is the one true way to patch S10.
I can only imagine that many other Sun customers are subject to the same sort of corporate environment (must always use the proxy). How are they getting around this bug? Has anybody successfully uninstalled and reinstalled update manager?
I tried uninstalling update manager, but the document on docs.sun.com is already out of date. It runs you through manual patch removal, but all the patches mentioned have already been superceded -- I can't seem to untangle the new ones.
I can use the bundle all day, inefficient as it is. Unfortunately, this sort of thing hinders my ability to push for the adoption of S10. That in turn makes it hard for me to justify CoolThreads servers. I really want Niagara and S10 here. =-) Thanks again...
cbella at 2007-7-21 14:58:41 >
# 22
I'm having the same problem with sconadm.
smpatch on solaris 8 systems works fine. It can analyze, downlaod and update sytems.
For all i know smpatch will work fine on solaris 10 if we can just get sconadm to work.
my $.02:
Just in case Sun is watching these forums, automated patch managment is extremely critical. We have way to many servers to have to go to each one and use the The recommended patch cluster. the fact that Redhat up2date is working fine makes it a very enticing alternative.
I would rate Patch managment as the most important consideration when investing in an OS. Everything else is secondary, still very importaant, but the price of entry into considering all the other aspects of an OS is a good working patch managment tool.
At first we thought it was becuase the proxy was disallowing certain user_agents from the http header. I no longer think this is the case but I'm not sure. You can test this if you like to try and recreate the problem. Use one proxy (the real proxy) to only allow a certain user agent, then use another proxy such as squid to rename the user agent you are using to the one that is allowed. Then point the squid proxy to the real proxy. You can also use the "curl" tool to test your proxy. It has a user-agent option and curl seems to work better than lynx or wget for this sort of thing.
Other than that I have no idea why this is failing. It worked from home when I went through a standard squid proxy.
Here are the important bits from my log file:
May 30, 2006 2:29:20 PM com.sun.cns.basicreg.BasicRegCLI run
INFO: Authenticating user ...
May 30, 2006 2:29:20 PM com.sun.cns.basicreg.adapter.eCRAdapter <init>
INFO: Using eCRAdapter endpoint := https://cns-services.sun.com/UserInformationService/UserInformationService
May 30, 2006 2:29:26 PM com.sun.cns.basicreg.common.ProxyManager isSecureProxyEnabled
INFO: secure proxy is enabled
May 30, 2006 2:29:26 PM com.sun.cns.basicreg.adapter.Adapter connectToSun
INFO: secure proxy tested OK !
May 30, 2006 2:29:26 PM com.sun.cns.basicreg.adapter.eCRAdapter authenticateUser
SEVERE: Exception in web service communication
May 30, 2006 2:29:26 PM com.sun.cns.basicreg.adapter.eCRAdapter authenticateUser
SEVERE: java.lang.NullPointerException
May 30, 2006 2:29:26 PM com.sun.cns.basicreg.adapter.eCRAdapter authenticateUser
SEVERE:
com.sun.cns.basicreg.adapter.eCRAdapter.authenticateUser(eCRAdapter.java:82)
com.sun.cns.basicreg.BasicRegCLI.authenticateUser(BasicRegCLI.java:1016)
com.sun.cns.basicreg.BasicRegCLI.run(BasicRegCLI.java:653)
com.sun.cns.basicreg.BasicRegCLI.main(BasicRegCLI.java:548)
May 30, 2006 2:29:26 PM com.sun.cns.basicreg.BasicRegCLI run
SEVERE: Exception in web service communication
May 30, 2006 2:29:26 PM com.sun.cns.basicreg.BasicRegCLI run
SEVERE: Exception in web service communication
Thanks,
# 23
Unfortunately we've still not got to the bottom of what exactly causes the "Exception in web communication" error. It only appears to happen with certain types of proxy setups. Bypassing the proxy usually works. Is bypassing the proxy in your network for the purposes of registering the system an option for you?
Whether or not that is possible you may wish to raise a support case with Sun if you have a support contract so that your issue can be investigated in more depth after gathering all the necessary output which could be quite large.
# 24
I reviewed the bug and the issue lies in Java. The Java team is working on a fix and will release it shortly. SunUC support team will post an annoucement once the fix is avaliable.
A possible work around is trying pointing sconadm to a different proxy. Our testing has shown this solves the problem. It may require changing proxy to 2 or 3 times.
# 25
We're experiencing the same problem when using the GUI based registration (/usr/bin/updatemanager) on Solaris 10 x86 through a proxy.
> I reviewed the bug and the issue lies in Java. The
> Java team is working on a fix and will release it
> shortly. SunUC support team will post an annoucement
> once the fix is avaliable.
Where will SunUC support announce the (java) fix for this problem?
# 26
When the fix is available an announcement will be posted on this forum.
# 27
we downloadedjdk-6-beta-solaris-sparc.tar.Zfrom the sun web site and installed it.
$ ls -ld /usr/j*
lrwxrwxrwx1 rootroot12 Jun 8 14:33 /usr/java -> jdk/jdk1.6.0
This worked. We were able to register our system.
Hoiwever now on one of the systems i investigating the following error:
# smpatch analyze
Unexpected Failure: java.lang.Exception: Sequencer failed.
# 28
Great to hear that worked. For the new error can you see whether patch 117499-02 is installed and refer to the following thread: http://forum.sun.com/jive/thread.jspa?forumID=316&threadID=92186
# 29
Yes. I had Veritas 4.1MP1 installed on Solaris 10. Following the instructions in your thread link worked to resolve the smpatch problem. Thank you.Moving right along ......
# 30
ignore ... hadn't seen page 2 of this thread. Need to try that first befor i complain. ;)Message was edited by: KurtWagner
# 31
Given that it is now Dec 2006, I still see no progress on this issue (which is affecting a lot of customers).Is there a patch available yet? If not, any ETA?
# 32
Use the solution "mcadoo" mentioned.Update your jdk to jdk6 betaI followed his advise and everything did work just fineI was able to register my 2 new systems successfullyHope that helpsRegards
