openldap sasl_server_init failed
In fact this is not a question ;
This is a solution for an sutitation I met and digged into to solve for 2 days: here is error and solution details: I had 1 master; 2 slave openldap replications; 1 master and 1 slave were ok; but other slave I will call it "nodeFail". Code:
[root@nodeFail ldap]# slaptest -d 1 -v compat-openldap-2.1.30-7.4E.i386.rpm cyrus-sasl-2.1.19-5.EL4.i386.rpm cyrus-sasl-devel-2.1.19-5.EL4.i386.rpm cyrus-sasl-gssapi-2.1.19-5.EL4.i386.rpm cyrus-sasl-md5-2.1.19-5.EL4.i386.rpm cyrus-sasl-ntlm-2.1.19-5.EL4.i386.rpm cyrus-sasl-plain-2.1.19-5.EL4.i386.rpm cyrus-sasl-sql-2.1.19-5.EL4.i386.rpm nss_ldap-226-24.el4_6.i386.rpm openldap-2.2.13-7.4E.i386.rpm openldap-devel-2.2.13-7.4E.i386.rpm openldap-servers-2.2.13-7.4E.i386.rpm python-ldap-2.0.1-2.i386.rpm but one file is not owned by any of rpms; and it causes to openldap related security operations to fail in init stage of sasl. [root@nodeFail rpms]# rpm -qf /usr/lib/sasl2/slapd.conf file /usr/lib/sasl2/slapd.conf is not owned by any package so removing it will solve your problem; mv /usr/lib/sasl2/slapd.conf /usr/lib/sasl2/slapd.conf.none [root@nodeFail rpms]# slaptest config file testing succeeded I don't expect any of you to face this struggling error; And wish to find this note if you face it :) Have a nice day ; Tamer |
All times are GMT -5. The time now is 07:34 AM. |