lpphiggp Absent Member.
Absent Member.
11553 views

Cannot resolve nu.novell.com, repositories inaccessible

I've set the system proxy up to use our proxy and to do so without a login; if I set Firefox to "use system proxy", I can get out to anywhere on novell.com fine.
Thus I know the proxy is working.

Let me repeat that.. or just read it again. The proxy is working. I can get to nu.novell.com via a browser, using the system (not separate browser) proxy settings, with no login required.

But I can't (re)register or check repositories, or do updates.
(At one time the server had a public IP and didn't need a proxy, so it has a repository that I can't get to now)

suse_register -a email=<my email> -a regcode-sles=53A22B0743A934 -L /root/.suse_register.log

Returns
[INDENT]
Refreshing service 'nu_novell_com'.
Repository 'SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234' is up to date.
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Problem retrieving the repository index file for service 'nu_novell_com':
Download (curl) error for 'https://nu.novell.com/repo/repoindex.xml?cookies=0&credentials=NCCcredentials':
Error code: Connection failed
Error message: Couldn't resolve host 'nu.novell.com'

Check if the URI is valid and accessible.
Skipping service 'nu_novell_com' because of the above error.
Some of the services have not been refreshed because of an error.
Download (curl) error for 'https://nu.novell.com/repo/$RCE/SLES11-SP2-Core/sle-11-x86_64/repodata/repomd.xml?credentials=NCCcredentials':
Error code: Connection failed
Error message: Couldn't resolve host 'nu.novell.com'

Problem retrieving files from 'SLES11-SP2-Core'.
Download (curl) error for 'https://nu.novell.com/repo/$RCE/SLES11-SP2-Core/sle-11-x86_64/repodata/repomd.xml?credentials=NCCcredentials':
Error code: Connection failed
Error message: Couldn't resolve host 'nu.novell.com'

Please see the above error message for a hint.
Skipping repository 'SLES11-SP2-Core' because of the above error.
Download (curl) error for 'https://nu.novell.com/repo/$RCE/SLES11-SP2-Extension-Store/sle-11-x86_64/repodata/repomd.xml?credentials=NCCcredentials':
Error code: Connection failed
Error message: Couldn't resolve host 'nu.novell.com'

Problem retrieving files from 'SLES11-SP2-Extension-Store'.
Download (curl) error for 'https://nu.novell.com/repo/$RCE/SLES11-SP2-Extension-Store/sle-11-x86_64/repodata/repomd.xml?credentials=NCCcredentials':
Error code: Connection failed
Error message: Couldn't resolve host 'nu.novell.com'[/INDENT]

I get the same sort of thing trying to use zypper to do a refresh.
It resolves nu.novell.com using the browser with system proxy settings.
So.. it seems that curl/zypper/whatever is ignoring the proxy.

zypper does the same:

[INDENT]varan-new-vm:/etc/zypp # zypper sl
# | Alias | Name | Enabled | Refresh | Type
--+--------------------------------------------------+--------------------------------------------------+---------+---------+------
1 | nu_novell_com | nu_novell_com | Yes | Yes | ris
2 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | No | Yes | yast2
3 | SUSE-Linux-Enterprise-Server-11-SP2_11.2.2-1.234 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | Yes | No | yast2
varan-new-vm:/etc/zypp # zypper lp
Refreshing service 'nu_novell_com'.
Problem retrieving the repository index file for service 'nu_novell_com':
Download (curl) error for 'https://nu.novell.com/repo/repoindex.xml?cookies=0&credentials=NCCcredentials':
Error code: Connection failed
Error message: Couldn't resolve host 'nu.novell.com'

Check if the URI is valid and accessible.

[/INDENT]

I'm a loss at this point.
Labels (2)
0 Likes
12 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Cannot resolve nu.novell.com, repositories inaccessible

On Fri, 13 Sep 2013 20:06:02 +0000, lpphiggp wrote:

> I've set the system proxy up to use our proxy and to do so without a
> login; if I set Firefox to "use system proxy", I can get out to
> anywhere on novell.com fine.
> Thus I know the proxy is working.


What kind of proxy? Is this just http(s) traffic? Or does it handle DNS
as well?


> Error message: Couldn't resolve host 'nu.novell.com'


