On 4/13/12 7:18 PM, William Seligman wrote: > On 4/13/12 6:42 PM, Seth Galitzer wrote: >> In attempting to build a nice clean config, I'm now in a state where >> exportfs never starts. It always times out and errors. >> >> crm config show is pasted here: http://pastebin.com/cKFFL0Xf >> syslog after an attempted restart here: http://pastebin.com/CHdF21M4 >> >> Only IPs have been edited. > > It's clear that your exportfs resource is timing out for the admin resource. > > I'm no expert, but here are some "stupid exportfs tricks" to try: > > - Check your /etc/exports file (or whatever the equivalent is in Debian; "man > exportfs" will tell you) on both nodes. Make sure you're not already exporting > the directory when the NFS server starts. > > - Take out the exportfs-admin resource. Then try doing things manually: > > # exportfs x.x.x.0/24:/exports/admin > > Assuming that works, then look at the output of just > > # exportfs > > The clientspec reported by exportfs has to match the clientspec you put into > the > resource exactly. If exportfs is canonicalizing or reporting the clientspec > differently, the exportfs monitor won't work. If this is the case, change the > clientspec parameter in exportfs-admin to match. > > If the output of exportfs has any results that span more than one line, then > you've got the problem that the patch I referred you to (quoted below) is > supposed to fix. You'll have to apply the patch to your exportfs resource.
Wait a second; I completely forgot about this thread that I started: <http://www.gossamer-threads.com/lists/linuxha/users/78585> The solution turned out to be to remove the .rmtab files from the directories I was exporting, deleting & touching /var/lib/nfs/rmtab (you'll have to look up the Debian location), and adding rmtab_backup="none" to all my exportfs resources. Hopefully there's a solution for you in there somewhere! >> On 04/13/2012 01:51 PM, William Seligman wrote: >>> On 4/13/12 12:38 PM, Seth Galitzer wrote: >>>> I'm working through this howto doc: >>>> http://www.linbit.com/fileadmin/tech-guides/ha-nfs.pdf >>>> and am stuck at section 4.4. When I put the primary node in standby, it >>>> seems that NFS never releases the export, so it can't shut down, and >>>> thus can't get started on the secondary node. Everything up to that >>>> point in the doc works fine and fails over correctly. But once I add >>>> the exportfs resource, it fails. I'm running this on debian wheezy with >>>> the included standard packages, not custom. >>>> >>>> Any suggestions? I'd be happy to post configs and logs if requested. >>> >>> Yes, please post the output of "crm configure show", the output of >>> "exportfs" >>> while the resource is running properly, and the relevant sections of your >>> log >>> file. I suggest using pastebin.com, to keep mailboxes filling up with walls >>> of >>> text. >>> >>> In case you haven't seen this thread already, you might want to take a look: >>> >>> <http://www.gossamer-threads.com/lists/linuxha/dev/77166> >>> >>> And the resulting commit: >>> <https://github.com/ClusterLabs/resource-agents/commit/5b0bf96e77ed3c4e179c8b4c6a5ffd4709f8fdae> >>> >>> (Links courtesy of Lars Ellenberg.) >>> >>> The problem and patch discussed in those links doesn't quite match what you >>> describe. I mention it because I had to patch my exportfs resource (in >>> /usr/lib/ocf/resource.d/heartbeat/exportfs on my RHEL systems) to get it to >>> work >>> properly in my setup. -- Bill Seligman | Phone: (914) 591-2823 Nevis Labs, Columbia Univ | mailto://[email protected] PO Box 137 | Irvington NY 10533 USA | http://www.nevis.columbia.edu/~seligman/
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
