Can someone tell me whats wrong here.. I had a working ldap/samba server and after I restarted the machine due to a power outage the slapd service wont start back up.
Here are what the logs show when I try to bring slapd back online: Apr 8 14:06:23 mdc slapd[12286]: @(#) $OpenLDAP: slapd 2.3.43 (Apr 8 2010 13:58:40) $ Apr 8 14:06:23 mdc root@mdc: /var/tmp/portage/net-nds/openldap-2.3.43/work/openldap-2.3.43/servers/slapd Apr 8 14:06:23 mdc slapd[12286]: nss_ldap: failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server Apr 8 14:06:23 mdc slapd: Last message 'nss_ldap: failed to ' repeated 1 times, supressed by syslog-ng on mdc.mydomain.org Apr 8 14:06:23 mdc slapd[12286]: nss_ldap: reconnecting to LDAP server... Apr 8 14:06:23 mdc slapd[12286]: nss_ldap: failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server Apr 8 14:06:23 mdc slapd[12286]: nss_ldap: reconnecting to LDAP server (sleeping 1 seconds)... Apr 8 14:06:24 mdc slapd[12286]: nss_ldap: failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server Apr 8 14:06:24 mdc slapd[12286]: nss_ldap: could not search LDAP server - Server is unavailable Apr 8 14:06:24 mdc slapd[12286]: nss_ldap: failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server Apr 8 14:06:24 mdc slapd: Last message 'nss_ldap: failed to ' repeated 1 times, supressed by syslog-ng on mdc.mydomain.org Apr 8 14:06:24 mdc slapd[12286]: nss_ldap: reconnecting to LDAP server... Apr 8 14:06:24 mdc slapd[12286]: nss_ldap: failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server Apr 8 14:06:24 mdc slapd[12286]: nss_ldap: reconnecting to LDAP server (sleeping 1 seconds)... Apr 8 14:06:25 mdc slapd[12286]: nss_ldap: failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server Apr 8 14:06:25 mdc slapd[12286]: nss_ldap: could not search LDAP server - Server is unavailable Apr 8 14:06:25 mdc slapd[12287]: bdb(dc=mydomain,dc=org): unable to allocate memory for mutex; resize mutex region Apr 8 14:06:25 mdc slapd[12287]: hdb_db_open: Database cannot be opened, err 12. Restore from backup! Apr 8 14:06:25 mdc slapd[12287]: bdb(dc=mydomain,dc=org): DB_ENV->lock_id_free interface requires an environment configured for the locking subsystem Apr 8 14:06:25 mdc slapd[12287]: bdb(dc=mydomain,dc=org): txn_checkpoint interface requires an environment configured for the transaction subsystem Apr 8 14:06:25 mdc slapd[12287]: bdb_db_close: txn_checkpoint failed: Invalid argument (22) Apr 8 14:06:25 mdc slapd[12287]: backend_startup_one: bi_db_open failed! (12) Apr 8 14:06:25 mdc slapd[12287]: bdb_db_close: alock_close failed Apr 8 14:06:25 mdc slapd[12287]: slapd stopped. Apr 8 14:06:25 mdc slapd[12287]: connections_destroy: nothing to destroy.
Thanks ~ Nick
--On Thursday, April 08, 2010 2:14 PM -0700 Nick Pappin npappin@latahfcu.org wrote:
Can someone tell me whats wrong here.. I had a working ldap/samba server and after I restarted the machine due to a power outage the slapd service wont start back up.
Here are what the logs show when I try to bring slapd back online: Apr 8 14:06:23 mdc slapd[12286]: @(#) $OpenLDAP: slapd 2.3.43 (Apr 8 2010 13:58:40) $ Apr 8 14:06:23 mdc root@mdc: /var/tmp/portage/net-nds/openldap-2.3.43/work/openldap-2.3.43/servers/sla
Run the correct db_recover (the one for the version of BDB openldap is linked against) inside your database directory, remove the alock file there, and then start it.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
On Thursday, 8 April 2010 22:14:57 Nick Pappin wrote:
Can someone tell me whats wrong here.. I had a working ldap/samba server and after I restarted the machine due to a power outage the slapd service wont start back up.
Here are what the logs show when I try to bring slapd back online: Apr 8 14:06:23 mdc slapd[12286]: @(#) $OpenLDAP: slapd 2.3.43 (Apr 8 2010 13:58:40) $ Apr 8 14:06:23 mdc root@mdc: /var/tmp/portage/net-nds/openldap-2.3.43/work/openldap-2.3.43/servers/slapd
Apr 8 14:06:25 mdc slapd[12287]: bdb(dc=mydomain,dc=org): unable to allocate memory for mutex; resize mutex region Apr 8 14:06:25 mdc slapd[12287]: hdb_db_open: Database cannot be opened, err 12. Restore from backup! Apr 8 14:06:25 mdc slapd[12287]: bdb(dc=mydomain,dc=org): DB_ENV->lock_id_free interface requires an environment configured for the locking subsystem Apr 8 14:06:25 mdc slapd[12287]: bdb(dc=mydomain,dc=org): txn_checkpoint interface requires an environment configured for the transaction subsystem Apr 8 14:06:25 mdc slapd[12287]: bdb_db_close: txn_checkpoint failed: Invalid argument (22) Apr 8 14:06:25 mdc slapd[12287]: backend_startup_one: bi_db_open failed! (12) Apr 8 14:06:25 mdc slapd[12287]: bdb_db_close: alock_close failed Apr 8 14:06:25 mdc slapd[12287]: slapd stopped. Apr 8 14:06:25 mdc slapd[12287]: connections_destroy: nothing to destroy.
Are you sure the database directory (and all of its contents) for dc=mydomain,dc=org is writable by the user slapd runs as? Looks like it isn't ...
Regards, Buchan
--On Friday, April 09, 2010 12:42 PM +0100 Buchan Milne bgmilne@staff.telkomsa.net wrote:
Are you sure the database directory (and all of its contents) for dc=mydomain,dc=org is writable by the user slapd runs as? Looks like it isn't ...
I've seen this numerous times with OpenLDAP 2.3.x and a hard failure. It usually indicates the alock file is in a corrupted state, preventing recovery and startup. Which is why I suggested what I did.
There's been several fixes to alock in 2.4, and I haven't seen this issue there so far.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
openldap-technical@openldap.org