[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: Invalid credentials
- To: "'Ryan Tandy'" <ryan@nardis.ca>
- Subject: RE: Invalid credentials
- From: "Dave Beach" <drbeach4@gmail.com>
- Date: Sun, 21 Feb 2016 13:16:37 -0500
- Cc: openldap-technical@openldap.org
- Content-language: en-ca
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=fv+ZPs58QnafCj2XP1M4pXx0LILFXLzad3b9fr0cQi8=; b=g0k0V5ag29Y2WSur6ztxw+w8edK9Sfy9Z/gPzufqkvhGp52FFB+K+U/UXdC/6F+1kZ Czm1+Cb28POgLgd27TGb4CXOLfaFhzdhOJakh4DsMK/M65YrmGTA3dFJVLWaBgp0I1jx vMpa4Qm7Pq86idD9tOs/ajOvRjDKnwxGbkODSLbicEMwB0yfP/85omTJ3nwO/7pQ0z4t M0/DuAB+n1oX9ZCRNb3ba+zAlN6udyPS8MqdEKOVX8+gySgvgp46ypFHgcHCmbJnbM6f 2zZEmDkdZ8Iv1XsWbg0jQtcHnwUOIB4oa1jvIy+C+JqxvwRLKlJB3nD2aKDF92hyXL5e TVdA==
- In-reply-to: <20160221174753.GA632@kiwi>
- References: <001201d16b94$285e5e20$791b1a60$@gmail.com> <DA06CE5AA35A4905CC681854@192.168.1.9> <003e01d16c06$776a8c10$663fa430$@gmail.com> <CACsf_wx3Xd50ALD2q5+aJrMSZsAVf-S8C6cG4ne5uFLXtJj_kQ@mail.gmail.com> <004801d16cb9$35b79bb0$a126d310$@gmail.com> <20160221174753.GA632@kiwi>
- Thread-index: AQGQGsr6H8Dlu7b2wMcbGBUYLhZ9lwJHQVrRAnziEBsBKNYWEAFvaOuYAnZUa1+fatrKQA==
> The default pidfile location is /var/run/slapd/slapd.pid, and the init
script does "mkdir $(dirname $pidfile)" during startup.
There is no /var/run/slapd...
> However, your pidfile is set to /var/run/slapd.pid, so probably nothing is
creating /var/run/slapd.
Aha.
> A workaround to get you going would be to change your pidfile setting to
/var/run/slapd/slapd.pid.
Done.
> To restore sanity, you may want to
> chown -R openldap:openldap /var/lib/ldap /etc/ldap/slapd.conf
Done.
> (and /etc/ldap/slapd.d, if it exists)
It does not (I've renamed it for the moment as a means of forcing the init
script to use slapd.conf, as it won't if /etc/ldap/slapd.d exists)
Ok. A quick test to see if that solves some of the problem.
Good news, slapd is now starting properly without manual intervention, and
var/run/slapd/slapd.pid exists. Much rejoicing throughout the kingdom.
>> database bdb
> And time to upgrade to MDB backend as well, but obviously with lower
priority, after the current fire has been put out. :)
Perhaps - I kept bdb because I'm working with older bdb databases; at some
point I'll have to figure out how to convert.
> I have no evidence that indexing is your problem, but in an odd situation
like yours, I might re-index just to rule that out:
> sudo -u openldap slapindex -f /etc/ldap/slapd.conf -q
Hmm. The result of which is:
56c9ff8f bdb_db_open: database "dc=drbhome,dc=ca": database already in use.
56c9ff8f backend_startup_one (type=bdb, suffix="dc=drbhome,dc=ca"):
bi_db_open failed! (-1)
slap_startup failed