Page 2 of 3

Posted: Fri Jan 16, 2009 10:05 am
by scott
No thats not on the list, you should have gotten more hops than that too. Even if it was, I wonder if there is an internal routing problem there.

Posted: Fri Jan 16, 2009 11:27 am
by jholzy
If it were an internal routing problem it seems that it would affect all connections rather than just a specific one...
scott wrote:Even if it was, I wonder if there is an internal routing problem there.

Posted: Fri Jan 16, 2009 12:38 pm
by hostingguy
can you post the entire traceroute as well as a print out of the route command (I think its route -p ? )

Posted: Fri Jan 16, 2009 1:04 pm
by jholzy
This is the complete traceroute. No other feedback.

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)  2995.451 ms !H  2995.229 ms !H  2994.838 ms !H
route:

Code: Select all

$ route -v
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.255.255.1    *               255.255.255.255 UH    0      0        0 eth0
82.165.0.0      *               255.255.0.0     U     0      0        0 eth0
217.160.0.0     *               255.255.0.0     U     0      0        0 eth0
default         10.255.255.1    0.0.0.0         UG    0      0        0 eth0

Posted: Fri Jan 16, 2009 1:17 pm
by jholzy
Just for reference, here's the feedback from another traceroute:

Code: Select all

$ traceroute disney.com
traceroute to disney.com (199.181.132.250), 30 hops max, 40 byte packets
 1  10.255.255.253 (10.255.255.253)  15.511 ms  14.558 ms  13.848 ms
 2  vl-993.gw-core-a.whn.oneandone.net (217.160.229.45)  0.579 ms  0.537 ms  0.581 ms
 3  ge-2-3-0-0.bb-a.tla.nyc.us.oneandone.net (217.160.229.97)  1.004 ms  0.817 ms  0.826 ms
 4  nyk-b5-link.telia.net (213.248.95.69)  0.754 ms  0.829 ms  0.774 ms
 5  4.68.63.213 (4.68.63.213)  1.175 ms  1.275 ms  0.749 ms
 6  vlan79.csw2.NewYork1.Level3.net (4.68.16.126)  12.435 ms vlan69.csw1.NewYork1.Level3.net (4.68.16.62)  1.880 ms  13.347 ms
 7  ae-72-72.ebr2.NewYork1.Level3.net (4.69.134.85)  1.422 ms ae-62-62.ebr2.NewYork1.Level3.net (4.69.134.81)  1.090 ms  12.695 ms
 8  ae-2.ebr1.Chicago1.Level3.net (4.69.132.65)  33.304 ms  30.655 ms  24.721 ms
 9  ae-6.ebr1.Chicago2.Level3.net (4.69.140.190)  21.666 ms  22.160 ms  22.108 ms
10  ae-3.ebr2.Denver1.Level3.net (4.69.132.61)  56.957 ms  56.759 ms  56.135 ms
11  ae-2.ebr2.Seattle1.Level3.net (4.69.132.53)  80.830 ms  80.385 ms  79.763 ms
12  ae-23-56.car3.Seattle1.Level3.net (4.68.105.164)  72.184 ms ae-23-52.car3.Seattle1.Level3.net (4.68.105.36)  72.012 ms ae-23-56.car3.Seattle1.Level3.net (4.68.105.164)  71.558 ms
13  WALT-DISNEY.car3.Seattle1.Level3.net (4.71.152.22)  71.495 ms  72.289 ms  72.382 ms
14  sav.online.disney.com (199.181.132.250)  72.500 ms  72.170 ms  72.828 ms

Posted: Fri Jan 16, 2009 2:42 pm
by hostingguy
it looks like ns2.webtinker.com is your problem - it cant get to the right place. Can you remove your static route to 82.165.0.0 and see if that helps ?

Posted: Fri Jan 16, 2009 3:29 pm
by jholzy
Ok... I'm not even sure how that's even in the picture. My guess is that it has something to do with an abandoned attempt at setting up name servers a long time ago. I'll do some digging and see if I can remove it.

Thanks for the help. Hopefully this resolves the problem. I'm just a little unsure why it would affect just the connection to atomicorp.com and attomicrocketturtle.com and not others.

Thank-you...

