Author: peter

Posted on

Be Thankful

Wow, oh wow what a trip the last day has been.
So, I had dinner plans last night, and they were immediately complicated by the fact that I locked myself out of my office. No cell phone, but fortunately I had my wallet with me, so I could still get food, which is good, because I had been told about this place and the ranting and raving alone were enough to make me drool. It would have been a real letdown if I couldn’t buy dinner. Continue reading “Be Thankful”

Posted on

RT 3.8.0 – Stable Again Thanks To InnoDB

Thanks to a couple of helpful folks on the rt-users mailing list, we were able to track down the cause of our problems. We experienced some corruption in our MySQL databases. I found out that you should “never” run RT on MyISAM tables and always use InnoDB. Oddly enough, we’ve run on MyISAM for years and never had this problem. However, we did have issues with slownes, for years, and it’s something we’ve been struggling with constantly.
for t in $(mysql -unotreal -pdontbother --batch --column-names=false -e "show tables" rt3);
do
mysql -e "alter table $t type=InnoDB" rt3;
done
Running this script revealed an error with the “Tickets” table.?Fortunately, the data itself in our tables was not corrupt, just the indexes were. ?myisamchk was able to repair these and allow us to convert all tables to InnoDB format. Once I fixed that error, I was able to convert everything over to InnoDB.
I was thrilled to see that, once the conversion was finished, RT popped right back up into place, with all of the tickets in their usual spots. And, as a bonus, the thing’s a lot faster than it ever was before.
Lesson learned. Next time, read the instructions more carefully.

Posted on

WordPress 2.6.1 Upgrate

I just ugpraded to WordPress 2.6.1, following my usual procedure (backup, download, extract over existing blog). I got some errors when I clicked to update the database:
WordPress database error: [Duplicate key name 'comment_approved']
ALTER TABLE nikolaidis_wp_comments ADD KEY comment_approved (comment_approved)

WordPress database error: [Duplicate key name 'type_status_date']
ALTER TABLE nikolaidis_wp_posts ADD KEY type_status_date (post_type,post_status,post_date,ID)
Upgrade Complete

Your WordPress database has been successfully upgraded!

Given the last line, I’m inclined to think that these database upgrades may have been done in the 2.6 upgrade I did a while back.
At least, that’s my hope…

Posted on

RT 3.8.0 Server is Hosed After Corrupt Sessions Table, myisamchk

To all of my regular readers, apologies if this post seems a bit out of the ordinary, but if you read on, you’ll see why I’m documenting this here, as opposed to in my ticketing system.

On Friday afternoon, for no apparent reason, while I was the only user on my RT 3.8.0 system, after clicking a link, I was presented with the logon prompt.
Puzzled, I entered my username and password and logged back in. Everything seemed normal, and the ticket I was trying to edit was there. I continued my edits, and clicked to update the ticket.
Login prompt again. Continue reading “RT 3.8.0 Server is Hosed After Corrupt Sessions Table, myisamchk”