Full_Name: Benjamin Behringer Version: 2.4.35 OS: Ubuntu 12.04 64bit URL: Submission from: (NULL) (2001:7c0:409:8eaa:cb:7a6a:91f0:f867) Hi, I'm using OpenLDAP and back-sql to make the information, stored in a MySQL Database, available over LDAP (for Authentication purposes). Unfortunately, when I insert or update an entry in the Database, the DIT is not updated. In contrast, a delete on the ldap_entries table will cause slapd to reflect the DB change in the DIT. The issue only occurs, when the DIT has already been loaded, and the subtree you will make the change to has already been read at least once. If you restart slapd, the changes are reflected. Software Versions: Distribution: Ubuntu 12.04 64bit MySQL: 5.5.31-0ubuntu0.12.04.1 OpenLDAP: 2.4.35 libmyodbc: 5.2.4 unixodbc: 2.3.0-2ubuntu1 Here are a sample configuration file: http://pastebin.de/34104 odbc config files: http://pastebin.de/34103 sample db script: http://pastebin.de/34101 and insert script: http://pastebin.de/34102 Is there a patch, workaround, anything? Regards
On 04/29/2013 02:33 PM, mail@benjamin-behringer.de wrote: > Full_Name: Benjamin Behringer > Version: 2.4.35 > OS: Ubuntu 12.04 64bit > URL: > Submission from: (NULL) (2001:7c0:409:8eaa:cb:7a6a:91f0:f867) > > > Hi, > > I'm using OpenLDAP and back-sql to make the information, stored in a MySQL > Database, available over LDAP (for Authentication purposes). Unfortunately, when > I insert or update an entry in the Database, the DIT is not updated. In > contrast, a delete on the ldap_entries table will cause slapd to reflect the DB > change in the DIT. The issue only occurs, when the DIT has already been loaded, > and the subtree you will make the change to has already been read at least once. > If you restart slapd, the changes are reflected. > > Software Versions: > > Distribution: Ubuntu 12.04 64bit > MySQL: 5.5.31-0ubuntu0.12.04.1 > OpenLDAP: 2.4.35 > libmyodbc: 5.2.4 > unixodbc: 2.3.0-2ubuntu1 > > Here are > > a sample configuration file: > http://pastebin.de/34104 > > odbc config files: > http://pastebin.de/34103 > > sample db script: > http://pastebin.de/34101 > > and insert script: > http://pastebin.de/34102 > > Is there a patch, workaround, anything? There is no caching of the contents of ldap_entries in back-sql; maybe some caching at the odbc level? p. -- Pierangelo Masarati Associate Professor Dipartimento di Scienze e Tecnologie Aerospaziali Politecnico di Milano
someone needs to confirm this is not a bug in back-sql but an issue with odbc
changed notes moved from Incoming to Software Bugs
patches welcome