I just started having odd issues with CAA services on my cluster, or one
service in particular. Placement is specified in the config for the service.
If I do a caa_start or caa_stop from my other cluster member, it fails -- or
at least reports failure, but looking at the other node shows the script
still running to start it up and when the script is no longer running, caa_stat
reports that the service is running.
Is there anything that could cause this behavior that anybody knows of?
-Charlie
Received on Sun Aug 29 2004 - 16:26:00 NZST