The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
Error 500 Mainsite.
GiantRobo
Registered User regular
Registered User regular
Yeah, can't view it, forums act fine for me though.
GiantRobo on
0
Posts
I'll report back if I hear more info on what is going on with it.
pages come back sporadically. sometimes they return a 503, sometimes a 500, occasionally the comics page works but then fails. probably need to bounce whatever lighttpd is using to serve the dynamic content... fastcgi cluster? tomcat perhaps?
Sorry, that's what I meant when I said, "Acknowledged".
To clarify, I have no purview over the "mainsite" but I have the contact info of the people who do (people like the illustrious alphamonkey who was up late last night getting us setup here (yay!) and is probably now snoozing, unfortunately(boo!))
I had not heard any news that the mainsite would be moving as well last night. It was already on servers isolated from the forums as far as I know and it was not having the pressing performance problems that we were having, so I'm a bit surprised to find it unavailable this morning.
It didn't. The mainsite moved over a while ago and does indeed run on separate servers, so the performance you see here is the real deal.
i'm curious why if ruby was sucking up all the ram and spinlocking, we didn't see some sort of hang or timeout? we just got a 500 or 503 immediately. did you hit max connections for ruby while it was spinning, or did the servers just fall over and your proxy decided not to connect to them anymore?
i admit i don't have enough experience with lighttpd to know what its full capabilities are here. usually i use apache, perl/php/java and mysql/oracle, and some apps are written poorly so when database connections fall over the childs just sit there soaking up connections and memory and never re-connecting to the db or providing anything useful to the client
My solution is to roll a different webserver, but that isn't a trivial conversion.
yikes! i haven't heard of that before, and we use it in a pretty high traffic fashion but for serving content right off the lighttpd box, no proxies (apache for proxies & most dynamic content; we're old-school). honestly if you've looked through the lighttpd code it's quite hairy. i wrote a patch so we could specify max-age longer than an unsigned int, ughhh.... i might prefer hacking apache!
Same thing here
PSN ID : DetectiveOlivaw | TWITTER | STEAM ID | NEVER FORGET
http://www.penny-arcade.com/comic/2002/02/01
I won't live in a world where Penny Arcade doesn't work!
forums and main website aren't hosted on the same boxes
Thirded.
and working ok now (3/29)
The other interesting thing is that that navigation buttons all point to an IP address-based link instead of a link with a domain name in it (except for the RSS feed link).
Front page just messed up again for me, as of 7:29 CDT 3/30.
WTF is happening?
"Oh what a day, what a LOVELY DAY!"
technically speaking.
it is this:
so no eta?
of course right after I write that I go check and it's fine.
of course it was fine for a while on sunday too.