Date: Sun, 28 Apr 2013 18:30:22 +0100 From: Chris Rees <crees@FreeBSD.org> To: FreeBSD Mailing List <freebsd-ports@freebsd.org>, Xin LI <d@delphij.net> Subject: Re: openldap-2.4.35: "failed to start slapd" Message-ID: <CADLo8382V97nGiTq4wMa_R_EXcjKpdGEZv3dEkBgrUeUwJ5yDA@mail.gmail.com> In-Reply-To: <20130428131704.1eb14721@scorpio> References: <20130428070851.60d08788@scorpio> <CADLo839jkJOAh4nNPvn8_2VMLEuaf8%2BoKW2ibnPtM9rmqU7ghw@mail.gmail.com> <20130428131704.1eb14721@scorpio>
next in thread | previous in thread | raw e-mail | index | archive | help
On 28 April 2013 18:17, Jerry <jerry@seibercom.net> wrote: > On Sun, 28 Apr 2013 16:48:33 +0100 > Chris Rees articulated: > >> Have you tried getting the older version and installing that? >> >> Ports-mgmt/portdowngrade will help you do that. >> >> Not a proper solution, but it'll get it working again if you're >> desperate. > > Actually, the database "log" got corrupted. Even the "db-recover" would > not correct it. Luckily, I had a semi-recent backup of the directory. I > had to run "/usr/local/libexec/slapd" via "GDB" to find out what the > problem was. I have no idea what caused the corruption though. The only > thing that comes to mind is that I DID NOT shut down openldap prior to > updating it. That never caused a problem before though. I'm really glad you had backups. I'd be surprised if the in-place upgrade broke things, but it might cause a problem. I've never had an issue with any daemons like that. Xin Li, do you know if corruption due to this is possible? Would a @stopdaemon line be appropriate here? Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo8382V97nGiTq4wMa_R_EXcjKpdGEZv3dEkBgrUeUwJ5yDA>