The CAA/MySQL has not been proven solved, but we have disabled niffd on
the affected clusters, and the problem has not come back yet, so it
looks like it *may* have been niffd rearranging the routing on the
cluster for no readily apparent reason.
I'd rather have a had a more definite smoking gun, but I'll just have
to keep an eye on things.
Tim
--
Dr Tim Cutts
Informatics Systems Group, Wellcome Trust Sanger Institute
GPG: 1024D/E3134233 FE3D 6C73 BBD6 726A A3F5 860B 3CDD 3F56 E313 4233
Received on Mon Mar 21 2005 - 17:43:44 NZST