Posted: Fri Jan 16, 2009 3:36 pm
by hostingguy
I think it is becuase you have a static route for 82.165.x.x /16 - and both your name server and the atomi site are in the same 82.165.x.x so its not going to your default gateway.

Posted: Fri Jan 16, 2009 4:30 pm
by jholzy
Alrighty-then...That actually makes sense! I'll let you know how it turns out once I figure out where to make the change! Thanks again...

Posted: Fri Jan 30, 2009 1:20 pm
by jholzy
OMG!!! What a royal PIA! What a simple solution, once figured out! As you indicated, hostingguy, the static route was the bad guy. I'm not a routing wiz by any stretch and it took some studying but I finally got the right "route del" combination to remove the static route from the routing table:

Code: Select all

route del -net 82.165.0.0 netmask 255.255.0.0 dev eth0
After that all is good on the SE shores of Lake Erie!!!

Here's where I found some good help on how to use the route command. Also, "man route" was extremely helpful in learning about route.

Thanks for your input!

Re: Error: Cannot find a valid baseurl for repo: atomic

Posted: Thu Mar 05, 2009 3:00 pm
by gjesus
Hello,

I also get "Cannot find a valid baseurl for repo: atomic" on a 1&1 VPS with Plesk 9.0.1 trying to upgrade PHP 5.0.4 to 5.2.8 per:
http://www.atomicorp.com/wiki/index.php/PHP
[root@s15242287 ~]# wget -q -O - http://www.atomicorp.com/installers/atomic |sh

Atomic Archive installer, version 1.0.14
Configuring the [atomic] yum archive for this system

Installing the Atomic GPG key: OK
Downloading atomic-release-1.0-10.fc4.art.noarch.rpm: OK

Would you like to add the Plesk yum repository to the system?

Enable Plesk repository? (y/n) [Default: n]: y

Plesk 8.6 and 9.0 repositories are available:
NOTE: Plesk 9 repos are only available for rhel/centos 4 and 5

Enable Plesk 8.6 or 9.0? (8/9) [Default: 8]: 9

The Atomic Rocket Turtle archive has now been installed and configured for your system
The following channels are available:
atomic - [ACTIVATED] - contains the stable tree of ART packages
atomic-testing - [DISABLED] - contains the testing tree of ART packages
atomic-bleeding - [DISABLED] - contains the development tree of ART packages

[root@s15242287 ~]# yum upgrade
Error: Bad repository file ///etc/yum.repos.d/plesk.repo, no repo stanzas.
Setting up Upgrade Process
Setting up repositories
extras 100% |=========================| 1.1 kB 00:00
Cannot find a valid baseurl for repo: atomic
atomic.repo
# Name: Atomic Rocket Turtle RPM Repository for -
# URL: http://www.atomicrocketturtle.com/
[atomic]
name = $releasever - atomicrocketturtle.com
mirrorlist = http://www.atomicorp.com/mirrorlist/atomic/--$basearch
#mirrorlist = http://www.atomicorp.com/channels/atomi ... ors-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 = $releasever - atomicrocketturtle.com - (Testing)
mirrorlist = http://www.atomicorp.com/mirrorlist/ato ... -$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 = $releasever - atomicrocketturtle.com - (Bleeding)
#baseurl = http://www.atomicorp.com/channels/atomi ... $basearch/
#enabled = 0
#priority = 1
#protect = 0
#gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY.art.txt
#gpgcheck = 1
plesk.repo
[plesk]
name=Plesk Server Administrator
mirrorlist=http://www.atomicorp.com/mirrorlist/fed ... -$basearch
gpgcheck=0
enabled=1

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

Posted: Thu Mar 05, 2009 5:40 pm
by scott
ah look at that, it didnt expand the variables. What distro are you on?

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

Posted: Thu Mar 05, 2009 6:54 pm
by gjesus
FedoraCore 4
Parallels Plesk for Linux build 90090127.18
Linux 2.6.9-023stab048.6-smp

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

Posted: Thu Mar 05, 2009 7:39 pm
by mikeshinn
As an aside FC4 is completely end of life so you definitely don't want to run it or any other EOL OS. There are no patches for it and no one is maintaining them - you want to upgrade to a non-EOL distro ASAP.

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

Posted: Thu Mar 05, 2009 7:45 pm
by gjesus
pardon my ignorance, but how do I upgrade FC4 and what distro do I upgrade to?