Howard Chu <hyc(a)symas.com> writes:
> dieter(a)dkluenter.de wrote:
>> Full_Name: Dieter Kluenter
>> Version: HEAD
>> OS: Linux x86_64
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (84.142.215.25)
>>
>>
>> Hi,
>> test036 fails constantly with following error:
>> ...
>> Using ldapsearch to retrieve all the entries...
>> Filtering ldapsearch results...
>> Filtering original ldif used to create database...
>> Comparing filter output...
>> comparison failed - slapd-meta search/modification didn't succeed
>
> If your HEAD snapshot is before this commit, then it's a known issue
> and this ITS will be closed.
>
> http://www.openldap.org/lists/openldap-commit/200807/msg00174.html
No, it is a cvs update from last night.
-Dieter
--
Dieter Klünter | Systemberatung
http://www.dkluenter.de
GPG Key ID:8EF7B6C6
dieter(a)dkluenter.de wrote:
> Full_Name: Dieter Kluenter
> Version: HEAD
> OS: Linux x86_64
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (84.142.215.25)
>
>
> Hi,
> test036 fails constantly with following error:
> ...
> Using ldapsearch to retrieve all the entries...
> Filtering ldapsearch results...
> Filtering original ldif used to create database...
> Comparing filter output...
> comparison failed - slapd-meta search/modification didn't succeed
If your HEAD snapshot is before this commit, then it's a known issue and this
ITS will be closed.
http://www.openldap.org/lists/openldap-commit/200807/msg00174.html
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
quanah(a)zimbra.com wrote:
> --On Thursday, July 17, 2008 6:19 AM +0000 marco.walther(a)sun.com wrote:
>
>> Full_Name: Marco Walther
>> Version: 2.4.11
>> OS: SunOS 5.11 snv_70b sun4v sparc SUNW,SPARC
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (192.18.43.225)
>
> No openldap release supports BDB 4.7 yet. There is already a bug filed on
> this issue, and it will be addressed in an upcoming release.
#5530. This ITS will be closed as a dup of #5530.
Hacking the BDB source to expose the private field certainly works for now,
but we'll be looking at a hands-off fix later.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
--On Thursday, July 17, 2008 6:19 AM +0000 marco.walther(a)sun.com wrote:
> Full_Name: Marco Walther
> Version: 2.4.11
> OS: SunOS 5.11 snv_70b sun4v sparc SUNW,SPARC
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (192.18.43.225)
No openldap release supports BDB 4.7 yet. There is already a bug filed on
this issue, and it will be addressed in an upcoming release.
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra :: the leader in open source messaging and collaboration
Full_Name: Marco Walther
Version: 2.4.11
OS: SunOS 5.11 snv_70b sun4v sparc SUNW,SPARC
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (192.18.43.225)
The problem is in servers/slapd/back-bdb/cache.c and
servers/slapd/back-bdb/init.c
The db-4.7.?? moved the lk_handle from the public DB_ENV to a private ENV
structure. So it's officially not accessible any more.
I'll include a little diff to show the problem. But I don't think my `quick
compile' fix is completely correct.
I'm more interested in the client libraries than the servers right now.
--- init.c.orig Wed Jul 16 22:56:00 2008
+++ init.c Wed Jul 16 23:01:26 2008
@@ -503,9 +503,15 @@
}
if ( !quick ) {
-#if DB_VERSION_FULL >= 0x04060012
+#if DB_VERSION_FULL >= 0x04070025
+ # XXX mw79288 real hack!!
+ #include "/export/home/marcow/src/db-4.7.25/build_unix/db_int.h"
u_int32_t lid;
XLOCK_ID(bdb->bi_dbenv, &lid);
+ __lock_getlocker(bdb->bi_dbenv->env->lk_handle, lid, 0,
&bdb->bi_cache.c_locker);
+#elsif DB_VERSION_FULL >= 0x04060012
+ u_int32_t lid;
+ XLOCK_ID(bdb->bi_dbenv, &lid);
__lock_getlocker(bdb->bi_dbenv->lk_handle, lid, 0,
&bdb->bi_cache.c_locker);
#else
XLOCK_ID(bdb->bi_dbenv, &bdb->bi_cache.c_locker);
Full_Name: Paul B. Henson
Version: 2.3.40
OS: Gentoo
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (134.71.248.24)
I would like to request some configuration mechanism that would allow slapd to
be configured with different LDAP settings. This could be a commandline option,
or an extension to the configuration file. My particular situation is that I
need to have a different setting for derefAliases for slapd (in order for
syncrepl to work) vs the automounter (which needs to dereference aliases to
integrate into my directory configuration).
Full_Name: Paul B. Henson
Version: 2.3.40
OS: Gentoo
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (134.71.248.24)
I recently installed some updates and configuration changes on one of my
LDAP slaves. Replication broke mysteriously after that. The only thing logged
was "slapd[30723]: do_syncrepl: rid 001 retrying (9 retries left)"
I finally figured out that the search was failing with a protocol error because
derefAliases was set to always, a setting I had just added. It would be useful
if replication failure provided better error messages, something in the logs
indicating that a protocol error had occurred because of an invalid
dereferencing setting would have saved me a lot of time.
In addition, if it is a protocol error to dereference aliases in the context of
syncrepl, shouldn't the server just ignore that global configuration setting and
just do the right thing?
Full_Name: Miguel Jinez
Version: 2.4.10
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (209.13.96.237)
I am running openLdap 2.4.10
I have configurated 2 n-way multimaster(A-B) servers, it works fine when two
masters are up.
I have a problem in the next situation:
1)-Everything ok
2)-One master(A) dies (is not working).
3)-Adds, updates and DELETES are performed meanwhile in master(B).
4)-Master(B) dies too and master(A) has not been restarted.
5)-Restart master(B)
6)-Restart master(A)
7)-Checking DIT in master(B) = ok
8)-Checking DIT in master(A) adds=ok
9)-Checking DIT in master(A) updates=ok
10)-Checking DIT in master(A) DELETES= Entries are not deleted at
synchronization time.
Why adds and updates are performed and deletes no?
Maybe the reqMod is not loaded in deletes?
Thanks fro your atention
Migue