Atomicorp

I appreciate the offer to use this medium to get questions cleared up but I'm not sure I have the patience to ask that many questions on a forum! lol... I'm going to reimage with the default install and add ASL then try to clean up the mess. Thanks again!

Thanks... I was able to find that and did the install. Is there a how-to anywhere? It seems that the only place I can even view the installation is via the serial console so was hoping to find a written step-by-step someplace... I know from the past that 1and1 has a way of screwing up the best laid ...

Is AOOI still alive and well? And if so, is there any up-to-date how-to's for it? Or would a really rusty old hack like me be better off just going with 1and1's set up? I have ASL ready to put on it and thought AOOI might play a little nicer with it. I found a lot of high risk alerts from the defaul...

I assume you mean running the "Retrieve Keys" located at Plesk Admin: Home > License Management > Retrieve Keys - This has already been done and Plesk is a fully functional and licensed version. I'm just not finding a file that contains .key I.E., psa.key or *.key for that matter. I wonder...

I have a new 1and1 Root server that I have run the AOOI on but haven't rebooted yet. At the end of the script it reminded me to back up the Plesk license key (thanks!) located at /etc/psa but there is no .key file there and the directory key.d is empty: $ ls -al total 40 drwxr-xr-x 5 root root 4096 ...

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 ...

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...

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 wh...

Just for reference, here's the feedback from another traceroute: $ 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....

This is the complete traceroute. No other feedback. $ 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: $ route -v Kernel IP routing table Destination Gateway Genm...

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.

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. $ 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 29...

This is what I get from stopping iptables: $ /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: $ dig www.atomicorp.com ; <<>...

OK... thought I'd check to see if I could access the mirrorlist via lynx. Lynx reports that it couldn't connect: 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 ...

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...