Couldn't resolve host 'ec2-a6369ea5-36b976fb.susecloud.net'

[comptont]

Amazon EC2 instance . . .
All of my zypper commands seem to fail with 'Couldn’t resolve host ‘ec2-a6369ea5-36b976fb.susecloud.net’

How to fix?

[Willem1]

[QUOTE=comptont;25280]Amazon EC2 instance . . .
All of my zypper commands seem to fail with 'Couldn’t resolve host ‘ec2-a6369ea5-36b976fb.susecloud.net’

How to fix?[/QUOTE]

Hi,

Do you have the exact output error zypper is reporting? I assume you can resolve other DNS names properly?

I don’t use EC2 instances, but I suspect that you need to re-register that failing repository.

Doing a quick search on EC2 and SUSE I came across this article that might be related: https://www.suse.com/communities/conversations/suse-linux-enterprise-server-aws-updates-shellshock/

Mainly this bit:

1.) wget http://ec2-54-197-240-216.compute-1.amazonaws.com/instanceInfraUpgrade.noarch.rpm
2.) zypper –non-interactive in instanceInfraUpgrade.noarch.rpm
3.) instanceInfraUpgrade

In summary:

In order to get the bash fixes, instances need to use the new EC2 update infrastructure provided by SUSE. This is accomplished using the procedure above on running instances. Instances started after Saturday September 27, 2:00 P.M. EDT already have the shellshock fixes integrated and also use the new infrastructure.

But again, I don’t have experiences on the EC2 platform.

Cheers,
Willem

[comptont]

[QUOTE=Magic31;25290]Hi,

Do you have the exact output error zypper is reporting? I assume you can resolve other DNS names properly?

I don’t use EC2 instances, but I suspect that you need to re-register that failing repository.

Doing a quick search on EC2 and SUSE I came across this article that might be related: https://www.suse.com/communities/conversations/suse-linux-enterprise-server-aws-updates-shellshock/

Mainly this bit:

But again, I don’t have experiences on the EC2 platform.

Cheers,
Willem[/QUOTE]

Thanks for your comment.

Yes, the server resolves other domain names. The domain resloves when requested outside the server.

I tried what you suggested above, but the “zypper –non-interactive in instanceInfraUpgrade.noarch.rpm” still fails to resolve the domain name.

zypper in instanceInfraUpgrade.noarch.rpm
Refreshing service ‘susecloud’.
Problem retrieving the repository index file for service ‘susecloud’:
Download (curl) error for ‘http://us-west-2-ec2-update.susecloud.net/repo/repoindex.xml?cookies=0’:
Error code: Connection failed
Error message: Couldn’t resolve host ‘ec2-a6369ea5-36b976fb.susecloud.net’

Check if the URI is valid and accessible.
Download (curl) error for ‘http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP3-Pool/sle-11-i586/repodata/repomd.xml’:
Error code: Connection failed
Error message: Couldn’t resolve host ‘ec2-a6369ea5-36b976fb.susecloud.net’

Abort, retry, ignore? [a/r/i/? shows all options] (a):

[Willem1]

[QUOTE=comptont;25291]…
zypper in instanceInfraUpgrade.noarch.rpm
Refreshing service ‘susecloud’.
Problem retrieving the repository index file for service ‘susecloud’:
Download (curl) error for ‘http://us-west-2-ec2-update.susecloud.net/repo/repoindex.xml?cookies=0’:
Error code: Connection failed
Error message: Couldn’t resolve host ‘ec2-a6369ea5-36b976fb.susecloud.net’

Check if the URI is valid and accessible.
Download (curl) error for ‘http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP3-Pool/sle-11-i586/repodata/repomd.xml’:
Error code: Connection failed
Error message: Couldn’t resolve host ‘ec2-a6369ea5-36b976fb.susecloud.net’

Abort, retry, ignore? [a/r/i/? shows all options] (a):[/QUOTE]

Ok…

