[Date Prev][Date Next]
Re: Enabling monitor backend mucks with slapcat (ITS#2343)
> Full_Name: Quanah Gibson-Mount
> Version: 2.1.14
> OS: Solaris 8
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (220.127.116.11)
> After upgrading to OpenLDAP 2.1.14 and enabling the monitor backend,
> slapcat now complains when run from the command line that the database
> doesn't support being exported. I can get around this by doing a
> slapcat -n 2. However, why does it even try to export the monitor
> backend DB if it isn't exportable?
What version did you upgrade from? I went back in source code
and I couldn't find any trace of changes that could have allowed
slapcat of monitor backend, nor enabled tools to skip it.
I understand your point, but you may well use -n 2 or move
the "database monitor" directive to the end of your slapd.conf
I added a fix that selects the first legal database and improves
database selection checks. However, I'd suggest to always specify
what database one is dumping, to avoid nasty misunderstandings.