aggregated thinking

i've had this happen to me again the other week and as always, felt like kicking myself for not remembering. we do a lot of performance tuning on mysql, and as a result, we almost always manage to get plesk mangled. not its fault, it just can't run without mysql, doh. not of preference, but plesk happens to be there to make handling domains easier, as a single editing point when you want to change something and not worry about missing something out. so there's a custom /etc/my.cnf that we use, and with changes to limits done (both on mysql and via ulimit), you'd think that a reload of mysqld would do. (we use InnoDB btw) normally, that's all you need to have mysqld read off the new settings. if you've grown so dependent on plesk (like i have), you would not notice that mysqld didn't actually start, and you will get an error when you load plesk, thinking that it's a plesk error: ERROR: PleskMainDBException MySQL query failed: Incorrect information in file...

i don't know with you, but i sometimes get the big push to update, if and when there's something new (relatively, for me) to try. up for this week is my dabbling with stuff around kicker, and using kblogger to do some much needed updates.