--On Tuesday, September 28, 2010 1:21 PM -0500 "Walton, Bryan K"
<bryan-wal...@uiowa.edu> wrote:
On Tue, 2010-09-28 at 09:42 -0700, Quanah Gibson-Mount wrote:
The last thing I can think of, just to verify the database didn't get
into an odd place, would be to reload the master. I'd spot check the
LDIF file to make sure it looked fine.
Thanks. That didn't seem to make any difference. LDIF file seems
perfectly correct. I dumped both directories (master and slave), and
LDIFs were identical. Yet, slapcat errors on the master and not the
slave. Anyway, I repopulated the directory and still get the error.
BTW, there is one other difference between the two servers, the master
is 64-bit, while the slave is 32-bit.
The other thing I find odd is that the error only occurs when slapd is
running. If there was really a problem, wouldn't the error also occur
when doing a slapcat while slapd is stopped?
Yeah, I really have no idea why you are seeing this. I would note that a
32-bit binary would not work well with a 64-bit built database (or vice
versa), but I assume both slapd and slapcat in your case are 64-bit.
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra :: the leader in open source messaging and collaboration
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
