[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: PID file /var/run/openldap/slapd.pid not readable (yet?) after start

To: Paul Pathiakis <pathiaki2@yahoo.com>, openldap-technical@openldap.org
Subject: Re: PID file /var/run/openldap/slapd.pid not readable (yet?) after start
From: Quanah Gibson-Mount <quanah@symas.com>
Date: Wed, 14 Aug 2019 11:09:17 -0700
Content-disposition: inline
In-reply-to: <261694580.5296575.1565797195646@mail.yahoo.com>
References: <261694580.5296575.1565797195646.ref@mail.yahoo.com> <261694580.5296575.1565797195646@mail.yahoo.com>

--On Wednesday, August 14, 2019 4:39 PM +0000 Paul Pathiakis<pathiaki2@yahoo.com> wrote:

I don't even know how to address that.

Sounds like it didn't actually start. Did you clean up the failed databaseafter adjusting the max size? Did you check to see what (if any) errorsslapd provided to the syslog file?

I would also note, that if you know the LDIF being imported is "good", it'smuch quicker to use slapadd -q to do an import while slapd is offline thanto use ldapadd while slapd is running.


--Quanah

--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>

References:
- PID file /var/run/openldap/slapd.pid not readable (yet?) after start
  - From: Paul Pathiakis <pathiaki2@yahoo.com>

Prev by Date: PID file /var/run/openldap/slapd.pid not readable (yet?) after start
Next by Date: Re: PID file /var/run/openldap/slapd.pid not readable (yet?) after start
Index(es):
- Chronological
- Thread