 |
| Fark site move (and 2-4 hours downtime) on the evening of Sat June 30. We'll try to webcast the carnage On the evening of Saturday, June 30, we'll be moving all of Fark's equipment to a new colocation provider. We'll be down for a couple of hours while this happens, starting around 7 pm US/Eastern time, probably between two and four hours... hopefully closer to two. We'll keep a static copy of all the main pages and tabs up on a temporary web server, so you'll still have something to read. Comments, user profiles, link submissions, mobile apps, user profiles, and all of TotalFark will be down during the move though. All of our numeric IP addresses will change during this move. We'll take the usual steps** to try to ensure your ISP picks up the change as fast as possible. Worst case, you might have to reboot your computer once after we move. We'll have directions up (at the old IP address) explaining what to do at that point, so no worries. Last time we did this, in October 2006, we were moving the servers 500 miles. This time we're moving them about 500 feet, or about one block down the street. So we won't be down anywhere near as long. Still, it takes a while to disassemble a full rack's worth of gear, roll it down the street, and re-bolt it into a new rack, and change all the IP addresses... longer if it decides to rain that night. We're also going to try to webcast the carnage, and the before & after drinking, on this Ustream channel, because, hey, why the hell not, it might be funny... assuming we can get it working over 3G/LTE... More details will be posted here, on our outage page, and on the main site if necessary... ** the usual steps = dropping DNS TTL's down and changing root nameserver glue records a full week in advance Some new complications w/ getting out of the old building may mean this takes a few hours longer than expected, but, hopefully not. :) Yes, there are very good reasons for not "just putting it in the cloud". Read the entire thread before suggesting it. :) |
||
| Add Comment | ||
| Showing 51-100 of 453 comments | ||
| Page 1 | Refresh | Page 3 |
| OgreMagi
AeAe: Change the TTL value on the DNS record to 5 minutes or something short. That should speed up the propagation of the DNS Five minutes is a bit short. I don't see any reason to set it to less than an hour. It's not like Fark is mission critical. Even if you set your TTL to a short value, an ISP is free to ignore that number. Many cache DNS and hold it for a long time, several days is not unusual. |
||
dramboxf ![[TotalFark]](http://img.fark.net/images/2003/totalfark.gif "[TotalFark]"){kind=small}
AeAe: Change the TTL value on the DNS record to 5 minutes Isn't TTL a "hop" value, not a "time" value? |
||
| Jake Havechek
Should we still be clenching our buttocks? |
||
| Majick Thise
Drew, I TOLD you geocities wouldn't be around forever |
||
| gunsmack
Was debating whether or not to go out and shoot some pool tonight. I think TF has finally found a way to get me out of the house. |
||
| GilRuiz1
Moving!  |
||
| AeAe
OgreMagi: AeAe: Change the TTL value on the DNS record to 5 minutes or something short. That should speed up the propagation of the DNS Five minutes is a bit short. I don't see any reason to set it to less than an hour. It's not like Fark is mission critical. Even if you set your TTL to a short value, an ISP is free to ignore that number. Many cache DNS and hold it for a long time, several days is not unusual. Well, duh, the point it to reduce propagation delay. They can set it back to something "reasonable" afterward. I'm no DNS speaking guy, but I think 4 hours was typical. |
||
| gunsmack
|
||
| SlantyBaws
JustSeanV67: Is there a designated drinker during this move? Everyone taking part in the move is a "Designated Drinker" you should know that by now! |
||
| Toshiro Mifune's Letter Opener
Third In Line: TMLO apparently already got into the MM. I'll have you know that I'm as sober as... ... um... ... A REALLY SOBER THING. Nyah! |
||
| Wyalt Derp
Is that 2-4 hours US/Eastern time or Greenwich Mean Time? |
||
| ph0rk
Somacandra: LaughingRadish: In other words, you might be running Windows. Any time Windows encounters something that's out of the ordinary (or even well-within the ordinary), a reboot is often required. [i.imgur.com image 320x240] That's why I only run OS/2 Warp 4. Nary a problem with my Netscape Navigator. shiat, you can still run Doom on that baby. |
||
| Amos Quito
Better you than me. I hate moving. |
||
| Bathia_Mapes
|
||
| BoboRod
gunsmack: Was debating whether or not to go out and shoot some pool tonight. I think TF has finally found a way to get me out of the house. Well, AFAIK, June 30 is NEXT Saturday night. Not that you should stay home tonight. |
||
| Third In Line
Toshiro Mifune's Letter Opener: Third In Line: TMLO apparently already got into the MM. I'll have you know that I'm as sober as... ... um... ... A REALLY SOBER THING. Nyah! Um... me too! |
||
| SlantyBaws
BarkingUnicorn: Gunz_drawn: Craptastic: Someone explain this to a non-computer guy. Why might I have to restart my computer? YES. I would like to know why too. My "puter" is almost 7 years old and the re-start string has been long gone. "Re-start string?" Are you using a lawn mower as a power supply? THAT would make a cool video! I personally prefer using a hamster with a shock collar as the "reboot" button :) |
||
| Buttbone McGillicutty
start->run->cmd /k ipconfig /flushdns /IDK it might work |
||
| edmo
OgreMagi: It's not like Fark is mission critical. Maybe you don't understand the mission. Besides, it's classified. |
||
| Unobtanium
Great. First saturday night in agens w/o Mrs. Un and Little Un, and you pick tonight. OgreMagi: Here's roughly the exchange we had when planning a move. Middle managers: You can't have any money. Just figure out how to move everything without downtime. Geek: Are you really that stupid? Note, the last line was not spoken out loud. So, your place has no disaster recovery plan? We at least have mirrored servers in a remote location. |
||
| middleoftheday
Toshiro Mifune's Letter Opener: I'll have you know that I'm as sober as... ... um... ...a ju-- hey. Are you Stephen Breyer? |
||
| AeAe
dramboxf: AeAe: Change the TTL value on the DNS record to 5 minutes Isn't TTL a "hop" value, not a "time" value? TTL = time to live. I'm unsure if TTL is used differently for ping or traceroute and I'm too lazy to look it up. In this context, the TTL value with regard to DNS is the how long the record is kept in cache by the local DNS server. When that TTL value is exceed, the record is flushed from cache. If you set the TTL value short, then the look up is done with more frequency. This is helpful when the IP addy of a website changes. The local DNS server doesn't "hold on" to the old IP for too long. |
||
| Buttbone McGillicutty
Buttbone McGillicutty: start->run->cmd /k ipconfig /flushdns /IDK it might work //it's 2012, I hate having to reboot ///don't get me started on Master Browser elections |
||
| clowncar on fire
So.. moving offshore? Fark You! |
||
| dramboxf
AeAe: TTL = time to live. I'm unsure if TTL is used differently for ping or traceroute and I'm too lazy to look it up. I think at the ping/tracert|traceroute level it's a "hop" count. |
||
| dramboxf
AeAe: TTL = time to live. I'm unsure if TTL is used differently for ping or traceroute and I'm too lazy to look it up. Just because I was curious: Every IP packet that gets sent out has a TTL field which is set to a relatively high number (in the case of ping a TTL of 255). As the packet traverses the network, the TTL field gets decreased by one by each router it goes through; when the TTL drops to 0, the packet is discarded by the router. The IP spec says that the TTL should be set to 60 (though it's 255 for ping packets). The main purpose of this is so that a packet doesn't live forever on the network and will eventually die when it is deemed "lost." But for ping purposes, it provides additional information. The TTL can be used to determine approximately how many router hops the packet has gone through. If the TTL field varies in successive pings, it could indicate that the successive reply packets are going via different routes, which isn't a great thing. (This is about the TTL value in a "ping" response) Source |
||
| OgreMagi
Unobtanium: Great. First saturday night in agens w/o Mrs. Un and Little Un, and you pick tonight. OgreMagi: Here's roughly the exchange we had when planning a move. Middle managers: You can't have any money. Just figure out how to move everything without downtime. Geek: Are you really that stupid? Note, the last line was not spoken out loud. So, your place has no disaster recovery plan? We at least have mirrored servers in a remote location. That was a different job that I no longer have. In my current job, we do have a disaster recovery plan -- though that could use some improvement (we're working on it). |
||
| Coronach
Well. Looks like 2-4 hours of internet porn on the 30th. Any suggestions? |
||
| Mike
Snort: No cure for for root dns server propagation Already changed the glue records today -- got one machine moved in advance already and it's already answering DNS requests at its new IP. AeAe: Change the TTL value on the DNS record to 5 minutes or something short. That should speed up the propagation of the DNS And I did that yesterday (1 hour). That's what I meant by "taking steps". And yes failing all that, ipconfig /flushdns will work, assuming they're on Windows, and I will have a page up on the old IP addresses explaining exactly that, and the Mac equivalent, in case someone can't reboot for some reason. I do think about these things :) |
||
| Toshiro Mifune's Letter Opener
middleoftheday: ...a ju-- hey. Are you Stephen Breyer? I'm a sentient carton of Breyers Ice Cream. (Don't tell the others.) |
||
| Mike
DNS TTL and the TTL seen by ping/traceroute are totally unrelated; one's a cache time and one's a hop count. |
||
| AeAe
Mike: Snort: No cure for for root dns server propagation Already changed the glue records today -- got one machine moved in advance already and it's already answering DNS requests at its new IP. AeAe: Change the TTL value on the DNS record to 5 minutes or something short. That should speed up the propagation of the DNS And I did that yesterday (1 hour). That's what I meant by "taking steps". And yes failing all that, ipconfig /flushdns will work, assuming they're on Windows, and I will have a page up on the old IP addresses explaining exactly that, and the Mac equivalent, in case someone can't reboot for some reason. I do think about these things :) You're clearly on the ball.. carry on.. ;) |
||
| vodka
Good luck, hope it goes better than these things usually do. ;) |
||
| WTFDYW
Mike: Craptastic: Someone explain this to a non-computer guy. Why might I have to restart my computer? When you type in www.fark.com, it translates that to a numeric address, and remembers it for a while so it doesn't have to keep re-translating it over and over. That numeric address is going to change, so if your computer remembers it for too long, it'll keep going to the old one when we change it. The fastest way (but not the only way) to make it forget the old one is to reboot... But we have taken some steps that should minimize the length of time it remembers things, so hopefully you won't have to... and hopefully things will just plain work. :) I have all the faith in the world in you Mike. Don't eat the fish though. |
||
| AeAe
dramboxf: AeAe: TTL = time to live. I'm unsure if TTL is used differently for ping or traceroute and I'm too lazy to look it up. Just because I was curious: Every IP packet that gets sent out has a TTL field which is set to a relatively high number (in the case of ping a TTL of 255). As the packet traverses the network, the TTL field gets decreased by one by each router it goes through; when the TTL drops to 0, the packet is discarded by the router. The IP spec says that the TTL should be set to 60 (though it's 255 for ping packets). The main purpose of this is so that a packet doesn't live forever on the network and will eventually die when it is deemed "lost." But for ping purposes, it provides additional information. The TTL can be used to determine approximately how many router hops the packet has gone through. If the TTL field varies in successive pings, it could indicate that the successive reply packets are going via different routes, which isn't a great thing. (This is about the TTL value in a "ping" response) Source Here's some interesting (to me anyway) trivia.. There was a time that the TTL value for traceroute was 30. Because the original designers didn't think that the Internets would ever be bigger than 30 hops. |
||
| Acharne
OgreMagi: Here's roughly the exchange we had when planning a move. Geeks: We're going to have a one to two day outage to move the equipment to the new colo in another state. Middle managers: We can't have an outage! Geeks: Then you'll have to give us the budget to buy duplicate equipment. Middle managers: You can't have the money. Find another way. Geeks: We can get by moving half the servers at a time with some reduced performance, but it's not possible without another filer. You need to give us the budget for another filer, which we need anyway. Middle managers: You can't have any money. Just figure out how to move everything without downtime. Geek: Are you really that stupid? Note, the last line was not spoken out loud. I work for an ISP. Last year we moved across town. The entire ISP. Let me tell you, that exact conversation happened many times, WITH the last line intact. |
||
| bgddy24601
As someone who is having another surgery on Wednesday and was planning on spending copious amounts of time on Fark while high on pain meds I am NOT getting a kick out of this. .But I'll be getting a kick out of the Percocets! |
||
| Kenny B
FARK Techs at work  |
||
| flucto
|
||
| picturescrazy
Best of luck! You'll need it. Beer spills so easily. |
||
| dramboxf
AeAe: Here's some interesting (to me anyway) trivia.. There was a time that the TTL value for traceroute was 30. Because the original designers didn't think that the Internets would ever be bigger than 30 hops. Jesus, god, I remember that. Something about 640k? /kidding |
||
| Toshiro Mifune's Letter Opener
I was all happy until I saw the Miracle Whip logo, flucto. Have you no sense of decency, sir? At long last, have you left no sense of decency? |
||
| middleoftheday
Toshiro Mifune's Letter Opener: I was all happy until I saw the Miracle Whip logo, flucto. For realz... I kind of really need to know what that what doing there. |
||
| middleoftheday
... so much so that I'm forgetting words, apparently. |
||
| kb7rky
Third In Line: You said "rack" twice. You like racks? *giggles* Can I see your rack? /blatant attempt at BIE //success or fail? ///we shall see ////even teh slashies liek teh bewbs! |
||
| flucto
Toshiro Mifune's Letter Opener: Have you no sense of decency, sir? At long last, have you left no sense of decency? You just can't please some people. Your own custom Breyer's flavor and you still squak. |
||
| Toshiro Mifune's Letter Opener
middleoftheday: For realz... I kind of really need to know what that what doing there. middleoftheday: ... so much so that I'm forgetting words, apparently. YOU SEE WHAT YOU'VE DONE, FLUCTO? *sobs gently* |
||
| Mike
|
||
| flucto
Toshiro Mifune's Letter Opener: Have you no sense of decency, sir? At long last, have you left no sense of decency? You just can't please some people. Your own custom Breyer's flavor and you still squawk. |
||
| Toshiro Mifune's Letter Opener
flucto: You just can't please some people. Your own custom Breyer's flavor and you still squak. This flavor does not represent me, knave! AWAY WITH IT |
||
| Showing 51-100 of 453 comments | ||
| Page 1 | Refresh | Page 3 |
| This thread is closed to new comments. |
Fark.com Mobile
Copyright © 1999 - 2013 Fark, Inc
Last updated: May 21 2013 07:55:20
Contact | Report error | TOS/legal/privacy
Full site
close