Atomicorp

Posted: **Wed Jan 14, 2009 12:03 pm**

Is this a problem on my end? It worked fine yesterday when I ran yum update.

Could not retrieve mirrorlist http://www.atomicorp.com/mirrorlist/ato ... tos-5-i386 error was
[Errno 4] IOError: <urlopen error (113, 'No route to host')>
Error: Cannot find a valid baseurl for repo: atomic

Using repos:

atomic.repo:

Code: Select all

# Name: Atomic Rocket Turtle RPM Repository for CentOS / Red Hat Enterprise Linux 5 -
# URL: http://www.atomicrocketturtle.com/
[atomic]
name = CentOS / Red Hat Enterprise Linux $releasever - atomicrocketturtle.com
mirrorlist = http://www.atomicorp.com/mirrorlist/atomic/centos-5-$basearch
#mirrorlist = http://www.atomicorp.com/channels/atomic/centos/5/mirrors-atomic
enabled = 1
priority = 1
protect = 0
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt
gpgcheck = 1

# Almost Stable, release candidates for [atomic]
[atomic-testing]
name = CentOS / Red Hat Enterprise Linux $releasever - atomicrocketturtle.com - (Testing)
mirrorlist = http://www.atomicorp.com/mirrorlist/atomic-testing/centos-5-$basearch
enabled = 0
priority = 1
protect = 0
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt
gpgcheck = 1

# Untested, Unstable, known buggy, and incomplete packages.
#[atomic-bleeding]
#name = CentOS / Red Hat Enterprise Linux $releasever - atomicrocketturtle.com - (Bleeding)
#baseurl = http://www.atomicorp.com/channels/atomic-bleeding/centos/5/$basearch/
#enabled = 0
#priority = 1
#protect = 0
#gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt
#gpgcheck = 1

CentOS-Base.repo:

Code: Select all

# CentOS-Base.repo
#
# This file uses a new mirrorlist system developed by Lance Davis for CentOS.
# The mirror system uses the connecting IP address of the client and the
# update status of each mirror to pick mirrors that are updated to and
# geographically close to the client.  You should use this for CentOS updates
# unless you are manually picking other mirrors.
#
# If the mirrorlist= does not work for you, as a fall back you can try the
# remarked out baseurl= line instead.
#
#

[base]
name=CentOS-$releasever - Base
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=os
#baseurl=http://mirror.centos.org/centos/$releasever/os/$basearch/
gpgcheck=1
gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5

#released updates
[updates]
name=CentOS-$releasever - Updates
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates
#baseurl=http://mirror.centos.org/centos/$releasever/updates/$basearch/
gpgcheck=1
gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5

#packages used/produced in the build but not released
[addons]
name=CentOS-$releasever - Addons
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=addons
#baseurl=http://mirror.centos.org/centos/$releasever/addons/$basearch/
gpgcheck=1
gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5

#additional packages that may be useful
[extras]
name=CentOS-$releasever - Extras
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras
#baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
gpgcheck=1
gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5

#additional packages that extend functionality of existing packages
[centosplus]
name=CentOS-$releasever - Plus
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=centosplus
#baseurl=http://mirror.centos.org/centos/$releasever/centosplus/$basearch/
gpgcheck=1
enabled=0
gpgkey=http://mirror.centos.org/centos/RPM-GPG-KEY-CentOS-5

plesk.repo:

Code: Select all

[plesk]
name=Plesk Server Administrator
mirrorlist=http://www.atomicorp.com/mirrorlist/plesk/9/centos-$releasever-$basearch
gpgcheck=0
enabled=1
# Plesk RPM bug
exclude=psa-mail-qc-driver*

Posted: **Wed Jan 14, 2009 1:42 pm**

Yeah network issue maybe? The system was rebooting earlier in the day too

Posted: **Wed Jan 14, 2009 5:23 pm**

Hmmm... still having the problem. It actually started at about 2 am eastern this morning (14 hours ago) not long after I did a "yum update" on a fresh image/reinstall. I wonder if an update may be the cause.

Posted: **Wed Jan 14, 2009 6:18 pm**

Hmm, well we added a bunch of mirrors a few weeks ago, so maybe its time to move the mirrorlist's off to another box. That at least should mitigate the problem until we get to the bottom of whats going on here.

Posted: **Wed Jan 14, 2009 9:44 pm**

Thought it might be a problem getting through the firewall. I haven't set up mod_security, apf, psad or anything on the box yet. I just have the default firewall running. I shut down the firewall and left it wide open but was still getting the same error.

Posted: **Thu Jan 15, 2009 12:43 am**

