The scoop for the record
I figured i’d log what was going on with my blog should someone else hit the problem… The basic problem was a few weeks or a month ago I started getting failures when using ecto to post to my blog. The failures showed up in an ecto error dialog as this:
Parsing Failure!
Could not parse response for “metaWeblog.editPost”. Please check the console log for more information.
Upon inspecting the log I saw this in the console:
500 Internal Server Error
Internal Server Error
The server encountered an internal error or
misconfiguration and was unable to complete
your request.Please contact the server administrator,
xxx@swimfinssf.com and inform them of the time the error occurred,
and anything you might have done that may have
caused the error.
This stimyed me as the message basically told me nothing about what actually failed… I found a few posts indicating that it might be a file permissions problem on the server so I fixed permissions on every file I could find but that did nothing… I searched and searched and searched and finally thought to look in the server log itself… Server log contained this error
Out of memory!
Callback called exit at mt.cgi line 11.
BEGIN failed–compilation aborted at mt.cgi line 11.
[Fri Jan 6 08:04:04 2006] [error] [client 71.139.13.81] Premature end of script headers: /home/swimfins/swimfinssf.com/mt/mt.cgi
Looking at mt.cgi didn’t tell me anything - that line in the source is the ‘run the blog’ line (i.e. all of MT was run in that line so it didn’t help at all… So then I started googling again. This time I came upon a lone sparse article which indicated that this was caused by the server process running out of memory when trying to access the Berkeley DB databases I was using to store entries. The article indicated that I should switch to MySQL which I did.. and BINGO.. worked like a charm and increased the speed of MT at the same time…
Anyway.. not super interesting but I wanted to post it should some one else start googling after seeing the same errors. Hope it helps someone.
Happy hacking
2 Comments to The scoop for the record
Keep up the great work on your blog. Best wishes WaltDe
You were right, I came here googling for this error. Thank you for posting. The problem is that I am a blogger user, and I don’t know what to do.
If you were aware of some solution for Blogger users, I would appreciate very much a simple mail.
Thank you again.
Leave a comment
Tweets
- homeward bound on the shuttle... got a pile of things to do tonight and not enough hours before bed time 3 days ago
- Just plugging away at a million different things. usual work day grind as I look out at the sun.. is it too early for a beer? 3 days ago
- New blog post: Labor Day Hike http://tinyurl.com/6zc4f7 5 days ago
- New blog post: The Bay http://tinyurl.com/6adbvn 6 days ago
- The Bay http://is.gd/26hq 6 days ago
- More updates...
Posting tweet...
Powered by Twitter Tools.
Search
Categories
Archives
My Buddies
Tags
apple audi auto blog california cancer coworkers dog ellen facebook family friends gay geek Giggles gltb grammar hrc kevin lymphoma mccain media missing person movies nina north carolina pennsylvania physics Politics random religion sawyers service site social networking sprichwörter support travel video viszsla vizsla washington dc weekend wordpress workRecent Comments
- Katie Farrell on Hypocrisy
- MJ on Some cool
grafitiArt from Kevin - Katie Farrell on The Birthday Girl
- Katie Farrell on My work day
- clem & brian on a note from the frey











August 31, 2006