So what happens if you "nslookup nu.novell.com" on this server?



--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.

0 Likes
lpphiggp Absent Member.
Absent Member.

Re: Cannot resolve nu.novell.com, repositories inaccessible

David Gersic;2282287 wrote:


What kind of proxy? Is this just http(s) traffic? Or does it handle DNS
as well?


The proxy handles DNS requests for http traffic, but not DNS in and of itself.

>> Error message: Couldn't resolve host 'nu.novell.com

So what happens if you "nslookup nu.novell.com" on this server?


It fails because the server has a private IP; (thus the absolute need for a proxy).
I have several other servers that also have private IPs, that use this proxy, and they're working fine with zypper (and they also can't resolve nu.novell.com via nslookup)

It seems like zypper or curl just isn't using the proxy, which is weird, because it's set right in the /etc/zypp/services.d/nu_novell_com.services file.
If I use Firefox to test (using the system proxy, not explicitly set) that gets to nu.novell.com fine too, albeit with the 403 error as expected.
But it's resolving, using the system proxy settings.


It's a real head scratcher.





--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.
0 Likes
lpphiggp Absent Member.
Absent Member.

Re: Cannot resolve nu.novell.com, repositories inaccessible

David Gersic;2282287 wrote:


What kind of proxy? Is this just http(s) traffic? Or does it handle DNS
as well?


The proxy handles DNS requests for http traffic, but not DNS in and of itself.

>> Error message: Couldn't resolve host 'nu.novell.com

So what happens if you "nslookup nu.novell.com" on this server?


It fails because the server has a private IP; (thus the absolute need for a proxy).
I have several other servers that also have private IPs, that use this proxy, and they're working fine with zypper (and they also can't resolve nu.novell.com via nslookup)

It seems like zypper or curl just isn't using the proxy, which is weird, because it's set right in the /etc/zypp/services.d/nu_novell_com.services file.
If I use Firefox to test (using the system proxy, not explicitly set) that gets to nu.novell.com fine too, albeit with the 403 error as expected.
But it's resolving, using the system proxy settings.


It's a real head scratcher.





--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot resolve nu.novell.com, repositories inaccessible

On Mon, 16 Sep 2013 16:06:03 +0000, lpphiggp wrote:

> David Gersic;2282287 Wrote:
>> So what happens if you "nslookup nu.novell.com" on this server?

>
> It fails because the server has a private IP; (thus the absolute need
> for a proxy).
> I have several other servers that also have private IPs, that use this
> proxy, and they're working fine with zypper (and they also can't resolve
> nu.novell.com via nslookup)


Weird. So it seems like it should work, since you have others that do.
What's different on the working ones vs. this one that doesn't? Were they
installed differently or something like that?


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.

0 Likes
lpphiggp Absent Member.
Absent Member.

Re: Cannot resolve nu.novell.com, repositories inaccessible

A different admin installed this one, but I don't know what he could've done so differently as to break this.

The funny thing, if I use the settings under the subdirectories of /etc/zypp/, I can actually access the rpms on nu.novel.com using Firefox w/ system proxy settings.. I login with the credentials and have no problem getting there.
So... the proxy works, it's just that zypper isn't passing it to curl or curl isn't using it.. or however that works, I'm really not sure.

I wonder if I could try uninstalling and reinstalling curl and zypper..? Or might that be a colossally bad idea..?
0 Likes
lpphiggp Absent Member.
Absent Member.

Re: Cannot resolve nu.novell.com, repositories inaccessible

Actually I just determined that curl is working fine (and so is our proxy)

curl -v https://www-secure.novell.com/home returns no error, it resolves and connects.

curl -v https://nu.novell.com/repo/$RCE/SLES11-SP2-Core/sle-11-x86_64/repodata/

