After commenting out the "passdb pam" section and uncommenting
"passdb
ldap", with the "args = /etc/dovecot-ldap.conf", the syslog
messages
went completely away, and everything continued to work.
I just thought I would mention it in the event that anyone else was
seeing similar problems in the future. :)
-Rich
> > (I sent this last night, but to the wrong address.. argh)
> > After an upgrade to FC5, and a rebuild and install of dovecot 1.0RC7,
> > I've been getting a LOT of syslog messages like the following:
> > Sep 26 21:47:55 myhost dovecot-auth: nss_ldap: reconnected to LDAP
> > server ldap://ldap.mydomain.com after 1 attempt
> >
> > Now, everything is working fine as far as I can tell (it's only
been a
> > rocky day since the upgrade.. and that was littered with other LDAP
> > related problems), but I was wondering why it was even using
> > nss_ldap... I have dovecot configured to connect to LDAP directly.
> >
> > My dovecot.conf contains:
> > auth default {
> > # Space separated list of wanted authentication mechanisms:
> > # plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi
> > mechanisms = plain
> > ...
> > passdb pam {
> > }
> > ...
> > # LDAP database
> > #passdb ldap {
> > # Path for LDAP configuration file, see doc/dovecot-ldap.conf for
> > example
> > #args > > #}
> > ...
> > # LDAP database
> > userdb ldap {
> > # Path for LDAP configuration file, see doc/dovecot-ldap.conf for
> > example
> > args = /etc/dovecot-ldap.conf
> > }
> >
> > And I am wondering if I missed something obvious here...
> >
> > I'm going to try commenting out the "passdb pam"
section, uncommenting
> > the "passdb ldap" section and see if that allows for
everything to go
> > directly to LDAP (and not rely on nss_ldap or pam_ldap).
> >
> > -Rich
> >
>