This content has been marked as final. Show 98 replies
tried CLI today, still works OK :-) No contract, no proxy. (test with GUI yesterday)
sconadm register -a -r /usr/lib/breg/data/RegistrationProfile.properties
bash-3.00# sconadm register -a -r /usr/lib/breg/data/RegistrationProfile.properties
sconadm is running
Authenticating user ...
# Lines of this file should be of the form VAR=value, where VAR is one of
# TZ, LANG, CMASK, or any of the LC_* environment variables. value may
# be enclosed in double quotes (") or single quotes (').
-------------------- snip ---------------------------
<locale from="LC_ALL">C</locale> <=== This can't be localized for sucess
<last.boot.time format="verbatim">Sat Jul 8 09:47:18 CEST 2006</last.boot.time>
I changed the entry of the "/etc/default/init" file
after rebooting, I tryed to register wit the command line tool "sconadm":
# sconadm register -a -r /usr/lib/breg/data/RegistrationProfile.properties
sconadm is running
Authenticating user ...
getLocalHostNames() - UnknownHostExceptionjava.net.UnknownHostException: home.homeland: home.homeland
after that I tryed to register with the "updatemanager"
"Error in SWUP/Cacao Register System"
If you need more information, please let me know.
Thanks in advance.
Can you try the following steps:
1. Stop the cacao container by executing : cacaoadm stop
2. rm /var/scn/persistence/SCN*
3. /usr/lib/cc-cfw/framework/lib/cc-client-adm stop
4. /usr/lib/cc-cfw/framework/lib/cc-client-adm disable
6. cacaoadm start
Then try registering again.
I'm having the same problem with this. A newly installed Solaris 10 06/06 system. The only thing I have done prior to trying to register my system is to set the dhcp hostname and remove sendmail.
Despite numerous attempts, its still failing to register.
Can anyone from Sun provide an update on this issue, and is there a way for me to get my Subscription ID checked to make sure it hasn't somehow gotten locked or something ?
Some customers have reported that reverting to an account id (for the Sun Online Account) which contains only lowercase characters has resolved this problem.
If convenient please attempt to create a new Sun Online Account with only lowercase characters and try again. It would be helpful if you were to post results here , thanks.
If failing , please provide us with a grep'ed output of /var/adm/messages for cacao, thank-you.
I've done as you requested (created a new account, all lower case), and still no dice.
Now, when I try to register with either account, it gets to the last step where I specify to manage updates locally or use remote update management and then click on finish.
It then sits for around 3 minutes with a box saying 'Storing System Information' before telling me I am not connected to the net. Of course I am, as Im sending this message from the machine at the same time.
It looks like its not getting an answer from the registration server.
Anyway, the output you requested from /var/adm/messages:
Jul 21 11:24:26 Solaris cacao: [ID 702911 daemon.warning] com.sun.scn.jmx.impl.AbstractComponent.log : SCNClientConfigImpl.activate("Register the Solaris software without choosing an update option") -- module unlocked
Jul 21 11:24:28 Solaris cacao: [ID 702911 daemon.warning] com.sun.scn.jmx.impl.AbstractComponent.log : SCNClientConfigImpl.deactivate("Register the Solaris software without choosing an update option") -- module locked
Jul 21 11:24:53 Solaris cacao: [ID 702911 daemon.warning] com.sun.scn.jmx.impl.AbstractComponent.log : SCNClientConfigImpl.activate("Use Sun Update Manager and Sun Update Connection to manage updates") -- module unlocked
Jul 21 11:27:05 Solaris cacao: [ID 702911 daemon.warning] com.sun.scn.service.BaseServiceClient.dumpThrowable : XYXYXY
Jul 21 11:27:05 Solaris java.rmi.RemoteException: HTTP transport error: java.net.SocketException: Connection reset; nested exception is:
Jul 21 11:27:05 Solaris HTTP transport error: java.net.SocketException: Connection reset
Jul 21 11:27:05 Solaris at com.sun.scn.offering.service.ams.AssetMgmtServiceIF_Stub.registerAsset(AssetMgmtServiceIF_Stub.java:234)
Jul 21 11:27:05 Solaris at com.sun.scn.offering.prom.AssetManagementServiceProvider.registerAsset(AssetManagementServiceProvider.java:154)
Jul 21 11:27:05 Solaris at com.sun.scn.offering.swupom.SWUPOfferingInstance.register(SWUPOfferingInstance.java:500)
Jul 21 11:27:05 Solaris at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Jul 21 11:27:05 Solaris at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
Jul 21 11:27:05 Solaris at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Jul 21 11:27:05 Solaris at java.lang.reflect.Method.invoke(Method.java:585)
Jul 21 11:27:05 Solaris at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(StandardMetaDataImpl.java:414)
Jul 21 11:27:05 Solaris at javax.management.Sta
Jul 21 11:27:27 Solaris cacao: [ID 702911 daemon.warning] com.sun.scn.jmx.impl.AbstractComponent.log : SCNClientConfigImpl.deactivate("Use Sun Update Manager and Sun Update Connection to manage updates") -- module locked
Would the fact I am using 'Solaris' as a hostname have anything to do with it ? I have assumed not, as I've previously registered using this hostname, and it worked absolutely fine.
Well thanks Gunnar, but waiting until Suns Registration server may or may not decide to let me register correctly isn't really the answer.
I have tried again this afternoon, now its back to the original problem ie. the error message described by the OP.
I've been patiently testing and re-installing Solaris now for some time, working out the show stoppers to me using it as a new desktop OS, following the bugs and changes, doing the trials on behalf of Sun etc etc.
Now I'm ready to finally make the shift, having paid for an update manager subscription, and I find I cant get past the starting blocks.
And to be honest, it makes absolutely no sense at all, carrying on any further with the installation until this issue is resolved, as I dont wish to work with an unpatched system.
Solaris has come such a long way in the last couple of years, and it seems a shame to see something like this, which has generally worked well in the past, to let it down now.
If there is any further information I can supply which may help, I'm all ears!!