On Fri, May 04, 2007 at 02:01:24PM -0500, Dave Dykstra wrote: > On Thu, May 03, 2007 at 09:19:33AM -0600, Alan Robertson wrote: > > Martijn Grendelman wrote: > > > Hi, > > > > > > I am trying to build a 2-node cluster serving DRBD+NFS, among other > > > things. It has been operational on Debian Sarge, with Heartbeat 1.2, but > > > recently, both machines were upgraded to Debian Etch, and today I > > > upgraded Heartbeat to 2.0.7. I maintained the R1 style configuration. > > > Heartbeat is running in an active/passive fashion. > > > > > > All is running fairly well, but there is one problem that I can't seem > > > to find the cause of. When a failover occurs, all resources on the > > > active node are released, including NFS: > ... > > > Now, _most_ resources are started on the other node, but not NFS. This > > > is written to syslog: > ... > > > but 'nfs-kernel-server' is never started. DRBD, the fs-mount, mysql, > > > etc. are all ok, just not NFS. And there is not a single reference to > > > 'nfs-kernel-server' in the syslog, after the line quoted above. > > > > > > Any clue as to what may cause this, is very welcome! > > > > > > Some config information: > > > 'haresources' is identical on both nodes: > > > > > > [EMAIL PROTECTED]:~> cat /etc/ha.d/haresources > > > vodka 213.207.104.20 \ > > > ipvsadm \ > > > mon \ > > > drbddisk::all \ > > > Filesystem::/dev/drbd0::/extra1::ext3 \ > > > nfs-kernel-server \ > > > Delay::3::0 \ > > > IPaddr::10.50.1.20/32/eth0 \ > > > mysql > > > > > > [EMAIL PROTECTED]:~> cat /etc/ha.d/haresources > > > vodka 213.207.104.20 \ > > > ipvsadm \ > > > mon \ > > > drbddisk::all \ > > > Filesystem::/dev/drbd0::/extra1::ext3 \ > > > nfs-kernel-server \ > > > Delay::3::0 \ > > > IPaddr::10.50.1.20/32/eth0 \ > > > mysql > > > > > > Please let me know if more information is needed. > > > > We run /etc/init.d/nfs-kernel-server status before starting it. If it > > says OK or running, then we don't start it because it's already running. > > > > See http://linux-ha.org/HeartbeatResourceAgent > > > And of course /etc/init.d scripts don't support a 'status' parameter. > You really need to write your own /etc/ha.d/resources script. > I don't quite understand why heartbeat can't skip the status checks > for /etc/init.d scripts. Either that or it shouldn't claim to support > /etc/init.d scripts.
How should a cluster work without being able to check the status of resources? > > - Dave > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems -- Dejan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
