I installed update manager for solaris 10. Registered the system, installed some updates, worked fine. Had to later reinstall solaris 10, and update manager, now when i try to register system again i get the message, "System Name Already In Use". when i go the web site and logon, i see no systems listed to delete.Not able to change the host id during registration, so i am stuck. Any help would be appreciated, i am a solaris newbie.
I waited more than 24 hours and still not able to add my system again, I get the system name already exists message. When I log onto the Sun Update Connection web site, there are no systems listed for me to delete or update. Strange I can't see the system from the web page, but the registration process from the update manager client still thinks it exists.
I've got the same problem:
Let me try to make this clear. I registered the system a few days ago using the Update Manager client. I used the "Continue without a subscription key or enter one later" choice. I don't remember a checkbox for managing the system online.
I had to reinstall the OS today. The Update Manager registration now says , "Invalid System Name/System Name Already Used". I cannot use the client at all, because I now cannot get past the registration.
If I follow the directions in the manual to unregister/delete a system in the online Update Connection, I discover that I have no systems!
So i can neither delete the system, nor re-register it. It's not a matter of waiting 24 hours. I never deleted the system. It just isn't there. Seems like they've left a huge catch 22 bug in this thing.
I am having the same problem too.
Been working on a Solaris 10 (x86) installation which was registered with Sun Update Connection (without Subscription Key) - everything had been working fine.However, this is a test machine and I just performed a clean rebuild. When attempting to update the patches, I am instructed to register, but when the system information on Page 3 of the Registration GUI is sent to Sun, the following error is displayed: "Invalid System Name/System Name Already Used".
I do not see any tools to "unregister".If the Host Name and System ID and all of the other registration information that is resent to Sun matches what is already in their records, it seems like this would simply display a message that the machine is already registered and/or is being updated.
Unless I change the hostname, I am stuck at the moment. As was mentioned in some of the earlier posts, I am not able to patch my system as I am unable to get beyond the registration.
-jtb
Hi,
Process below should resolve the issue.
step to re-register a host:
Assumptions:
o Sun Update Connection 1.0 System Addition is properly installed
o The customer has a valid Contract ID
o The customer has a valid Subscription Key
o The customer has a UNIX background and has root user permissions
Steps:
On system:
(1) Launch a terminal session and log in as root
(2) Run following command and note the assetid number returned
/usr/lib/cc-ccr/bin/ccr -g cns.assetid
(3) Run these exact ccr commands as root, where <ASSETID> = the number
returned in above step:
/usr/lib/cc-ccr/bin/ccr -p cns.assetid -v <ASSETID>
and then
/usr/lib/cc-ccr/bin/ccr -p cns.transport.serverurl -v
"https://cns-transport.sun.com"
(4) Exit the terminal session
(5) Launch Update Manager.
(6) Select the File Menu
(7) Select Manage Subscription
(8) In the registration wizard, there are 3 fields: Username/ Password
/Subscription key (all 3 fields are required)
(8.1) Enter the Username /Password /Sub key
Let me know if this resolve the problem or not.
Scott
Just a side note...
...The Update Manager Administration Guide does mention to go to the following website to delete a system:
http://updates.sun.com
However, none of the systems that I registered are listed - my clients were never configured to be "managed at Sun Update Connection".
Is there any other way to remove system registration information or enable a system to be re-registered?It is a little difficult to "Delete System" when no systems are listed.
-jtb
Hi Scott.
Thanks for the quick reply.
> Assumptions:
>
> o Sun Update Connection 1.0 System Addition is properly installed
> o The customer has a valid Contract ID
> o The customer has a valid Subscription Key
> o The customer has a UNIX background and has root user permissions
I have a valid Sun Online Account, but do not have a Subscription Key.The workstation in question was registered without a Subscription Key which would still allow access to "limited updates".
When I ran the "ccr -g cns.assetid" command, the returned value is simply blank so there is no value to use with the "ccr --p cns.assetid" command.
Update Manager 1.0 is installed. The "updatemanager" command still launches the registration window.When registering with the option to "continue without a subscription key", once the registration information is passed to Sun, the "invalid system name/system name already used" error continues.
-jtb
> Hi,
>
> Process below should resolve the issue.
>
> step to re-register a host:
>
> Assumptions:
>
> o Sun Update Connection 1.0 System Addition is
> properly installed
> o The customer has a valid Contract ID
> o The customer has a valid Subscription Key
> o The customer has a UNIX background and has root
> user permissions
And what about those who don't have a contract and who either don't have or didn't use a subscription code?
>
> Steps:
>
> On system:
>
> (1) Launch a terminal session and log in as root
> (2) Run following command and note the assetid number
> returned
>/usr/lib/cc-ccr/bin/ccr -g cns.assetid
no assetid is returned
Scott:
As you have requested, here is some output generated when I run "updatemanager" in debug mode (Note: I have removed the encrypted keys that were listed as well as output that is listed from the "ifconfig" command):
I did check the contents of the "basicreg*.log" file and you are right, there is a lot of information there.The error that reports the "invalid system name" is listed in one of the INFO lines, but not sure I see any obvious errors leading up to it.Here is a section from that file which is produced when the system info is processed.
Hope some of this helps.
Note:I did install a "customized" install of the End User System Support set of packages during the system installation, but don't think I am missing any of the necessary packages. Again, this was all working before the operating system was reinstalled (using the same hostname and network settings as before).
Thanks
Jim
Message was edited by: ForumModerator
> Hi,
>
> Can you run updatemanager in debug mode and post the
> output.
>
> # updatemanager -debug
>
> Also there is a basic reg file cretaed in /tmp as
> below.
>
> basicreg20050812081105940.log
>
Both of those contain more information than I'd like to post here. Is there something in particular you are expecting? I did notice in the basicreg... file that assetid was blank there too.
> I get a line just like yours below, different hostname of course
It certainly appears that Sun is going to have to come up with some sort of fix or solution for workstations that are rebuilt and need to be reregistered.I originally feared that maybe I was missing something when I reinstalled Solaris 10 (x86), but not now - not when others are experiencing the same troubles.
I thought the "updatemanager" tool was working pretty well before I decided to rebuild my system. Again, hopefully Sun will come up with a solution and will keep us posted within this forum.
Jim
- do you have multiple machiens registered? or just this one?
- if yes: when re-registering - are you using the same 'common name' as another machine already registered?
if yes: that is the error. you cannot do that.
if no:
have you made any hardware changes since you registered?
i.e nic card, ram .. etc
if yes: what changed?
-> - do you have multiple machiens registered? or just this one?
-> - if yes: when re-registering - are you using the same 'common
-> name' as another machine already registered?
-> if yes: that is the error. you cannot do that.
Yes, multiple machines have been registered, but no two machines have the same hostname and/or hostid.The problem here, and I am sure that Sun understands this, is a machine that was previously registered was rebuilt - same hostname, same hostid as before.I am willing to believe that Sun will come up with a solution for this problem.
-jtb
jtb: thanks for the info.
I am not asking about the host id or the host name
I am asking about the 'common name' that is provided at the time of registration.
if this common name that you are using has been used by another machine, then you will get name already in use error.
> jtb: thanks for the info.
>
> I am not asking about the host id or the host name
> I am asking about the 'common name' that is provided
> at the time of registration.
At the time of original registration, no names of any kind are 'provided'. All such information is automatically determined and sent by the registration 'wizard', and the user has no choice. It apparently indentifies the system by its serial number (in the case of Sun hardware anyway) and / or hostname.
I am going to have to agree with what scottie_mac_325 just reported.I have no idea what you are talking about when you refer to "common name".At least for non-Subscription Key users, you provide your Sun Online Account username and password and that is it.Then, if you are trying to reregister a machine that has been rebuilt, that's it - your stuck.
-jtb
> > jtb: thanks for the info.
> >
> > I am not asking about the host id or the host name
> > I am asking about the 'common name' that is provided
> > at the time of registration.
>
> At the time of original registration, no names of any kind are
> 'provided'. All such information is automatically determined and
> sent by the registration 'wizard', and the user has no choice. It
> apparently indentifies the system by its serial number (in the
> case of Sun hardware anyway) and / or hostname.
Scottie and jtb,
I'm a Sun engineer assigned to be the point of contact for this issue.
I'd like to work with both of you to help diagnose this problem and find you a solution.
First, could you give additional information that might help us determine what's different about your systems that causes this problem for you but not other users. Unusual hardware? Anything different happen when you re-installed Solaris?
I need to see the entire basic reg log file from the "updatemanager -debug" run discussed in the previous posting. It has additional info in it that will help me.
You can send the log to prodreg-help@sun.com and I'll be getting back to you.
HardWorker:
> First, could you give additional information that might help us
> determine what's different about your systems that causes this
> problem for you but not other users. Unusual hardware?
> Anything different happen when you re-installed Solaris?
Nothing changed. Same OS (Solaris 10 x86), no new hardware,
same hostname, same IP - everything was duplicated to match my
initial install.In fact, I reinstalled yesterday. When I ran "smpatch
analyze" and "smpatch update", I was able to install a set of 132
patches, which was actually more progress that what I had over
the weekend when "smpatch analyze" was not connecting
(complained about not being able to connect to obtain
detectors or someting?)
At any rate, yesterday I was able to update using "smpatch" and
that first set of patches installed 'updatemanger", but I am still
getting the same error as before when attempting to register.
The "basicreg" log file should be on its way.
Thanks for looking into this.
-jtb
> Scottie and jtb,
>
> I'm a Sun engineer assigned to be the point of
> contact for this issue.
>
> I'd like to work with both of you to help diagnose
> this problem and find you a solution.
>
> First, could you give additional information that
> might help us determine what's different about your
> systems that causes this problem for you but not
> other users. Unusual hardware? Anything different
> happen when you re-installed Solaris?
>
> I need to see the entire basic reg log file from the
> "updatemanager -debug" run discussed in the previous
> posting. It has additional info in it that will help
> me.
>
> You can send the log to prodreg-help@sun.com and I'll
> be getting back to you.
I'm out of town so it will be tomorrow or friday before I email. Nothing unusual about the reinstall, and the hardware is a stock W2100z.
The only difference I know is that the first time no patches had been applied to the system before running update manager. When I reinstalled Solaris 10x64 0305, I applied the recommended patch cluster after install, before running update manager. (Long story, but the update manager is what led me to reinstall, since it's updates left my system reporting various errors. By the way, I wasn't planning on letting it install any updates this time, until I had a better feel for it. I was just going to use it for easy reference.)
Got your log. Thanks a lot!
Now we understand why the registration was rejected as a name collision rather than detected as a redundant registration of the same system. We're still attempting to trace back to the root cause.
We have been unable to reproduce your problem in our lab (yet).
Here are some workarounds:
* Change the host name.
* Create a different user account and register the system to the other user.
Neither are satisfying.... We're still working on it.
> Got your log. Thanks a lot!
>
> Now we understand why the registration was rejected
> as a name collision rather than detected as a
> redundant registration of the same system. We're
> still attempting to trace back to the root cause.
>
> We have been unable to reproduce your problem in our
> lab (yet).
>
> Here are some workarounds:
>* Change the host name.
> * Create a different user account and register the
> the system to the other user.
>
> Neither are satisfying.... We're still working on it.
I've finally had a chance to send mine too now.
-> We have been unable to reproduce your problem in our lab (yet).
Not sure what to say about this. I have rebuilt my machine twice and the problem has occurred after each rebuild.
-> Here are some workarounds:
-> * Change the host name.
Certainly could do this, but would prefer not to.
-> * Create a different user account and register the system to the
-> other user.
I may try this a little later today.
-> Neither are satisfying.... We're still working on it.
Please keep us posted.
-jtb
- Did you reformat or fdisk when you did the re-install?
I am running Solaris 10 (x86) on a W1100z Java Workstation. I used "fdisk" during the original install, but I believe with the rebuilds, since the original "SOLARIS" partition was already defined, I simply selected it as the location for the install.This is a multi-boot system and I didn't want to reformat the entire drive as it would wipe out the other OS that is already installed. Therefore, I guess the answer to your question is "No, I don't believe so".
-jtb
As I also have the same problem (consistently),
I think its
worth adding we do a full re-install that wipes out
all existing data in /, /usr, /var etc. So even if we dont
do reformat or fdisk, we still overwrite all data.
Which results in unable to re-register
for update connection.
Still no fix reported?
Is there possibly any way that Sun can remove the offending system names from their records so that we can properly patch?Is there someone at Sun that we may notify to inform that a system has been rebuilt and can no longer be registered with "updatemanager" due to the "invalid system name/name already in use" error?
Thanks.
-jtb
I was told that the folks at 24-help have been in contact with you. If that's not the case I apologize for leaving you hanging.
We could hack the databases in production to work around your problem, but there are data integrity issues that make it a little risky. We are looking into the best and safest way to fix the root cause of the problem.
We posted the two workarounds. Can those work for you in the short term?
If you are truly stuck, push back on us and we will explore the options.
-- I was told that the folks at 24-help have been in contact with you.
-- If that's not the case I apologize for leaving you hanging.
Other than this forum, I haven't been contacted by anyone, but that is OK - I can probably wait. I just hope that something will be posted here when a proper fix has been developed.
-- We posted the two workarounds. Can those work for you in the
-- short term?
Using a different user account didn't seem to work. I was really hoping I wouldn't have to change the hostname, but I suppose that is what I will do unless a fix is expected within the next few weeks.
-- If you are truly stuck, push back on us and we will explore the
-- options.
I think I can get by. I don't mean to be an annoyance. I just hadn't seen any new posts in awhile and was curious what the status of a fix was.
Thanks.
-jtb
Hi,
I have the exactly same problem as well, I checked my account at update.sun.com, but there is NO registered system under my account. Hence there is nothing could be cleaned up. The system I want to register is a Sol10X86 pure clean installation from scratch based on Vmware WS4.5.2.
PLS Help!!!
Update: the root cause of this has been identified. Sometimes when Solaris is re-installed on x86 systems it is unable to retain the same Host ID. This causes problems when registering again with Update Connection.
A fix for this issue will be included in the next version of Update Connection. Once we have a release date for this we will post it here.
> Update: the root cause of this has been identified. Sometimes
> when Solaris is re-installed on x86 systems it is unable to retain
> the same Host ID. This causes problems when registering again
> with Update Connection.
Does this refer to the Host ID that is displayed by the "hostid"
command?I never compared that value from one build to
the next.
If the "hostid" can not be retained between builds, there may
be other side-effects than just Update Manager. Not to
open another can of worms, but this may be a concern - for
example, what happens with third party software solutions
that may rely on the "hostid" value, such as FlexLM license
managers?This is not a big concern for me personally at
the moment, but there certainly may be other applications
besides Update Manager that rely on "hostid".
> A fix for this issue will be included in the next version of Update
> Connection. Once we have a release date for this we will post it
> here.
Thanks for the update!Looking forward to the fix.
-jtb
