Problem with Postfix connecting to LDAP

[jayk]

Here is a snippet of what I'm experiencing from my log files:

Code:

Aug 15 07:03:53 mainsrv postfix/trivial-rewrite[10751]: warning: database /etc/postfix/relocated.db is older than source file /etc/postfix/relocated
Aug 15 07:03:53 mainsrv postfix/trivial-rewrite[10751]: warning: dict_ldap_connect: Unable to bind to server ldap://127.0.0.1:389 as cn=nobody,cn=internal,dc=lubecorp,dc=ws: 49 (Invalid credentials)
Aug 15 07:03:53 mainsrv postfix/trivial-rewrite[10751]: warning: dict_ldap_connect: Unable to bind to server ldap://127.0.0.1:389 as cn=nobody,cn=internal,dc=lubecorp,dc=ws: 49 (Invalid credentials)
Aug 15 07:03:53 mainsrv postfix/trivial-rewrite[10751]: warning: dict_ldap_connect: Unable to bind to server ldap://127.0.0.1:389 as cn=nobody,cn=internal,dc=lubecorp,dc=ws: 49 (Invalid credentials)
Aug 15 07:03:53 mainsrv postfix/trivial-rewrite[10751]: fatal: ldap:/etc/postfix/ldapdistlist.cf(0,lock|fold_fix): table lookup problem
Aug 15 07:03:54 mainsrv postfix/master[10628]: warning: process /usr/lib64/postfix/trivial-rewrite pid 10751 exit status 1
Aug 15 07:03:54 mainsrv postfix/master[10628]: warning: /usr/lib64/postfix/trivial-rewrite: bad command startup -- throttling
Aug 15 07:03:54 mainsrv postfix/qmgr[10629]: warning: problem talking to service rewrite: Success

I had previously botched an upgrade by accidentally overwriting my kolab.conf using etc-update. In the /etc/kolab folder, I noticed that there were some automatically generated backup folders which had copies of kolab.conf. I used one of these and was able to do a kolabconf again. I can authenticate with my email account users. It seems to only be this part of Postfix that is having trouble.

Any help would be greatly appreciated.

Thanks,
Jason

[jayk]

Apparently there is more to my problem than I thought. I tried to login to the kolab web admin and I see:

Errors:
Could not bind to LDAP server: Invalid credentials

at the top of the screen. I'm thinking the ldap passwords in the backup kolab.conf that I restored are wrong. Is there a way to recover ldap passwords? Will I have to back up my IMAP data and then re-bootstrap my install and then restore my IMAP data?

Thanks,
Jason

[jayk]

Well, after trying many different things to get my existing server working, I ended up backing everything up, bootstrapping, and re-importing my ldap user data. I should have taken the plunge and gone this route sooner as it was about 15 minutes to fix it.

Things seem to be working fine now.

Lesson learned: "Don't upgrade kolab late at night with little sleep. Don't ever overwrite kolab.conf with etc-update."

Cheers,
Jason

[Gunnar Wrobel]

Having a good backup taht you can restore as quick as possible is probably the most important thing on a Kolab server. Usually restoring kolab.conf from a kolabconf backup should also work as long as you didn't change the settings. There is usually also a kolab.conf.old that has the original settings. In any case kolabconf is currently still rather stupid and should actually constantly create backups from the configuration files (at least if something gets changed).

Cheers,

Gunnar