ok, disabled all but the CentOS repo and yum works fine. Its only when I add the ART repo back in that the error occurs.

Posted: **Thu Jan 15, 2009 9:46 am**

Ah, maybe youre shunned. Whats your IP?

Posted: **Thu Jan 15, 2009 9:59 am**

217.160.240.21

What could trigger getting the door slammed in your face?

Posted: **Thu Jan 15, 2009 1:23 pm**

Nope, not shunned or ever shunned.

Posted: **Thu Jan 15, 2009 1:33 pm**

Thanks Michael (& Scott)...

I'm not sure what else to check on my end. I guess I'll check back from time to time and see if its changed. Seems odd that I'm the only one reporting this problem without it coming from my end... uh... so-to-speak...

Posted: **Thu Jan 15, 2009 1:49 pm**

OK... thought I'd check to see if I could access the mirrorlist via lynx. Lynx reports that it couldn't connect:

Code: Select all

lynx: Can't access startfile http://www.atomicorp.com/channels/atomic/centos/5/mirrors-atomic

So I tried http://www.atomicorp.com and http://www.atomicrocketturtle.com and still the same result

Next I tried disney.com, google.com, ebay.com... they all work.

After that I went to a shared server account and tried both atomicorp.com and atomicrocketturtle.com with lynx and they both worked.

Again, this is still on a fresh install with only the default firewall running. The only thing I've done is run yum update from the ART repo then upgraded to 9.0.0

Posted: **Thu Jan 15, 2009 2:39 pm**

So, for your firewall, check this.

Code: Select all

/etc/init.d/iptables stop
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X

Try a dig or a host comand to see if your getting the right stuff

Code: Select all

# dig www.atomicorp.com

; <<>> DiG 9.3.4-P1 <<>> www.atomicorp.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55707
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.atomicorp.com.             IN      A

;; ANSWER SECTION:
www.atomicorp.com.      4172    IN      CNAME   atomicorp.com.
atomicorp.com.          12229   IN      A       82.165.242.46

;; Query time: 407 msec
;; SERVER: 10.7.30.50#53(10.7.30.50)
;; WHEN: Thu Jan 15 10:37:18 2009
;; MSG SIZE  rcvd: 65

# host www.atomicorp.com
www.atomicorp.com is an alias for atomicorp.com.
atomicorp.com has address 82.165.242.46
atomicorp.com mail is handled by 10 ac3.atomicorp.com.

Posted: **Thu Jan 15, 2009 3:04 pm**

This is what I get from stopping iptables:

Code: Select all

$ /etc/init.d/iptables stop
Flushing firewall rules:                                   [  OK  ]
Setting chains to policy ACCEPT: security raw nat mangle fi[FAILED]
Unloading iptables modules:                                [  OK  ]

No feedback from using any of the other switches mentioned.

dig:

Code: Select all

$ dig www.atomicorp.com

; <<>> DiG 9.3.4-P1 <<>> www.atomicorp.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52393
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.atomicorp.com.             IN      A

;; ANSWER SECTION:
www.atomicorp.com.      540     IN      CNAME   atomicorp.com.
atomicorp.com.          540     IN      A       82.165.242.46

;; Query time: 33 msec
;; SERVER: 217.160.240.251#53(217.160.240.251)
;; WHEN: Thu Jan 15 13:52:51 2009
;; MSG SIZE  rcvd: 65

host:

Code: Select all

$ host www.atomicorp.com
www.atomicorp.com is an alias for atomicorp.com.
atomicorp.com has address 82.165.242.46
atomicorp.com mail is handled by 5 ac1.atomicorp.com.
atomicorp.com mail is handled by 10 ac3.atomicorp.com.
atomicorp.com mail is handled by 5 ac2.atomicorp.com.
atomicorp.com mail is handled by 0 ac0.atomicorp.com.

Posted: **Thu Jan 15, 2009 3:49 pm**

how about a traceroute ?

Posted: **Thu Jan 15, 2009 5:57 pm**

This is interesting... it is showing a nameserver I set up a long time ago and thought I had switched back to 1and1's nameservers.

Code: Select all

$ traceroute atomicorp.com
traceroute to atomicorp.com (82.165.242.46), 30 hops max, 40 byte packets
 1  ns2.webtinker.com (82.165.241.79)  2997.035 ms !H  2996.606 ms !H  2996.117 ms !H

Wonder if that IP has been shunned???

Atomicorp

[RESOLVE]Error: Cannot find a valid baseurl for repo: atomic

[RESOLVE]Error: Cannot find a valid baseurl for repo: atomic