I found a work around. Like the gentleman with the mysql service problem a while back, I edited /etc/init.d/named on both nodes such than named stop returns 0, even though named is already stopped. I'm not smart enough, yet, to figure out why that works, but it does. On Thu, 2006-03-16 at 07:22 -0800, Philip R. Dana wrote: > We have a two node active/passive cluster running bind as our master DNS > server. Shared storage is iSCSI on a NetApp Filer. The OS is CentOS 4.2. > Whenever the rgmanager service on the passive node is started/restarted, > the service resource on the active node fails in that named itself is > shut down. The only way to recover, as near as I can tell, is to set > autostart=0 in cluster.conf, reboot both nodes, then manually start the > service on one of the nodes. Is this by design, or an "undocumented > feature"? > Any help will be greatly appreciated. TIA. > > -- > > Linux-cluster@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
