I keep getting this error as i try to post to Rhymes With Right. Can anybody tell me what is going on, and whetehr the problem is on my end or at the server?
Updated by Pixy: AAAARGH!
(Sorry, I'm at work and we're having major computer problems here right now. Give me an hour and I'll be back.)
(At least that worked.)
(In fact, it seems much better now.)
(Let me know if you have any more problems. I blocked a spam/ping flood attack, which might have been causing the problem, but I'm not sure that was it.)
(There's still some worthless excuse for an organic life-form trying to DoS us, but he's too stupid to have any significant effect.)
(Test test.)
(Test some more.)
Posted by Greg at July 3, 2005 11:14 PM | TrackBackThat's a server error, but as far as I know the server is okay. Let me check.
Posted by Pixy Misa at July 3, 2005 11:27 PMI was able to make (and then delete) a test post on your blog. Are you still getting the error?
Posted by Pixy Misa at July 3, 2005 11:31 PMI'm getting the same error intermittently, but more no than go.
Posted by Ted at July 3, 2005 11:33 PMHere's the message I'm getting:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@blog.mu.nu and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache/1.3.33 Server at www.blog.mu.nu Port 80
Still getting it -- in particular on the one entitled "Does That Star-Spangled Banner Yet Wave?
Posted by Greg at July 3, 2005 11:43 PMHey!
I'm still getting that error. The only way I can post is to try to save, then rebuild. But, when I do it that way, I can't ping anyone.
I've been having that problem all day.
; )
Thank you!
Posted by Christina at July 4, 2005 01:02 AMHey, I just got one too! Just from posting a comment! 
Still getting it with my latest post, though the rebuild lets it through without notifying my trackback sources.
Posted by Greg at July 4, 2005 02:02 AMOkay, I've restarted the web server, now I'm going to try another test post.
Posted by Pixy Misa at July 4, 2005 02:03 AMI was able to post one entry but my 2nd got this error. No matter if I just tried to save or publish, I got this.
Posted by Sissy at July 4, 2005 02:05 AMIf you click save or publish a couple of times, it'll save it that many times. If you then rebuild, it'll publish (and if you happened to publish it 3 times and got the error, it'll be on your site 3 times)
Hope that info helps...
Posted by Sissy at July 4, 2005 02:10 AMIs it also direly slow for everyone?
Just reading blogs is fine; posting comments is okay, but posting entries is slooooooooooooow.
Posted by Pixy Misa at July 4, 2005 02:23 AMI'm going to restart the MySQL server now.
No idea if that's the problem, but it's not the web server, so...
Posted by Pixy Misa at July 4, 2005 02:26 AMOkay, I can see there are still 500 errors coming up.
Still working on it.
Posted by Pixy Misa at July 4, 2005 03:49 AMJust smacked another idiot with a stick. Let's see if that helps.
Posted by Pixy Misa at July 4, 2005 03:54 AMI just got a comment and a test post to post, so it seems to be... okay.
(Kinda hesitant to say that right out. Didn't wanna jinx anything...)
I'll keep an eye on it.
It was a combination of denial-of-service attacks causing the problem. Bah.
Posted by Pixy Misa at July 4, 2005 04:41 AM