Hi all I think that I have got this one sorted, simply replicate the tbd files from the primary (working) node across to the secondary node and restart the SMB and winbind services, once done both nodes will have the same database of AD -> UNIX accounts
this probably calls for a cron job to keep it in sync on my redhat system: scp /var/lib/samba/*.tdb secondary:/var/lib/samba/ ssh secondary "service smb restart && service winbind restart" now I am sure that this is not the best way of doing this and am still hoping that someone can tell me how to store the tdb files on the shared resource? Thanks Jay 2009/2/25 Jason Fitzpatrick <[email protected]> > Hi all > > I have a wee puzzle for you. > > I have a 2 node cluster running DRBD to share out a volume that is used for > hosting a SAMBA share (Using ADS to query AD for account information), both > nodes of the cluster have been joined to AD and are testing fine (able to > add AD accounts to the share / connect from windows clients etc) > > my problem is this, after setting permissions on the share and failing the > cluster over to the 2ndary node the permissions on the shares are reset to > different user accounts, when I fail back the permissions all go back to the > way that they should be. > > I have to assume that this is due to the way that winbind maps AD accounts > to the local Unix ones, and the lists that are hosted on the different > servers do not seem to be in sync. > > has anyone come across this before? is it possible to store the winbind > configuration on the shared resource so that the same mapping is used on all > nodes on the cluster? > > I know that this is not realy the form for winbind / samba / ADS issues, > but I recon that this is the only place that people would have run into this > type of an issue. > > thanks a mill > > Jason > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
