Package: samba
Version: 3.0.14a-3sarge1
Severity: minor
While trying to get a samba server set up via ldap, I ran in to the case
where smbd would apparently start successfully but then exit without any
messages of any kind and nothing in the log.smbd file.
1) The first problem was I had:
; LDAP settings
ldap admin dn = "uid=samba,ou=Services,dc=precidia"
ldap suffix = "dc=precidia"
ldap user suffix = "ou=People"
ldap group suffix = "ou=Groups"
ldap idmap suffix = "ou=Idmap"
ldap machine suffix = "ou=Hosts"
ldap replication sleep = 1000
ldap password sync = true
ldapsam:trusted = true
This would cause "invalid DN" errors from the ldap server. I had to use
strace and tcpdump to figure out that there shouldn't be any quotes here.
2) The second problem I had was missing "sambaSID" values in the groups
in my directory. Once I added these, the smbd daemon kept running.
Just to reiterate... These were all mistakes on my part. My bug
concerns only that samba reported _nothing_ and left me to find these
problems with tools like strace and tcpdump -- not the most
user-friendly methods of debugging.
It occurred to me later that I should have increased the logging level.
I think fatal errors should always get logged, though.
Brian
( [EMAIL PROTECTED] )
-------------------------------------------------------------------------------
Until we are first independent, we cannot be interdependent.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
