pa1.rsyncpalace.info down again

Portal Home > Knowledgebase > Industry Announcements > Web Hosting Main Forums > Providers and Network Outages and Updates > pa1.rsyncpalace.info down again

Posted by dkg, 11-01-2010, 11:16 AM
I reported this to Otto last Friday and I still don't have access to pa1. In fact, the nameservers for all of rsyncpalace.info are also down. I tried accessing the server with the IP address provided when I signed up and the server is unresponsive. I have had one response to my ticket from Otto on Friday saying he would look into this and there have been no updates since. This is now getting serious for me since I need to get access to some backups I have on that server.

I have been an RsyncPalace.com customer for the past 10 months and have been generally happy. However, this is the second time in two months there have been serious problems with this server
Posted by bear, 11-01-2010, 12:43 PM
I can't reach anything on the server via http (cpanel login), but I'm able to access via shell without issue. Checking the nameservers for the main domain, they time out.
Posted by dkg, 11-01-2010, 01:47 PM
I never really considered using the cpanel login (btw, it doesn't work either). I cannot get a connection with SSH -- it instantly disconnects when attempting a connection.

BTW, my nightly cronjob for backups hasn't reported back to me either since early Friday morning.
Posted by bear, 11-01-2010, 02:21 PM
I was moved at some point to pa2 and forgot to update my notes, so sorry about that incorrect info above.
I did a trace to his main site, and it's showing some major delays in the DC, which looks like a broken router. Never completes to his server's hostname, but some hops right in front of it have 99, 2055 and 719 ms times.
Posted by dkg, 11-01-2010, 02:29 PM
I am not sure what you mean by "his main site". If you mean rsyncpalace.com, I have had no issues with that site and there is nothing weird about the traceroute to it (it appears to be hosted at Softlayer in Dallas).
Posted by bear, 11-01-2010, 02:54 PM
".info", not the .com.
Since that's the hostname on the servers, that's the one that's relevant. That resolves to "199.19.226.149", which was very unreachable when I'd looked. "Main site" was misleading, sorry about that.
Posted by dkg, 11-01-2010, 03:14 PM
Well, I couldn't resolve that hostname at all since the nameservers are offline. And since I didn't have an IP address for it I couldn't do a traceroute.

What is most disturbing is the complete lack of communications from Otto or any other representative of rsyncpalace regarding this outage
Posted by -OY-, 11-01-2010, 10:23 PM

Quote:

Originally Posted by dkg

Well, I couldn't resolve that hostname at all since the nameservers are offline. And since I didn't have an IP address for it I couldn't do a traceroute.

What is most disturbing is the complete lack of communications from Otto or any other representative of rsyncpalace regarding this outage

I'm truly sorry for the lack of communications Dave, I've updated your ticket with additional information regarding the server status.

As to why the .info does not respond, it's because that isn't the domain for what we use for the hostnames of our servers or nameservers.

Otto
Posted by bear, 11-01-2010, 10:47 PM

Quote:

Originally Posted by -OY-

that isn't the domain for what we use for the hostnames of our servers

It isn't? Maybe I'm misunderstanding, but:
pa1.rsyncbackup.info
pa2.rsyncbackup.info
Aren't they hostnames?
Posted by -OY-, 11-01-2010, 11:03 PM

Quote:

Originally Posted by bear

It isn't? Maybe I'm misunderstanding, but:
pa1.rsyncbackup.info
pa2.rsyncbackup.info
Aren't they hostnames?

Yes, those are correct. However, the thread title was .rsyncpalace.info so I was under the assumption that that's why Dave thought the nameservers were down as well.
Posted by dkg, 11-02-2010, 06:41 AM

Quote:

Originally Posted by -OY-

Yes, those are correct. However, the thread title was .rsyncpalace.info so I was under the assumption that that's why Dave thought the nameservers were down as well.

Oops, you are correct. I was mixing up your one set of hostnames for the other. Sorry.

And thank you for the update.