Karl Podesta wrote: > On Tue, Feb 19, 2008 at 09:43:03PM +0100, Pavlos Parissis wrote: >> It would be much better and useful for everyone to post your clutser.conf and the error you get. >> >> You can always test your configuration prior using it by using rg_test tool. >> >> Cheers, >> Pavlos > > Ok - I make the change in cluster.conf (see below), then do: > > ccs_tool update /etc/cluster/cluster.conf > cman_tool version -r 68 > > ... this works fine, no errors. Clustat reports cluster working as normal, > no messages in /var/log/messages etc. But then when I enter system-config- > cluster, I get a window with an error telling me it can't read the config > file (error is below). Any help you can give is appreciated! Or even if > you'd recommend something different to allow tolerance for heartbeats. > > Incidentally - it appears deadnode_timeout isn't a variable in the cman > section in the RHEL 4 cluster.conf schema: > (http://sources.redhat.com/cluster/doc/cluster_schema_rhel4.html) > ... so maybe deadnode_timeout isn't a valid variable anymore? > deadnode_timeout is a valid variable in RHEL4. It just seems that system-config-cluster (at least your version of it) doesn't like it :( The way to check it has been honoured is to cat /proc/cluster/config/cman/deadnode_timeout and see if it has the right value. -- Chrissie -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
