[Samba] Samba4 AD DC using s3fs an OpenIndiana/Illumos/Solaris
rpenny at f2s.com
Thu Apr 11 06:22:57 MDT 2013
On 11/04/13 12:10, Henner Gratz wrote:
> I've just built my first samba4 (4.0.5) on an OpenIndiana machine
> without any problems.
> But when it comes to the provision step the problems begin. Everything
> is fine, if I
> call samba-tool with the --use-ntvfs option. But I want to use samba4
> with s3fs because
> of the support for newer SMB protocol versions.
> But when I call samba-tool without --use-ntvfs option I got the
> root at openindiana:~# /usr/local/samba/bin/samba-tool domain provision
> Realm: domain.local
> Domain [domain]:
> Server Role (dc, member, standalone) [dc]:
> DNS backend (SAMBA_INTERNAL, BIND9_FLATFILE, BIND9_DLZ, NONE)
> DNS forwarder IP address (write 'none' to disable forwarding)
> [184.108.40.206]: none
> Administrator password:
> Retype password:
> ERROR(<class 'samba.provision.ProvisioningError'>): Provision failed -
> ProvisioningError: guess_names: 'realm=WIWI.LOCAL' in DOMAIN.LOCAL
> must match chosen realm '/usr/local/samba/etc/smb.conf'! Please
> remove the smb.conf file and let provision generate it
> line 398, in run
> use_rfc2307=use_rfc2307, skip_sysvolacl=False)
> line 1978, in provision
> sitename=sitename, rootdn=rootdn)
> line 597, in guess_names
> raise ProvisioningError("guess_names: 'realm=%s' in %s must match
> chosen realm '%s'! Please remove the smb.conf file and let provision
> generate it" % (lp.get("realm").upper(), realm, lp.configfile))
> I know that samba uses POSIX ACLs while OpenIndiana/ZFS uses NFSv4
> ACLs, but I hoped
> that there is a way to configure samba4 to work with s3fs on Solaris
> machines as well.
> Unfortunately I wasn't able to find anything about this topic with
> google and friends.
> Does somebody on this list know more about it?
> Thank you very much for any advice in advance!
Hi, did you provision it first with --use-ntvfs ? if you did, do you
have /usr/local/samba/etc/smb.conf ?
If you do, then do what the error message is telling you, remove or
rename smb.conf and try provisioning again.
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the samba