Shibboleth Developers

["Scott Cantor" <>]

Speaking of error handling, first real problem cropped up here, in the MySQL
cache. We have some problems in the cache calls right now, we seem to be
bizarrely assuming that cache inserts always succeed. Umm, not.

Some looping occurs because we don't trap problems, or even report them in
some cases. The SQL table corrupted itself somehow, and the cache plugin
isn't even reporting the failure.

This is all easy to fix, this should trap out as a fatal error, obviously.

My bigger concern is why it corrupted itself after running fine for weeks. I
wasn't a MySQL fan before this, so I'm not exactly shocked, but it still
pisses me off. ;-)

Anyway, I dunno if I can get a copy of the corrupted table, but I wanted to
see if it's possible to run MySQL repair tools on them. I guess it might be
worth it to actually detect the errno in question (145) and run a REPAIR
command.

-- Scott