It would be good to know the repositories that you have available on that machine. Maybe the one giving the issue can simply be disabled.

What’s the output of :

zypper ls
zypper ca

-Willem

[comptont]

The server can resolve the IP address:
host us-west-2-ec2-update.susecloud.net
us-west-2-ec2-update.susecloud.net is an alias for update-1549120573.us-west-2.elb.amazonaws.com.
update-1549120573.us-west-2.elb.amazonaws.com has address 54.214.41.66
update-1549120573.us-west-2.elb.amazonaws.com has address 54.214.44.14

The repositories:
zypper lr -u

| Alias | Name | Enabled | Refresh | URI

—±----------------------------------------±------------------------------±--------±--------±-----------------------------------------------------------------------------------------------
1 | local | local | Yes | No | dir:///root
2 | susecloud:SLE11-SDK-SP1 | SLE11-SDK-SP1 | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/install/SLE11-SDK-SP1/sle-11-i586
3 | susecloud:SLE11-SDK-SP1-Pool | SLE11-SDK-SP1-Pool | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP1-Pool/sle-11-i586
4 | susecloud:SLE11-SDK-SP1-Updates | SLE11-SDK-SP1-Updates | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP1-Updates/sle-11-i586
5 | susecloud:SLE11-SDK-SP2-Core | SLE11-SDK-SP2-Core | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP2-Core/sle-11-i586
6 | susecloud:SLE11-SDK-SP2-Updates | SLE11-SDK-SP2-Updates | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP2-Updates/sle-11-i586
7 | susecloud:SLE11-SDK-SP3-Pool | SLE11-SDK-SP3-Pool | Yes | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP3-Pool/sle-11-i586
8 | susecloud:SLE11-SDK-SP3-Updates | SLE11-SDK-SP3-Updates | Yes | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-SDK-SP3-Updates/sle-11-i586
9 | susecloud:SLE11-SP1-Debuginfo-Pool | SLE11-SP1-Debuginfo-Pool | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-SP1-Debuginfo-Pool/sle-11-i586
10 | susecloud:SLE11-SP1-Debuginfo-Updates | SLE11-SP1-Debuginfo-Updates | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-SP1-Debuginfo-Updates/sle-11-i586
11 | susecloud:SLE11-SP2-Debuginfo-Core | SLE11-SP2-Debuginfo-Core | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-SP2-Debuginfo-Core/sle-11-i586
12 | susecloud:SLE11-SP2-Debuginfo-Updates | SLE11-SP2-Debuginfo-Updates | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-SP2-Debuginfo-Updates/sle-11-i586
13 | susecloud:SLE11-SP2-WebYaST-1.3-Pool | SLE11-SP2-WebYaST-1.3-Pool | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-SP2-WebYaST-1.3-Pool/sle-11-i586
14 | susecloud:SLE11-SP2-WebYaST-1.3-Updates | SLE11-SP2-WebYaST-1.3-Updates | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-SP2-WebYaST-1.3-Updates/sle-11-i586
15 | susecloud:SLE11-SP3-Debuginfo-Pool | SLE11-SP3-Debuginfo-Pool | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-SP3-Debuginfo-Pool/sle-11-i586
16 | susecloud:SLE11-SP3-Debuginfo-Updates | SLE11-SP3-Debuginfo-Updates | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-SP3-Debuginfo-Updates/sle-11-i586
17 | susecloud:SLE11-WebYaST-SP1 | SLE11-WebYaST-SP1 | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/install/SLE11-WebYaST-SP1/sle-11-i586
18 | susecloud:SLE11-WebYaST-SP1-Updates | SLE11-WebYaST-SP1-Updates | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-WebYaST-SP1-Updates/sle-11-i586
19 | susecloud:SLE11-WebYaST-SP2-Pool | SLE11-WebYaST-SP2-Pool | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-WebYaST-SP2-Pool/sle-11-i586
20 | susecloud:SLE11-WebYaST-SP2-Updates | SLE11-WebYaST-SP2-Updates | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLE11-WebYaST-SP2-Updates/sle-11-i586
21 | susecloud:SLES11-Extras | SLES11-Extras | Yes | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLES11-Extras/sle-11-i586
22 | susecloud:SLES11-SP1 | SLES11-SP1 | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/install/SLES11-SP1/sle-11-i586
23 | susecloud:SLES11-SP1-Pool | SLES11-SP1-Pool | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLES11-SP1-Pool/sle-11-i586
24 | susecloud:SLES11-SP1-Updates | SLES11-SP1-Updates | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLES11-SP1-Updates/sle-11-i586
25 | susecloud:SLES11-SP2-Core | SLES11-SP2-Core | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLES11-SP2-Core/sle-11-i586
26 | susecloud:SLES11-SP2-Extension-Store | SLES11-SP2-Extension-Store | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLES11-SP2-Extension-Store/sle-11-i586
27 | susecloud:SLES11-SP2-Updates | SLES11-SP2-Updates | No | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLES11-SP2-Updates/sle-11-i586
28 | susecloud:SLES11-SP3-Extension-Store | SLES11-SP3-Extension-Store | Yes | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLES11-SP3-Extension-Store/sle-11-i586
29 | susecloud:SLES11-SP3-Pool | SLES11-SP3-Pool | Yes | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLES11-SP3-Pool/sle-11-i586
30 | susecloud:SLES11-SP3-Updates | SLES11-SP3-Updates | Yes | Yes | http://us-west-2-ec2-update.susecloud.net/repo/update/SLES11-SP3-Updates/sle-11-i586

