Any news on when it might come back up?Site Down?
Forum rules
This forum is now read-only. Support for TheTVDB.com is now available at https://support.thetvdb.com/
This forum is now read-only. Support for TheTVDB.com is now available at https://support.thetvdb.com/
-
pazoo
Figures the day I go to organize my tv shows the site goes down. Any news on when it might come back up?
Any news on when it might come back up?-
manekineko
Yup. Figures. This weekend I would have had the time to do a huge series clean-uppazoo wrote:Figures the day I go to organize my tv shows the site goes down.
It's been more than half a day now. An update would be much appreciated.Any news on when it might come back up?
One of the customers at that location turned up 9 blades last night and blew 2 circuits. They've been working since late last night trying to resolve the issue. The new circuit won't be installed until Monday. We'll know more in a bit.
If it ends up being Monday, CrazzyKid is going to move the server to his new datacenter today. He'd then set up the old location as a mirror for both the current site and the new site. If we do need to move the site, I'll have to make a DNS update to the new IP address accordingly. Then it would be up to everyone to clear their DNS cache to find the new site, or wait however long for the record to update. In expectation of this, I'm lowering the TTL for the DNS record to 300 seconds (from 86400). This will apply for the rest of the weekend. Should speed up resolution for some people.
In a nutshell: either later today or Monday. Sorry, folks. The good news is that we wanted to move to the new datacenter at some point anyway.
If it ends up being Monday, CrazzyKid is going to move the server to his new datacenter today. He'd then set up the old location as a mirror for both the current site and the new site. If we do need to move the site, I'll have to make a DNS update to the new IP address accordingly. Then it would be up to everyone to clear their DNS cache to find the new site, or wait however long for the record to update. In expectation of this, I'm lowering the TTL for the DNS record to 300 seconds (from 86400). This will apply for the rest of the weekend. Should speed up resolution for some people.
In a nutshell: either later today or Monday. Sorry, folks. The good news is that we wanted to move to the new datacenter at some point anyway.
-
manekineko
Oh well. Things like that just happen and there's nothing you can do about it.
Thanks for keeping us updated.
Thanks for keeping us updated.
-
brillyfresh
is http://thetvdb.somewhere.com/ a suitable mirror for the time being?
scraping doesn't seem to work; i tried setting up their IP address as thetvdb.com and images.thetvdb.com in my hosts file, but i guess that site doesn't have the correct host headers set up, because i get a 404 if i try to browse to thetvdb.com with that configuration
for simple browsing, it works for now
scraping doesn't seem to work; i tried setting up their IP address as thetvdb.com and images.thetvdb.com in my hosts file, but i guess that site doesn't have the correct host headers set up, because i get a 404 if i try to browse to thetvdb.com with that configuration
for simple browsing, it works for now
-
emigrating
- Site Admin
- Posts: 278
- Joined: Mon Aug 27, 2007 2:38 pm
- Contact:
Where'd ya get that URL from? That's my local boxbrillyfresh wrote:is http://thetvdb.somewhere.com/ a suitable mirror for the time being?
scraping doesn't seem to work; i tried setting up their IP address as thetvdb.com and images.thetvdb.com in my hosts file, but i guess that site doesn't have the correct host headers set up, because i get a 404 if i try to browse to thetvdb.com with that configuration
for simple browsing, it works for now
API access may work on it, but shouldn't be relied upon as it's basically just a local DB copy for internal use. Should bw usage go up a lot on it I'll probably have to pull the plug anyway as there are other, more mission critical, applications hosted on the same pipe.
We're trying to get the current outtage sorted though and like Szsori said, Monday at the very latest - hopefully earlier at a new location.
--edit--
Removed URL
-
brillyfresh
oops sorry, i found it through google, 2nd page of resultsemigrating wrote:Where'd ya get that URL from? That's my local box
API access may work on it, but shouldn't be relied upon as it's basically just a local DB copy for internal use. Should bw usage go up a lot on it I'll probably have to pull the plug anyway as there are other, more mission critical, applications hosted on the same pipe.
We're trying to get the current outtage sorted though and like Szsori said, Monday at the very latest - hopefully earlier at a new location.
--edit--
Removed URL
may want to set robots.txt on it or similar to prevent it from being crawled
-
Chianti
Check out nac.net. i have connections there, so I could likely get you a discount.szsori wrote:I have an email out to Crzzykid, who handles issues like this. Hopefully it won't be too long. Since I can't connect remotely there's no way of telling what's going on with it right now.
@Chianti:
I forgot I removed that email alias a while ago. I just added it again. The issue isn't so much the server itself, but rather the bandwidth the server takes. We may need hardware at some point, but right now we're looking more at purchasing hosting where hardware and software licenses are provided, since we need some SQL Server and Windows licenses as well for the new site.
Will definitely check it out.
Just a followup for everyone. He's not yet been able to get access to the co-loc, but he's working on it. I've made the DNS changes required to get the site moved ASAP as soon as possible, but he'll still need to get in there to do it. Unfortunately this means Sunday or Monday at this point. I know it's inconveniencing people, but we've done all we can do to this point.
Once the new site is up and running, mirrors will be much easier so we shouldn't have to deal with this again after that.
Just a followup for everyone. He's not yet been able to get access to the co-loc, but he's working on it. I've made the DNS changes required to get the site moved ASAP as soon as possible, but he'll still need to get in there to do it. Unfortunately this means Sunday or Monday at this point. I know it's inconveniencing people, but we've done all we can do to this point.
Once the new site is up and running, mirrors will be much easier so we shouldn't have to deal with this again after that.
-
tecnobrat
Thanks for your hard work on this. I know that downtime happens, doesn't matter how many precautions you take
I don't know if you guys have discussed the options of mirroring some of the higher bandwidth content off to a cloud system like amazon, or something similar. Or allowing users to setup mirrors for this content. I assume the banners and screenshots are the highest bandwidth suckers you have.
I for one have a server which is used mainly to host some personal content, but it is in a multi-10 gigabit homed DC, with a 100mbit connection and with 10 terrabytes of bandwidth a month. I would be willing to donate some of those resources. I would assume an rsync mirror of the image files, with some sort of RRDNS setup (which you would have to check uptimes/sync status of servers, and remove/add them from the pool).
Anyways, the offer is always there.
I don't know if you guys have discussed the options of mirroring some of the higher bandwidth content off to a cloud system like amazon, or something similar. Or allowing users to setup mirrors for this content. I assume the banners and screenshots are the highest bandwidth suckers you have.
I for one have a server which is used mainly to host some personal content, but it is in a multi-10 gigabit homed DC, with a 100mbit connection and with 10 terrabytes of bandwidth a month. I would be willing to donate some of those resources. I would assume an rsync mirror of the image files, with some sort of RRDNS setup (which you would have to check uptimes/sync status of servers, and remove/add them from the pool).
Anyways, the offer is always there.