Highlighted
Absent Member.
Absent Member.
3823 views

OES2 Updates : Beyond FRUSTRATED

Hi:

So during an SLES10/OES2 setup, there was a DNS problem and the registration failed. So I did it later. I've done this before so I wasn't too concerned about it.

However, if you do a rug sl, you see https://nu.novell.com is inactive. I've done tid # 3818394, 3303599 and 3150078 (which have worked for me in the past under similar circumstances). My other servers are all ok.

What I'm left with is that when you do a rug --quiet sa --ignore-failure -t nu https://nu.novell.com (which is part of tid # 3150078), it comes back and says "ERROR: Could not add 'https://nu.novell.com': Failed to download XML metadata: Download failed: (https://nu.novell.com/repo/repoindex.xml) The remote server returned an error: (401) Unauthorized. However, my SLES updates are working just fine 🙂 It's the OES2 updates that won't come down.

Pray tell...does anyone know what stupidness might be causing this? Or am I just going to have to haul the server out of the tree and start again?

Thanks in advance!
Labels (2)
0 Likes
2 Replies
Highlighted
Absent Member.
Absent Member.

pattercw;1597806 wrote:
Hi:

So during an SLES10/OES2 setup, there was a DNS problem and the registration failed. So I did it later. I've done this before so I wasn't too concerned about it.

However, if you do a rug sl, you see https://nu.novell.com is inactive. I've done tid # 3818394, 3303599 and 3150078 (which have worked for me in the past under similar circumstances). My other servers are all ok.

What I'm left with is that when you do a rug --quiet sa --ignore-failure -t nu https://nu.novell.com (which is part of tid # 3150078), it comes back and says "ERROR: Could not add 'https://nu.novell.com': Failed to download XML metadata: Download failed: (https://nu.novell.com/repo/repoindex.xml) The remote server returned an error: (401) Unauthorized. However, my SLES updates are working just fine 🙂 It's the OES2 updates that won't come down.

Pray tell...does anyone know what stupidness might be causing this? Or am I just going to have to haul the server out of the tree and start again?

Thanks in advance!


I had a similar problem here. Nothing (at all) would fix it. The problem was that our MLA expired on 12-31. It was extended to 1-31 while it was renegotiated. The contract was finished before 1-31, however whatever got extended so that my reg codes would keep working wasn't changed. So I could no longer register new servers, and all of my old servers stopped getting updates from Novell. (The ones I had pointing at my internal Zenworks box kept working). On the ones that broke I would get the 401 errors.

Long story short, I got issued new reg codes for all my SuSE products. One of the engineers from Novell dialed in and fixed all my old servers that had gotten broken. They basically did the same steps as described in the TIDs you mentioned. I wrote a small batch script that would do basically the same thing they were doing. This is what it looks like (with the passwords, etc munged)


rczmd stop

(Note: Take a look to ensure zmd actually stopped. If not, kill it with -9)

rm /var/lib/zmd/*

cd /var/cache/zmd/web

rm -rf *

rm /etc/zmd/deviceid
rm /etc/zmd/secret

suse_register -a regcode-sles=711F9A56 -a email=sam@here.com
suse_register -a regcode-oes=6BE472C8 -a email=sam@here.com

rczmd start

rug --quiet sa --ignore-failure -t nu https://nu.novell.com

rug sub SLES10-SP1-Updates

rug sub OES2-Updates

rug ref

rug up -t patch SLES10-SP1-Updates

rug up -t patch OES2-Updates


This generally worked for me (again, after I got new registration codes.)

Hope it helps you, but it sounds like you've already done most if not all of this.

Sam

Highlighted
Absent Member.
Absent Member.

Yup, you're absolutely right...that's precisely what happened. The codes expired (even though it was my understanding they weren't supposed to at that time).

Anyway our Corporate IT Operations department got new codes the next day and I was fine after that.

Thanks for the response!

Chuck
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.