These all have the same domain name.

I have since removed all these repositories guessing that a refresh would maybe bring back good addresses. No luck

[Willem1]

[QUOTE=comptont;25295]The server can resolve the IP address:
host us-west-2-ec2-update.susecloud.net
us-west-2-ec2-update.susecloud.net is an alias for update-1549120573.us-west-2.elb.amazonaws.com

…

These all have the same domain name.

I have since removed all these repositories guessing that a refresh would maybe bring back good addresses. No luck[/QUOTE]

Hmmm… it could well be that there is an issue with the update/repo service.

You might be best off contacting support on Amazon or via SUSE directly. (or others might chime in in this thread).

Sorry I don’t have a better answer for you.

-Willem

[malcolmlewis]

Hi
Maybe have a browse in the Amazon-EC2 subforum here;
https://forums.suse.com/forumdisplay.php?94-Amazon-EC2

There have be image and infrastructure changes in the last few weeks, one wonders if something is cached somewhere in the ether causing problems…?

[comptont]

[QUOTE=malcolmlewis;25297]Hi
Maybe have a browse in the Amazon-EC2 subforum here;
https://forums.suse.com/forumdisplay.php?94-Amazon-EC2

There have be image and infrastructure changes in the last few weeks, one wonders if something is cached somewhere in the ether causing problems…?[/QUOTE]

I was thinking the same thing. It seems more like an Amazon problem than a susecloud problem, but I am just guessing. I looked for an Amazon support contact, but Amazon declines support for EC2 customers.
Who do I contact?

Thanks.

[malcolmlewis]

On Sun 07 Dec 2014 02:44:01 PM CST, comptont wrote:

malcolmlewis;25297 Wrote:[color=blue]

Hi
Maybe have a browse in the Amazon-EC2 subforum here;
https://forums.suse.com/forumdisplay.php?94-Amazon-EC2

There have be image and infrastructure changes in the last few weeks,
one wonders if something is cached somewhere in the ether causing
problems…?[/color]

I was thinking the same thing. It seems more like an Amazon problem
than a susecloud problem, but I am just guessing. I looked for an
Amazon support contact, but Amazon declines support for EC2 customers.

Who do I contact?

Thanks.

Hi
Repost your query in the Amazon-Ec2 subforum indicated, the SUSE folks
should respond since they monitor that one.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.28-4-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!