On 04/30/2012 05:42 PM, Dimitri Maziuk wrote: > On 04/30/2012 05:04 PM, Seth Galitzer wrote: >> This was a bit trickier to get worked out, but I have made some >> progress. It turns out just putting the metadata on a shared disk >> resource and symlinking wasn't quite enough. nmbd (the netbios >> management daemon that samba uses) complained that the symlink to its >> working directory wasn't a real directory. > > Why not use your AD controller (or whatever they call it) to be browse > master and netbios name server?
As I understand it, nmbd needs to be running on the samba host so that it can respond to netbios/cifs queries. I've not yet found a way to separate the two. > >> The other new oddity is that after I've put the primary into standby and >> everything has failed over to the secondary, as soon as I bring the >> primary back online, the resources try to switch back, i.e. they don't >> stay on the secondary (new primary) as expected. > > As I recall clusters from scratch have a paragraph on that. (Basically, > it's configurable, it may be desirable if e.g. you're using a > low-powered back-up node.) > > (I can't be more specific because I'm using "R1" configs here, not crm.) > > Per another post, I was able to resolve this by setting the "resource stickiness" value for the group. Thanks. Seth -- Seth Galitzer Systems Coordinator Computing and Information Sciences Kansas State University http://www.cis.ksu.edu/~sgsax [email protected] 785-532-7790 _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
