On Thursday 22 December 2005 05:52, Robert Fitzpatrick wrote: > I have been implementing saslauthd to use ldap for cyrus, postfix, etc. > All working well with no problems for a couple of days now. After an > unrelated reboot, slapd process starts, but the pid file never gets > written and the slapd process takes over 90 percent of CPU until I have > to kill -9 the process. I cannot find anything in the debug.log or > messages that were not already showing up prior to the reboot except for > the nsswitch.conf error I now see: > > Dec 21 22:39:56 esmtp slapd[3510]: bdb_db_init: Initializing BDB database > Dec 21 22:43:15 esmtp slapd[3745]: @(#) $OpenLDAP: slapd 2.2.29 (Dec 12 > 2005 23:40:46) $ > root@esmtp.webtent.net:/usr/ports/net/openldap22-sasl-server/work/openldap- >2.2.29/servers/slapd Dec 21 22:43:15 esmtp slapd[3745]: > NSSWITCH(nss_method_lookup): files, passwd_compat, endpwent, not found > Dec 21 22:43:15 esmtp slapd[3745]: NSSWITCH(nss_method_lookup): files, > group_compat, setgrent, not found > Dec 21 22:43:15 esmtp slapd[3745]: NSSWITCH(nss_method_lookup): files, > group_compat, endgrent, not found > Dec 21 22:43:15 esmtp slapd[3745]: NSSWITCH(nss_method_lookup): files, > group_compat, endgrent, not found > Dec 21 22:43:15 esmtp slapd[3745]: _sasl_plugin_load failed on > sasl_auxprop_plug_init for plugin: ldapdb > Dec 21 22:43:15 esmtp slapd[3745]: bdb_db_init: Initializing BDB database > > That's it, can't find any other message related to slapd not > starting....anyone know what might have gone wrong? Yep, 2.2.x doesn't do automatic recovery on start, you should ensure that database recovery (ie dbrecover -h /path/to/data) is run any time that unclean shutdown is likely/possible (ie in the start() section of the init script or similar). Regards, Buchan -- Buchan Milne ISP Systems Specialist B.Eng,RHCE(803004789010797),LPIC-2(LPI000074592)
Attachment:
pgpaz2O2airza.pgp
Description: PGP signature