also resolves and has some results.. (not a full connection of course, I didn't login, but I get there, which is the point)

I tried again with the full URL that a "zypper ref" tries:
curl -v https://nu.novell.com/repo/$RCE/SLES11-SP2-Core/sle-11-x86_64/repodata/repomd.xml?credentials=NCCcredentials

That connected but didn't get any further.. just curious what I'd get. (got a 404 error)

This gets curiouser and curiouser.. someone give me the blue pill, I want out of the rabbit hole! lol
0 Likes
Knowledge Partner
Knowledge Partner

Re: Cannot resolve nu.novell.com, repositories inaccessible

lpphiggp;2282981 wrote:
Actually I just determined that curl is working fine (and so is our proxy)

curl -v https://www-secure.novell.com/home returns no error, it resolves and connects.

curl -v https://nu.novell.com/repo/$RCE/SLES11-SP2-Core/sle-11-x86_64/repodata/

also resolves and has some results.. (not a full connection of course, I didn't login, but I get there, which is the point)

I tried again with the full URL that a "zypper ref" tries:
curl -v https://nu.novell.com/repo/$RCE/SLES11-SP2-Core/sle-11-x86_64/repodata/repomd.xml?credentials=NCCcredentials

That connected but didn't get any further.. just curious what I'd get. (got a 404 error)

This gets curiouser and curiouser.. someone give me the blue pill, I want out of the rabbit hole! lol


Hi
You need to escape the $;

curl -v https://nu.novell.com/repo/\$RCE/SLES11-SP2-Core/sle-11-x86_64/repodata/repomd.xml?credentials=NCCcredentials
--
Cheers Malcolm °¿° SUSE Knowledge Partner
SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
If you appreciate what I've posted, click the LIKE button below. If this
solves your problem, please click the ACCEPT AS SOLUTION button.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Cannot resolve nu.novell.com, repositories inaccessible

On Wed, 18 Sep 2013 14:26:02 +0000, lpphiggp wrote:

> I wonder if I could try uninstalling and reinstalling curl and zypper..?
> Or might that be a colossally bad idea..?


I'm guessing that would be a bad idea. I'm out of good ideas on this,
though. I've asked around to see if anybody else can chime in.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.

0 Likes
lpphiggp Absent Member.
Absent Member.

Re: Cannot resolve nu.novell.com, repositories inaccessible

malcolmlewis;2282990 wrote:
Hi
You need to escape the $;

curl -v https://nu.novell.com/repo/\$RCE/SLES11-SP2-Core/sle-11-x86_64/repodata/repomd.xml?credentials=NCCcredentials


That might help my example but it's not really the point... I'm not supposed to manually run curl to do updates.. unless you are saying there's a typo in the zypper script?
Because that's where I got this URL from, the sdout error that zypper returns when I try to do a refresh.

The point of the above was, that nu.novell.com resolved .. It got to the server, otherwise I would not have even seen it's 404 error.

The question is, why does it suddenly fail to resolve when I try to do updates via zypper or even yast?

Perhaps I should post my actual errors here..
0 Likes
lpphiggp Absent Member.
Absent Member.

Re: Cannot resolve nu.novell.com, repositories inaccessible

Okay, update..
I think I need to quit IT and commit myself to a mental asylum, because no one will believe this.

I wanted to copy and paste the "zypper ref" error here to the forum, which I'm viewing on my Windows box.
However I've been using my linux box, via normal Open-SSH, to work on this problem server (hostname = Varan)

So, on my win box I fired up puTTY and SSH'd into Varan, and ran the same command so as to copy this error.

...aaaaaand ... no error.
It worked. It worked?

Tried from my linux box again, failure.
Tried again from Win/puTTy, success.

What?

How does this even matter? And even if, somehow, SSH on my linux box were trying to reroute DNS requests through itself, (which I doubt) it would work because it has a public IP. I don't need a proxy on that.


See.. I said no one would believe me. I hear The Meadows (PA) is lovely this time of year.
0 Likes
lpphiggp Absent Member.
Absent Member.

Re: Cannot resolve nu.novell.com, repositories inaccessible

Not knowing what else to do, I logged out of all my open SSH sessions on the linux box and rebooted it.

ssh'd into Varan again (ssh varan -X -l root)
Ran zypper ref
Got better results, but a curious error halfway through this time:


varan-new-vm:~ # zypper ref
Repository 'SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234' is up to date.
Repository 'SLES11-SP1-Pool' is up to date.
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 20 (X_GetProperty)
Resource id in failed request: 0x1e03f55
Serial number of failed request: 608
Current serial number in output stream: 608


I ran the command once again, this time, I got normal, full results.

zypper lp works too now.

Seems resolved whatever it was.
Google seems to suggest that error is due to a bug, so I'll go see if there're any new updates for my workstation.
0 Likes
dlshospitality Absent Member.
Absent Member.

Re: Cannot resolve nu.novell.com, repositories inaccessible

lpphiggp;2282280 wrote:
I've set the system proxy up to use our proxy and to do so without a login; if I set Firefox to "use system proxy", I can get out to anywhere on novell.com fine.
Thus I know the proxy is working.

Let me repeat that.. or just read it again. The proxy is working. I can get to nu.novell.com via a browser, using the system (not separate browser) proxy settings, with no login required.

But I can't (re)register or check repositories, or do updates.
(At one time the server had a public IP and didn't need a proxy, so it has a repository that I can't get to now)

suse_register -a email=<my email> -a regcode-sles=53A22B0743A934 -L /root/.suse_register.log

Returns
[INDENT]
Refreshing service 'nu_novell_com'.
Repository 'SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234' is up to date.
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Abort, retry, ignore? [a/r/i/?] (a): a
Problem retrieving the repository index file for service 'nu_novell_com':
Download (curl) error for 'https://nu.novell.com/repo/repoindex.xml?cookies=0&credentials=NCCcredentials':
Error code: Connection failed
Error message: Couldn't resolve host 'nu.novell.com'

Check if the URI is valid and accessible.
Skipping service 'nu_novell_com' because of the above error.
Some of the services have not been refreshed because of an error.
Download (curl) error for 'https://nu.novell.com/repo/$RCE/SLES11-SP2-Core/sle-11-x86_64/repodata/repomd.xml?credentials=NCCcredentials':
Error code: Connection failed
Error message: Couldn't resolve host 'nu.novell.com'

Problem retrieving files from 'SLES11-SP2-Core'.
Download (curl) error for 'https://nu.novell.com/repo/$RCE/SLES11-SP2-Core/sle-11-x86_64/repodata/repomd.xml?credentials=NCCcredentials':
Error code: Connection failed
Error message: Couldn't resolve host 'nu.novell.com'

Please see the above error message for a hint.
Skipping repository 'SLES11-SP2-Core' because of the above error.
Download (curl) error for 'https://nu.novell.com/repo/$RCE/SLES11-SP2-Extension-Store/sle-11-x86_64/repodata/repomd.xml?credentials=NCCcredentials':
Error code: Connection failed
Error message: Couldn't resolve host 'nu.novell.com'

Problem retrieving files from 'SLES11-SP2-Extension-Store'.
Download (curl) error for 'https://nu.novell.com/repo/$RCE/SLES11-SP2-Extension-Store/sle-11-x86_64/repodata/repomd.xml?credentials=NCCcredentials':
Error code: Connection failed
Error message: Couldn't resolve host 'nu.novell.com'[/INDENT]

I get the same sort of thing trying to use zypper to do a refresh.
It resolves nu.novell.com using the browser with system proxy settings.
So.. it seems that curl/zypper/whatever is ignoring the proxy.

zypper does the same:

[INDENT]varan-new-vm:/etc/zypp # zypper sl
# | Alias | Name | Enabled | Refresh | Type
--+--------------------------------------------------+--------------------------------------------------+---------+---------+------
1 | nu_novell_com | nu_novell_com | Yes | Yes | ris
2 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | No | Yes | yast2
3 | SUSE-Linux-Enterprise-Server-11-SP2_11.2.2-1.234 | SUSE-Linux-Enterprise-Server-11-SP2 11.2.2-1.234 | Yes | No | yast2
varan-new-vm:/etc/zypp # zypper lp
Refreshing service 'nu_novell_com'.
Problem retrieving the repository index file for service 'nu_novell_com':
Download (curl) error for 'https://nu.novell.com/repo/repoindex.xml?cookies=0&credentials=NCCcredentials':
Error code: Connection failed
Error message: Couldn't resolve host 'nu.novell.com'

Check if the URI is valid and accessible.

[/INDENT]

I'm a loss at this point.


had similar issue, this did help me yesterday:
/etc/zypp/services.d
edit nu_novell_com.service and add your proxy in line url = https://nu.novell.com/?credentials=NCCcredentials&proxy=http://YourProxy
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.