WordPress update
Just installed WordPress 2.5.1. Currently it’s just the Bootcamp 2008 blog only, but the others will follow – in due time. It’s just a matter of getting enough time to do all updates: In particulare MySQL to 5.1 – it should be more stable than 4.1 and the PHP MysQL4 engine is know to work with it. I’m only worried on the extra workload that it may impose on the system – memory usage is the big concern.
For a few weeks, I get this error on this version’s admin page:
Allowed memory size of 10485760 bytes exhausted (tried to allocate 11 bytes)
where the feed items were previously showing. No big deal, but the 2.5 blogs don’t have this problem. But instead, theer are more MySQL crashes, at least, so it seems.
Another thought: Could I put MySQL on a different machine? Or would that mean to push all the PHP stuff to another machine? It would mean the cluster should be up-and-running. And that’s where the failures are….
Updating the database means recreating the databases into MySQL 5.1, after, or before updating the blogs (which is very easy indeed: Just point to the right WordPress directory: [WP25] in stead of [WP233] for each logical :D. (hey Unix guys, ever seens an update that easy?) and running the admin script, as usual. (I’d do a load into MySQL 5.1 first and if that runs, update WP this way. If either one fails, the original is unspoiled and can be refererd to without a problem).
Windows woes
I kept Aphrodite – Thw Windows box – running fro a few days, doing nothing more than the SETI stuff. The Einstein@Home project won’t give me new work – the system isn’t up long enough???
But that wasn’t a good idea, it seems. It lost track of quite some things. Docking my camera on the USB port caused a hang in one system image (svhost – being one of those obscure functions with a lot of functionality that isn’t shown normally) leaving Explorer non-responsive, at least, consuming one of the two hyperthreads. WindowsXP isn’t clever enough to use the other one (running a very-low priority SETI task).
So I stopped this svhost task – and it was the one accessing the USB connection.
After that, I thought it wise to restart.
Well, it’s Windows, after all: In case of trouble: REBOOT. Oh well.