NS Server Issues - NO "ME TOO" POSTS

[Again]

sight wide attack maybe?

It's too early for April Fools...

(REFERENCE TO APRIL FOOLS 2011 FOR THOSE WHO DONT KNOW)

Funny. I was wondering the same thing as well...

[Gallopfrey and the Pony Republic Therof]

I have the site back, but it was down not 30 seconds ago.

[Again]

I have the site back, but it was down not 30 seconds ago.

It's just phasing in and out and in and out. Until we have it solid for more than 15 minutes, or until an Admin says it is completely resolved, get used to NationStates' slow heartbeat.

[The Cosmos]

Everything works for me except for the side bar, it says 'couldn't find website.' I can still post and stuff, just can't access telegrams, or issues, or anything like that.

[Again]

It's been up for me since my last post, but I could just be jinxing myself...

[Zakiristan]

Everything works for me except for the side bar, it says 'couldn't find website.' I can still post and stuff, just can't access telegrams, or issues, or anything like that.

me too

[Thafoo]

Everything works for me except for the side bar, it says 'couldn't find website.' I can still post and stuff, just can't access telegrams, or issues, or anything like that.

me too

Um, you can read the title, right?

"NO "ME TOO" POSTS"

[SalusaSecondus]

Everything should be working right now. I haven't fixed all of the root causes, but any problems which do occur should fix themselves in around 10 seconds.

[Erstaunlich]

Everything should be working right now. I haven't fixed all of the root causes, but any problems which do occur should fix themselves in around 10 seconds.

Thanks!

[Karputsk]

Will the update be finishing at a later time tonight? It didn't finish before the site crashed and looking at the World Assembly page/my reports it seems to have stalled.

[SalusaSecondus]

None of the problems should have impacted the daily update. I'll check out the logs.

[[violet]]

Everything should be working right now. I haven't fixed all of the root causes, but any problems which do occur should fix themselves in around 10 seconds.

Root cause should be fixed now.

[Rosko]

me too

Um, you can read the title, right?

"NO "ME TOO" POSTS"

me too

[Erstaunlich]

Um, you can read the title, right?

"NO "ME TOO" POSTS"

me too

meeeee tooooooooo

[Frisbeeteria]

me too

meeeee tooooooooo

You both can take a *** warning for spamming *** for that idiocy.

[Erstaunlich]

me too

meeeee tooooooooo

You both can take a *** warning for spamming *** for that idiocy.

I like idiocy, I just HAD to do that sorry...

[[violet]]

By way of explanation, the reason different people have been experiencing different results (i.e. it's down for one person, but up for another) is because we changed some DNS settings, which do not take instant effect but need to be picked up by everyone's ISPs. The ISPs do this at different times, so one person's ISP might be sending requests for "nationstates.net" to the old IP while another ISP's customers are being sent to the new one.

The reason for the DNS change is simply to increase site reliability. Which, obviously, isn't off to a flying start, since there was a misconfiguration.

False and false, sorry guys. The FB "fix" is what is causing the connectivity problem. [..] Taking into account the DNS propagation time, it is clear that the "unrelated topic" is actually the root of the problem. When I was working as webmaster, always the DNS changes gave problems when some portions of the net accessed the old config while some others accessed the new one.

REMOVE the FB "fix" and IN A FEW HOURS NationStates will work for everyone again. DNS propagation has a lot of inertia, it takes a long time to reach everywhere.

The Facebook fix didn't involve any DNS changes and isn't related to this issue.

[Erstaunlich]

By way of explanation, the reason different people have been experiencing different results (i.e. it's down for one person, but up for another) is because we changed some DNS settings, which do not take instant effect but need to be picked up by everyone's ISPs. The ISPs do this at different times, so one person's ISP might be sending requests for "nationstates.net" to the old IP while another ISP's customers are being sent to the new one.

The reason for the DNS change is simply to increase site reliability. Which, obviously, isn't off to a flying start, since there was a misconfiguration.

False and false, sorry guys. The FB "fix" is what is causing the connectivity problem. [..] Taking into account the DNS propagation time, it is clear that the "unrelated topic" is actually the root of the problem. When I was working as webmaster, always the DNS changes gave problems when some portions of the net accessed the old config while some others accessed the new one.

REMOVE the FB "fix" and IN A FEW HOURS NationStates will work for everyone again. DNS propagation has a lot of inertia, it takes a long time to reach everywhere.

The Facebook fix didn't involve any DNS changes and isn't related to this issue.

Oh that puts it clearer now, thanks...

[Rosko]

me too

meeeee tooooooooo

You both can take a *** warning for spamming *** for that idiocy.

Hey and what happened to humor on this site? Sorry, I guess.

[Sproctor]

You both can take a *** warning for spamming *** for that idiocy.

Hey and what happened to humor on this site? Sorry, I guess.

People were told multiple times not to add 'me too' to this thread. You did so purposefully when it was obvious the Mods weren't in the best of moods. It's like wearing red around a temperamental bull and wondering why it charged you. I sympathize with you about the humor, but there are times when humor isn't called for, you know, and arguing about it really doesn't get you anywhere. You just have to pick your moments better, that's all.

By way of explanation, the reason different people have been experiencing different results (i.e. it's down for one person, but up for another) is because we changed some DNS settings, which do not take instant effect but need to be picked up by everyone's ISPs. The ISPs do this at different times, so one person's ISP might be sending requests for "nationstates.net" to the old IP while another ISP's customers are being sent to the new one.

The reason for the DNS change is simply to increase site reliability. Which, obviously, isn't off to a flying start, since there was a misconfiguration.

False and false, sorry guys. The FB "fix" is what is causing the connectivity problem. [..] Taking into account the DNS propagation time, it is clear that the "unrelated topic" is actually the root of the problem. When I was working as webmaster, always the DNS changes gave problems when some portions of the net accessed the old config while some others accessed the new one.

REMOVE the FB "fix" and IN A FEW HOURS NationStates will work for everyone again. DNS propagation has a lot of inertia, it takes a long time to reach everywhere.

The Facebook fix didn't involve any DNS changes and isn't related to this issue.

Thanks, Violet.

[The Republic of Lanos]

Site's down around 8:59-9:00 PM CDT.

Edit: Back on.

[AETEN II]

So, much like several days ago, the non-forums went down for me again. I'm not sure if this is happening to everyone else or if there's already a thread reporting that the 'error' is back, but it just went down for a short bit and I'd thought it be best to inform the staff. Went down at 6:59-7:02 PM, pacific (California).

[Edward Richtofen]

Site's down around 8:59-9:00 PM CDT.

10:00 Eastern US time?

[Thafoo]

This still goes in the original thread.

/not a mod

[Thafoo]

Site's down around 8:59-9:00 PM CDT.

10:00 Eastern US time?

CDT: Central Daylight Time.