repositories and/or updates mangled!

SUSE Linux Enterprise Server SLES Updates
1

Hi,
Recently installed SLES 11.3 server, was working well, then suffered drive failure in array.
Backed up, drive(s) replaced, system fully re-installed and then restored from backup.

Everything works, except updates (as far as i can tell so far anyway)

The first error i was getting was “unsupported protocol https”. when running the update-on-demand So having removed all the repositories, and then re-added the DVD I now get the following…
If i run the Yast-Online update. I get “No update repository configured yet, run configuration workflow now?”
If i select Yes and end up in “Novell customer centre configuration” hitting NEXT, gives “ERROR Unsupported protocol (1)”
checking my registration status that comes up as “config successful” and has the right dates in it etc??

If i go to updates via yast - online update configuration - it says “Current update repository (none)” if i choose “config repositories” the dvd is in the list and it’s enabled? If i choose the “register for support & get the repository” I just get the same as i did above - same error, same “your registration is ok”?

I’m just going round & round in circles on this.
please someone come up with something before i have to wipe the box & start over. maybe if i could ‘un-register’ the box and then re-register it? if that’s possible?

Cheers,

Carl.

ps - I’m relatively new to SLES so go easy pls :slight_smile:

2

Hi
Yes there have been some issues with the online repositories, you can delete and re-register the system, it should then add the repositories back.

3

hi

i tried the re-registering bit, but not the deleting.
presumably your referring to something clever like deleting some registration files from location-currently-unknown, as opposed to wiping the box & starting over…
i did try googling that but couldn’t find an exact match.
pointers appreciated!

cheers

c

4

Hi
No, I meant delete on the Novell Customer Center, log in there and
delete the system. Then re-register.

You can also try the -r option with the command line
version called suse_register to restore the repositories.

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.10-7-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

5

[QUOTE=malcolmlewis;19200]Hi
No, I meant delete on the Novell Customer Center, log in there and
delete the system. Then re-register.

You can also try the -r option with the command line
version called suse_register to restore the repositories.

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.10-7-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks![/QUOTE]

Aha, I see. or at least i thought i did!

I haven’t registered the system at the NCC. all my interactions so far have been through buy.suse.com
Now having logged in to NCC appears that I don’t have any products!
so I just tried to add the one i’ve got and i get “subscriptions.addSubscriptionError” ???
This just gets better & better!

/Edit
Additionaly just tried suse_register -r and also --erase-local-regdata and both return “ERROR: Unsupported protocol: (1)”
If i just knew what the error msg meant it would be a start!
/

Cheers,
Carl.

6

Hi
If you register the system via YaST and add your subscription number
(which you would have got when it was purchased), then it should add
fine?

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.10-7-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

7

Hi Malcolm,

Yes, I have registered it via yast. then as i said at the beginning of the thread, i had restore the whole machine from a backup, that’s when i noticed the update/repository/registration issues
Now when i try to update i get a message “no valid repositorys”
which sends you to the registration thing.
pressing the button “registration status” says “registration successful” and the details button says it was registered 2-12-13 and subscription active (full version)
Attempting to register it produces the error(s) listed previously
Since my last post I have now got the system successfully registered at NCC. But the local problem remains.

I believe that the box is in a ‘half-registered’ state somehow, and it’s probably best to un-register it (forcefully if necessary) and then try to register it again then. unfortunately, i know not how to go in & rip out it’s registration details without, as i said, just wiping the box and starting over. But as everything else appears fine, and it’s in production now, i’m reluctant to take that course unless there are no others!

Cheers,
Carl.

8

Additional,
I’ve been here - http://www.novell.com/support/kb/doc.php?id=3303599 and done that
it works up to step 4,
step 5 gives the same error as before “ERROR: Unsupported protocol: (1)”

/C

9

Hi
So if you look at the log file, does it provide extra info?

less /root/.suse_register.log

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.10-7-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

10

Yup, not sure it’s going to be much help though…

/----- Mon Feb 24 11:53:09 2014 ---------------------------------------
2014-02-24 11:53:10 SUSE::SRPrivate - [info] SEND DATA to URI: https://secure-www.novell.com/center/regsvc/?command=listproducts&lang=$
2014-02-24 11:53:10 SUSE::SRPrivate - [error] ERROR: Unsupported protocol: (1)
2014-02-24 11:53:10 SUSE::SRPrivate - [error] (2)
/

11

Hi
I’ve asked my SUSE contacts if there is something going on, but you may
need to raise an SR, will post back with more details.

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.10-7-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

12

Not sure if this will help, but i did a ‘supportconfig’ and then looked in the file ‘updates.txt’, here is what i think is the ‘long version’ of the previous log entry you asked for…

Feb 24 11:47:44 Bender suse_register[16442]: Installed Products Dump: $VAR1 = [ [ 'SUSE_SLES', '11.3', '', 'x86_64' ] ]; Feb 24 11:47:46 Bender suse_register[16442]: Commandline params: no-optional:0 forceregistration:0 no-hw-data:0 batch:0 Feb 24 11:47:46 Bender suse_register[16442]: Argument Dump: $VAR1 = { 'timezone' => { 'kind' => 'mandatory', 'value' => 'Europe/London', 'flag' => 'i', 'description' => 'Timezone' }, 'ostarget' => { 'kind' => 'mandatory', 'value' => 'sle-11-x86_64', 'flag' => 'i', 'description' => 'Target operating system identifier' }, 'processor' => { 'kind' => 'mandatory', 'value' => 'x86_64', 'flag' => 'i', 'description' => 'Processor type' }, 'platform' => { 'kind' => 'mandatory', 'value' => 'x86_64', 'flag' => 'i', 'description' => 'Hardware platform type' } }; Feb 24 11:47:46 Bender suse_register[16442]: Products Dump: $VAR1 = []; Feb 24 11:47:46 Bender suse_register[16442]: ERROR: Unsupported protocol: (1) (2)

13

[QUOTE=malcolmlewis;19512]Hi
I’ve asked my SUSE contacts if there is something going on, but you may
need to raise an SR, will post back with more details.
![/QUOTE]

OK Cheers,
Carl.

14

Hi
So the suggestion back are;

1 - Refreshing existing registration:

suse_register -L /root/.suse_register.log

2 - Re-enable repositories for an existing registration :

suse_register -r

3 - Alternatively, he could also completely clear out the registration
as per TID 3303599 and manually re-register perhaps using a debug
option as this:

suse_register -d 3 -a email=<email_adress> -a regcode-sles=<sles_reg_code> >/tmp/suse-register.txt

If things go wrong again, he can log an SR and provide the /tmp/suse-register.txt output gathered above.

Also, just to re-confirm, there is no proxy involved?

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.10-7-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

15

OK, now i think were getting somewhere. I had done the above before, but didn’t know how to get the debug txt file out of it.

It would appear my issues are with something called cURL…

Protocol https not supported or disabled in libcurl Closing connection -1

And this is the point i think i have to admit to probably being the cause!
I was asked to install something called “Madeline 2.0 PDE” http://eyegene.ophthy.med.umich.edu/madeline/install.php
Which i now see messes with OpenSSL & libCurl.
I was just following the instructions in that link, didn’t think it would affect things they way it (probably) has.

Thanks for your help Malcolm, without knowing where to look i would still be scratching my head i think, but it looks like i need to change the title of this thread to “I messed up my SSL somehow - help!”

Cheers
Carl.

16

Hi
Glad you have identified the issue, just start a new thread with the
details and title :wink:

–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE 13.1 (Bottle) (x86_64) GNOME 3.10.2 Kernel 3.11.10-7-desktop
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!