isRegistred command give unknown message and updates

SUSE Manager
1

To whom it may concern

I manually registered our SUSE Manager Server with the suse_register command to nu.novell.com.When I run the command isRegistred I am getting the following message.

The system is registered against nu.novell.com
Product status:

  • SUSE-Manager-Server-2.1-x86_64 : unknown

Is this correct ? Will my SUSE Manager server get all the updates from nu.novell.com ? Why not from https://scc.suse.com ?

If I run the command zypper update on my SUSE Manager server, I get the following message :

Loading repository data…
Reading installed packages…

Nothing to do.

Where and what repositories do I need to add in YAST, to update my SUSE Manager server ?

2

Hi plaubscher,

have you switched SuMa to SCC yet?

Regards,
Jens

3

Jens

When I run the command mgr-ncc-sync enable scc to switch to SCC ( If this is how you do it ) I receive the following error.

Updating Channel Family Information
Downloading Product information…
SUSE Manager 11390 2016/03/17 15:41:32 +02:00: (‘transfer closed with outstanding read data remaining’,)
NCC connection failed.

I can do a nslookup to scc.suse.com.

What procedure do I need to follow ?

4

Hi plaubscher,

When I run the command mgr-ncc-sync enable scc to switch to SCC ( If this is how you do it )

the documentation (https://www.suse.com/documentation/suse_manager/book_susemanager_user/data/s1-sm-scc.html or https://www.suse.com/documentation/suse_manager/singlehtml/book_susemanager_user/book_susemanager_user.html#s2-sm-scc-inst) describes a slightly different path :wink:

It may well be that all these ways lead to the same error, in which case I’d recommend to open a service request with SUSE.

Regards,
Jens

5

Hi plaubscher,

the preferred method for registration is yast.

If you want to use the suse_register command line tool, see https://www.novell.com/support/kb/doc.php?id=3030847 for help with running suse_register.
Since SUSE Manager 2.1 is based on SLES 11 SP3, its initial registration is against nu.novell.com. Only from SLES 12 onwards, the registration is handled by scc.suse.com.

Be careful to use “-a regcode-sms=…” instead of “-a regcode-sles=…” if you want to use a SUSE Manager 2.1 registration code.

Hth,
Klaus

6

Thanks for the feedback.At least my subscriptions started to download now.When running the mgr-ncc-sync refresh command.I can’t see anything on the Web Interface, to do the migration to SCC, only that the repo channels is scheduled to run.Must I wait until it continue to run ?

mgr-ncc-sync refresh
Updating Channel Family Information
Downloading Product information…
Found 670 products using 3 mirror credentials.
Downloading Subscription information…
Found 156 subscriptions using 3 mirror credentials.
Updating Upgrade Path Information
Scheduling repo sync for all installed channels…
Scheduling repo sync for all installed channels…
Scheduled repo sync for channel sles10-sp3-pool-i586.
Scheduled repo sync for channel sles10-sp3-updates-i586.
Scheduled repo sync for channel sle10-sp4-suse-manager-tools-i586.
Scheduled repo sync for channel sle10-sp3-suse-manager-tools-i586.
Scheduled repo sync for channel sle10-sdk-sp3-updates-i586.
Scheduled repo sync for channel sle10-sdk-sp3-pool-i586.
Scheduled repo sync for channel sles10-sp3-pool-x86_64.
Scheduled repo sync for channel sle10-sp4-suse-manager-tools-x86_64.
Scheduled repo sync for channel sle10-sp3-suse-manager-tools-x86_64.
Scheduled repo sync for channel sles10-sp3-updates-x86_64.
Scheduled repo sync for channel sle10-sdk-sp3-pool-x86_64.
Scheduled repo sync for channel sle10-sdk-sp3-updates-x86_64.
Scheduled repo sync for channel sles10-sp4-pool-i586.
Scheduled repo sync for channel sles10-sp4-updates-i586.
Scheduled repo sync for channel sle10-sdk-sp4-updates-i586.
Scheduled repo sync for channel sle10-sdk-sp4-pool-i586.
Scheduled repo sync for channel sles10-sp4-pool-x86_64.
Scheduled repo sync for channel sles10-sp4-updates-x86_64.
Scheduled repo sync for channel sle10-sdk-sp4-pool-x86_64.
Scheduled repo sync for channel sle10-sdk-sp4-updates-x86_64.
Scheduled repo sync for channel sles11-sp1-pool-i586.
Scheduled repo sync for channel sles11-sp1-suse-manager-tools-i586.
Scheduled repo sync for channel sles11-sp1-updates-i586.
Scheduled repo sync for channel sle11-sdk-sp1-pool-i586.
Scheduled repo sync for channel sle11-sdk-sp1-updates-i586.
Scheduled repo sync for channel sles11-sp1-pool-x86_64.
Scheduled repo sync for channel sles11-sp1-suse-manager-tools-x86_64.
Scheduled repo sync for channel sles11-sp1-updates-x86_64.
Scheduled repo sync for channel oes11-pool-x86_64.
Scheduled repo sync for channel oes11-updates-x86_64.
Scheduled repo sync for channel sle11-sdk-sp1-pool-x86_64.
Scheduled repo sync for channel sle11-sdk-sp1-updates-x86_64.
Scheduled repo sync for channel sles11-sp2-core-i586.
Scheduled repo sync for channel sles11-sp2-extension-store-i586.
Scheduled repo sync for channel sles11-sp2-suse-manager-tools-i586.
Scheduled repo sync for channel sles11-sp2-updates-i586.
Scheduled repo sync for channel sle11-sdk-sp2-updates-i586.
Scheduled repo sync for channel sle11-sdk-sp2-core-i586.
Scheduled repo sync for channel sle11-smt-sp2-pool-i586.
Scheduled repo sync for channel sle11-smt-sp2-updates-i586.
Scheduled repo sync for channel sle11-smt-updates-i586.
Scheduled repo sync for channel sle11-sp2-webyast-1.3-updates-i586.
Scheduled repo sync for channel sle11-sp2-webyast-1.3-pool-i586.
Scheduled repo sync for channel sles11-sp2-extension-store-x86_64.
Scheduled repo sync for channel sles11-sp2-core-x86_64.
Scheduled repo sync for channel sles11-sp2-suse-manager-tools-x86_64.
Scheduled repo sync for channel sles11-sp2-updates-x86_64.
Scheduled repo sync for channel oes11-sp1-pool-x86_64.
Scheduled repo sync for channel oes11-sp1-updates-x86_64.
Scheduled repo sync for channel sle11-sdk-sp2-updates-x86_64.
Scheduled repo sync for channel sle11-sdk-sp2-core-x86_64.
Scheduled repo sync for channel sle11-smt-sp2-updates-x86_64.
Scheduled repo sync for channel sle11-smt-sp2-pool-x86_64.
Scheduled repo sync for channel sle11-smt-updates-x86_64.
Scheduled repo sync for channel sle11-sp2-webyast-1.3-updates-x86_64.
Scheduled repo sync for channel sle11-sp2-webyast-1.3-pool-x86_64.
Scheduled repo sync for channel sles11-sp3-pool-i586.
Scheduled repo sync for channel sles11-sp3-suse-manager-tools-i586.
Scheduled repo sync for channel sles11-sp3-updates-i586.
Scheduled repo sync for channel sle11-sdk-sp3-updates-i586.
Scheduled repo sync for channel sle11-sdk-sp3-pool-i586.
Scheduled repo sync for channel sle11-smt-sp3-updates-i586.
Scheduled repo sync for channel sle11-smt-sp3-pool-i586.
Scheduled repo sync for channel sles11-sp3-pool-x86_64-server-2.1.
Scheduled repo sync for channel sles11-sp3-pool-x86_64.
Scheduled repo sync for channel sles11-sp3-updates-x86_64-server-2.1.
Scheduled repo sync for channel sles11-sp3-updates-x86_64.
Scheduled repo sync for channel sles11-sp3-suse-manager-tools-x86_64.
Scheduled repo sync for channel oes11-sp2-updates-x86_64.
Scheduled repo sync for channel oes11-sp2-pool-x86_64.
Scheduled repo sync for channel sle11-sdk-sp3-updates-x86_64.
Scheduled repo sync for channel sle11-sdk-sp3-pool-x86_64.
Scheduled repo sync for channel sle11-smt-sp3-pool-x86_64.
Scheduled repo sync for channel sle11-smt-sp3-updates-x86_64.
Scheduled repo sync for channel suse-manager-server-2.1-pool-x86_64.
Scheduled repo sync for channel suse-manager-server-2.1-updates-x86_64.

7

Wow, thats A LOT of repositories. This will take days to sync. Just be patient.

SUSE Manager 2.1 has a ‘setup wizard’ under the ‘Admin’ tab. There you can select products and see their sync progress.

If this is a new Manager 2.1 installation, I wonder how you got access to “mgr-ncc-sync” ? If you followed the installation instructions and fully updated your Manager, “yast2 susemanager_setup” would have you migrated to SCC and removed “mgr-ncc-sync”.

8

Sorry for only replying now.We had Easter holidays in our country.Yes this is a new Manager 2.1 installation.Since 23 March 2016 there was no changes with our channels and the space in use, also stayed the same.I did manage to login to the NCC Settings with our NCC username and password with the new installation.What is weird is that I know, that this server never had a update before.On my test server it did the update 100%.Do I need to worry ? or can I continue with the clients ?

9

SUSE Manager runs fine with NCC and SCC, no need to worry. However, only SCC will give you SLE 12 channels.

However, if seems as if your SUSE Manager Server isn’t correctly registered and did not get all patches. Please look at https://download.suse.com/patch/finder/ (select correct product and version) and verify that all listed patches are applied.

See the release notes at https://www.suse.com/releasenotes/x86_64/SUSE-MANAGER/2.1/ and the documentation on how to migrate from NCC to SCC.

10

It seems that my ‘/etc/suseRegister.conf’ has been edited, as it was pointing to the wrong location.
I fixed it, it should read :

url = https://secure-www.novell.com/center/regsvc/
listParams = command=listparams
register = command=register
listProducts = command=listproducts
#hostGUID = 122354

My SUSEManager server is now patched, and thus my problem is solved.