I've noticed a 500 error:"internal server error" message at times when browsing the site.

Yeah, that happens a lot. Dunno why, though.

There's one or two a day that result from the site being updated. Those are generally scheduled for when the site is least busy.
Most, occur when the site is really busy, these are recognizable as just temporary problems that go away after a few minutes. These, I think are supposed to be 503 errors, but that code got ripped out by the previous administration.
Rarely, there is a real problem, one that lasts hours or days, these need to be reported to the bug tracking site (see the sticky forum thread).
Don't take this as set in stone, my memory may not be 100% accurate.

Well... You see, here you can read why they occur. They mostly happen to me at night (8:00Pm - 2:00Am GMT-8)

I hate silent 500 errors, when I'm changing tags by tag script, and when refreshing page I discover that some of changes weren't done. T_T

Gilda_The_Gryphon said:
I hate silent 500 errors, when I'm changing tags by tag script, and when refreshing page I discover that some of changes weren't done. T_T

Had this happen sometimes as well. =>.<=

edidaf said:
There's one or two a day that result from the site being updated. Those are generally scheduled for when the site is least busy.
Most, occur when the site is really busy, these are recognizable as just temporary problems that go away after a few minutes. These, I think are supposed to be 503 errors, but that code got ripped out by the previous administration.
Rarely, there is a real problem, one that lasts hours or days, these need to be reported to the bug tracking site (see the sticky forum thread).
Don't take this as set in stone, my memory may not be 100% accurate.

on the nose :)
btw, next update is bringing back good old 503. I'd rather not have the site chug along for 14 seconds then break down. if it's straining, it'll let you know. (and to wait 15 seconds and refresh)

Aurali said:
on the nose :)
btw, next update is bringing back good old 503. I'd rather not have the site chug along for 14 seconds then break down. if it's straining, it'll let you know. (and to wait 15 seconds and refresh)

That would be much preferable, because every time this site starts chugging, I have to open another site to make sure it isn't a failure on my end. Quick failures are the best failures.