Server Rebooted.

Apologies, I don’t get much time to warn about impromptu reboots these days, mostly because I only get to work on the server in the evenings. Anyway, I rebooted the server with the new Linux kernel version installed. This new one has various kernel semaphore fixes which should improve the SMP (dual processor) capability. And in theory, that and the new MySQL binaries from TCX should fix the lockups and excessive ‘Temporary Failure’ messages.

I shall, however, try to keep my eye on it for the next little while…


MySQL Update

It actually appears I was unfair to MySQL, after scouring the net I have discovered that its probably a glibc problem. I won’t explain that one, you either know what I mean or you don’t :-)

Anyway, I’ve installed a new version of MySQL which has built-in glibc routines which reportedly will fix the problem. However, there’s also issues with Linux 2.4.3 (as I suspected) which upgrading to the latest Linux kernel should fix.

I shall be trying that this evening.

More news as we know it.



Test on new version of MySQL

Advice Required

It would seem the MySQL is an unreliable heap of junk. I’m bored of fightíng it. If anyone has any suggestions (other than Postgres which flat refuses to run with our schema) of decent priced, but reliable databases I’d like to hear about it.

MySQL bit it again this evening, and once again couldn’t even be killed by a kill -9 (which to be honest stinks to me of a Linux kernel bug, but since neither side will admit it, we’re stuck). And they wonder why corporates won’t use Linux seriously.

Well, I’d like to say we’re looking into it, but frankly, I’m out of ideas.


Spurious comment error

It seems that the adult verification system caused an unexpected side effect. In order to remember which diary you were visiting when you hit a page that needs an adult ID, we store the diary name in a cookie.

Unfortunately, by default, PHP (which the new secure comments system is written in) reads cookies and automatically assigns variable names to them, as one of the last places it takes information from. I used the keyword diary in the cookie. Matt used the keyword diary in the PHP script. As such, it was possible, if you started adding a comment, then went to someone elses diary before actually saving your comment, that you could end up posting the comment to a non existant diary! The fact that it was nonexistant was purely down to the fact that I saved the diary as a string and Matt used it as a number…

This is now fixed, please let us know if you still experience comment issues.