On 2007-06-22T17:33:39, Ben Clewett <[EMAIL PROTECTED]> wrote: > Dear Linux-ha, > > I have had terrible results from running V2.0.8 using the GUI.
Well, as frequently mentioned, the upstream 2.0.8 is a bit dated. However, your list of issues is fairly long. Quick inspection indicates that some issues have been addressed. For most of them though it's impossible to tell whether they are known, known and fixed, unknown or even possibly configuration issues. That means that instead of a long list of summary items, you should file independent bug reports with a complete description and logs each. Further, packages I'd suggest to use are either http://software.opensuse.org/download/server:/ha-clustering (if you want to remain on 10.1). Or, if you're using this in a production environment, you might be interested in purchasing SLES10 SP1. Not only does it come with prebuilt working packages, Dejan, Andrew and I get paid to fix any remaining bugs quickly. ;-) (That is not to say that the free downloads don't get fixed; it's essentially the same code. But, the attention shifts.) And yes, I'm not a big fan of the GUI either and wouldn't recommend it to configure a production cluster. Some very quick feedback: > 3. Often the Start, Stop and Refresh of resources does nothing. "Refresh"? What do you mean? > 4. The GUI reports different state from the physical state of the > servers. The tools reflect the logical, not the physical status. Physically, I assume all servers are present ;-) > 6. The 'Monitor' -> 'Restart' operation will return 'running', yet > heartbeat will still continually restart the resource after every start. > Only cured by a reboot. Hm? What is a Monitor->Restart operation? > 7. There seems absolutely no way of telling Heartbeat that if the ping > to the router fails, bring down the node. Not helped by some > documentation on the subject suggesting options that don't exist. Using pingd this is possible though. > 8. More than once a day Heartbeat will restart some or all resources > for no reason. Logs? > 9. The /etc/messages file reports so many warning and errors, many > hundred a minute, checking it is impossible. That almost certainly indicates a configuration error. > 11. Often the options the GUI displays are differ from what Heartbeat is > holding in memory. Hm? > 12. On a good clean compile of Heartbeat, the GUI is not installed. I'd not call that a clean compile then ;-) > 13. Refreshing a stale resource sometimes does nothing, again a restart. Hm? What do you mean? > 14. A monitor which fails sometimes restarts the wrong resource. The mind boggles at this idea. Do you have logs? Regards, Lars -- Teamlead Kernel, SuSE Labs, Research and Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
