Clustering mystery still ghosting and byting. Now with a tester that is much refined that fetches both front-end (and simply mentions it is delivered the wrong node) and back end (and stops if the back-end does not show the expected values).
This refined tester is the only tool we have thus far to test failed cluster synchronization after a restart. Our last deployment on Tuesday required us 25 restarts to get in sync, about 15 of them were done with this tester which failed in several different ways, particularly login.
paul