This post originated from an RSS feed registered with Python Buzz
by Phillip Pearson.
Original Post: pycs.net, still broken
Feed Title: Second p0st
Feed URL: http://www.myelin.co.nz/post/rss.xml
Feed Description: Tech notes and web hackery from the guy that brought you bzero, Python Community Server, the Blogging Ecosystem and the Internet Topic Exchange
Argh - just logged in to the server to find that the pycs.net process has used 1338 minutes (just over 22 hours) of CPU time since Friday, and that it was currently sucking 97% CPU. Ouch. Sorry to all the other users of the JohnCompanies FreeBSD box it's been abusing.
It looks like something is causing MetaKit (the database) to spin while trying to access something. Definitely what happend ages back. At that time, it was the comment database that was all screwed up. Nowadays, PyCS stores a lot more data in there, so it could be anything -- user data, referrer info, comments, trackbacks, access rules, etc.
I'm going to pick up my MetaKit database compaction script from the other day and get it to look a bit deeper into the database, and actually copy each bit of data separately. I suspect that picking up a row and dropping it another file was just copying bytes from DB to DB rather than redoing the structure. Let's see.
Previous Topic
