cannot connect to repo

[mneese77]

here is the error...

Code: Select all

Loaded plugins: fastestmirror
Determining fastest mirrors
Could not retrieve mirrorlist http://www.atomicorp.com/mirrorlist/atomic/centos-5-x86_64 error was
[Errno 4] IOError: <urlopen error (113, 'No route to host')>
Error: Cannot find a valid baseurl for repo: atomic

This is after yum clean all....

[breun]

Might have been a temporary problem? It's working for me:

# curl http://www.atomicorp.com/mirrorlist/ato ... s-5-x86_64
http://www2.atomicorp.com/channels/atom ... s/5/x86_64
http://www3.atomicorp.com/channels/atom ... s/5/x86_64
http://www4.atomicorp.com/channels/atom ... s/5/x86_64
http://www5.atomicorp.com/channels/atom ... s/5/x86_64
http://www6.atomicorp.com/channels/atom ... s/5/x86_64
http://www7.atomicorp.com/channels/atom ... s/5/x86_64

[mikeshinn]

If you can't connect, whats your IP?

[mneese77]

I am not getting info in the web gui either...

my ip **.**.***.***....

Could I be on some blacklist or something?

EDITED>>>just checked using a blacklist scan and I am clear on some 140 blacklists with no issues there...

[mikeshinn]

You're not shunned or blocked by us. Whats the error you get when you run:

asl -u

I also see that your system stopped logging in on the 6th, is it possible you made a change on your system that is mucking up your routes? Or may some firewall rules on your end that are blocking outbound connections?

[mneese77]

here is the asl -u error...

[root@u15332031 etc]# asl -u
Checking for updates..

Update2 failed for some reason, retrying with full debug information...
--2010-10-08 12:37:16-- http://www.atomicorp.com/channels/rules/VERSION
Resolving www.atomicorp.com... 74.208.155.133
Connecting to www.atomicorp.com|74.208.155.133|:80... failed: No route to host.

I have added two new IPs to the server, with one being dedicated for a cart, and i added a new cert for my home server...the ip is the same for the server itself, just added the ssl cert.

[mikeshinn]

That would be caused by a local routing issue then. The error is being returned by your OS, theres no route, so you'll want to check your routing tables, and also use a sniffer and traceroute to see if its local routing issue.

Our book actually covers this in depth. If you made changes to your system around the time this started, then its probably safe to say those changes are the likely cause.

[mikeshinn]

I just logged into your system, you've got some kind of major network issue going on. I think you are hosted with 1and1, this looks like a networking problem at 1and1. Your local network isnt returning an ARP request for the upstream destination:

tethereal -i eth0 host 74.208.155.133
Capturing on eth0
0.000000 TyanComp_4c:4f:c0 -> Broadcast ARP Who has 74.208.155.133? Tell <redacted>
0.999503 TyanComp_4c:4f:c0 -> Broadcast ARP Who has 74.208.155.133? Tell <redacted>
1.999990 TyanComp_4c:4f:c0 -> Broadcast ARP Who has 74.208.155.133? Tell <redacted>

You've got a seriously fubar arp table and the local router isnt returning ARP requests, it might be your new IPs you added, could be the subnet on an interface (without knowing whats correct can't say for sure with just a quick glance) - hard to say, talk with 1and1 about whats going, but its on your end:

arp -n
Address HWtype HWaddress Flags Mask Iface
<redacted> (incomplete) eth0
<redacted> (incomplete) eth0
<redacted> (incomplete) eth0
<redacted> (incomplete) eth0
<redacted> (incomplete) eth0
<redacted> (incomplete) eth0
<redacted> (incomplete) eth0
<redacted> (incomplete) eth0
<redacted> ether 00:00:5e:00:01:f0 C eth0
<redacted> (incomplete) eth0
<redacted> ether 00:00:0c:07:ac:00 C eth0

[mneese77]

thanks for this info...i think it is something with my new IPs and the cert I installed..I may have done this incorrectly, so I'm off to 1and1 land for tech support...

[mneese77]

Just to finalize this for others...yes you were correct mshinn, and yes it was related to my new ips added to the server...
I setup one of the ips with an incorrect submask...e.g. (names changed to protect the innocent) 188.88.88.77.255.255.255.255..instead i had it configured as 188.88.88.77.255.255.0.0

This just messed up the whole server in so many ways...two little numbers wrong and things fell apart...