Hello List,
i can not get the base dn into the postgres db. The phpLDAPadmin tool complains about the missing base dn. When i try to set one, the slapd segfalts.
The w32 LDAP Admin V0.9.9.2 does not complain about the base dn. When i try to add an item, the slapd allso segfalts.
Without the sql backend the LDAP where wokring fine. The slapd seems to talk to postgres just fine.
I read a hole lot of howtos. Waht i really missed was clear instructions in howto init the sql database and brand it with the base dn.
What can i do next?
Thx a lot, Axel
The LDAP host:
Linux fn 2.6.7-1-686-smp #1 SMP Wed Jul 28 13:02:18 CEST 2004 i686
ii libiodbc2 3.52.2-3 iODBC Driver Manager ii odbc-postgresq 07.03.0200-5 ODBC driver for PostgreSQL ii odbcinst1 2.2.4-11 Support library and helper
ii odbc-postgresq 07.03.0200-5 ODBC driver for PostgreSQL ii postgresql-8.1 8.1.4-6~bpo.1 object-relational SQL database ii postgresql-cli 8.1.4-6~bpo.1 front-end programs for PostgreSQL 8.1 ii postgresql-cli 59~bpo.1 manager for multiple PostgreSQL ii postgresql-com 59~bpo.1 manager for PostgreSQL database ii postgresql-doc 8.1.4-6~bpo.1 documentation for the PostgreSL da ii postgresql-ser 8.1.4-6~bpo.1 development files for PostgreSQL
ii ldap-utils 2.2.23-8 OpenLDAP utilities ii libldap-2.2-7 2.2.23-8 OpenLDAP libraries ii libldap2 2.1.30-8 OpenLDAP libraries
Down here you find:
1. slapd debug to stdout/err 2. postgres statements
######################################################################
1.
fn:/etc/ldap# slapd -d 160000 -f slapd.conf @(#) $OpenLDAP: slapd 2.2.23 (May 30 2005 08:52:42) $ @pulsar:/home/torsten/packages/openldap/openldap2.2-2.2.23/debian/build/servers/slapd slapd starting conn=0 fd=10 ACCEPT from IP=217.86.159.169:4084 (IP=0.0.0.0:389) conn=0 op=0 BIND dn="cn=admin,dc=c111,dc=org" method=128 conn=0 op=0 BIND dn="cn=admin,dc=c111,dc=org" mech=SIMPLE ssf=0 conn=0 op=0 RESULT tag=97 err=0 text= conn=0 op=1 SRCH base="dc=c111,dc=org" scope=1 deref=0 filter="(objectClass=*)" conn=0 op=1 SRCH attr=objectclass conn=0 op=1 SEARCH RESULT tag=101 err=12 nentries=0 text=control unavailable in context conn=0 op=2 SRCH base="dc=c111,dc=org" scope=1 deref=0 filter="(objectClass=*)" conn=0 op=2 SRCH attr=objectclass conn=0 op=2 SEARCH RESULT tag=101 err=0 nentries=0 text= conn=0 op=3 SRCH base="dc=c111,dc=org" scope=0 deref=0 filter="(objectClass=*)" conn=0 op=3 SEARCH RESULT tag=101 err=0 nentries=0 text= conn=0 op=4 ADD dn="ou=test,dc=c111,dc=org" Segmentation fault
##########################################################################
2.
conn = 135496696, PGAPI_Connect(DSN='ldap', UID='ldap', PWD='xxxxx') Global Options: Version='07.03.0200', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=8190 disable_optimizer=1, ksqo=1, unique_index=1, use_declarefetch=0 text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1 NAMEDATALEN=64 extra_systable_prefixes='dd_;', conn_settings='' conn_encoding='OTHER' conn=135496696, query=' ' conn=135496696, query='select version()' [ fetched 1 rows ] [ PostgreSQL version string = 'PostgreSQL 8.1.4 on i386-pc-linux-gnu, compiled by GCC cc (GCC) 3.3.5 (Debian 1:3.3.5-13)' ] [ PostgreSQL version number = '8.1' ] conn=135496696, query='set DateStyle to 'ISO'' conn=135496696, query='set geqo to 'OFF'' conn=135496696, query='set extra_float_digits to 2' conn=135496696, query='select oid from pg_type where typname='lo'' [ fetched 0 rows ] conn=135496696, query='select pg_client_encoding()' [ fetched 1 rows ] [ Client encoding = 'SQL_ASCII' (code = 0) ] conn=135496696, query='SELECT id,name,keytbl,keycol,create_proc,delete_proc,expect_return FROM ldap_oc_mappings' [ fetched 0 rows ] conn=135496696, query='ROLLBACK' conn=135496696, PGAPI_Disconnect conn = 135495944, PGAPI_Connect(DSN='ldap', UID='ldap', PWD='xxxxx') Global Options: Version='07.03.0200', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=8190 disable_optimizer=1, ksqo=1, unique_index=1, use_declarefetch=0 text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1 NAMEDATALEN=64 extra_systable_prefixes='dd_;', conn_settings='' conn_encoding='OTHER' conn=135495944, query=' ' conn=135495944, query='select version()' [ fetched 1 rows ] [ PostgreSQL version string = 'PostgreSQL 8.1.4 on i386-pc-linux-gnu, compiled by GCC cc (GCC) 3.3.5 (Debian 1:3.3.5-13)' ] [ PostgreSQL version number = '8.1' ] conn=135495944, query='set DateStyle to 'ISO'' conn=135495944, query='set geqo to 'OFF'' conn=135495944, query='set extra_float_digits to 2' conn=135495944, query='select oid from pg_type where typname='lo'' [ fetched 0 rows ] conn=135495944, query='select pg_client_encoding()' [ fetched 1 rows ] [ Client encoding = 'SQL_ASCII' (code = 0) ]
--On Wednesday, December 13, 2006 7:10 PM +0100 Axel Christiansen axel@zedx.org wrote:
Hello List, What can i do next? ii ldap-utils 2.2.23-8 OpenLDAP utilities ii libldap-2.2-7 2.2.23-8 OpenLDAP libraries ii libldap2 2.1.30-8 OpenLDAP libraries
I'd start by upgrading to a modern, supported version of OpenLDAP.
--Quanah
-- Quanah Gibson-Mount Principal Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
I'd start by upgrading to a modern, supported version of OpenLDAP.
That might not be enough, since back-sql sees little support, but it's particolarly true in this case, since back-sql was sort of heavily reworked and redesigned especially in order to make "obvious" things work (like loading from scratch) which was impossible earlier. In 2.3's source tree you'll also find some non-trivial back-sql database generation examples (for postgres, look into servers/slapd/back-sql/rdbms_depend/pgsql/). Make sure you read the back-sql related FAQ instead of Howto's: all I could find on the 'net are at least terribly outdated, if not completely wrong.
p.
Pierangelo Masarati schrieb:
I'd start by upgrading to a modern, supported version of OpenLDAP.
That might not be enough, since back-sql sees little support, but it's particolarly true in this case, since back-sql was sort of heavily reworked and redesigned especially in order to make "obvious" things work (like loading from scratch) which was impossible earlier. In 2.3's source tree you'll also find some non-trivial back-sql database generation examples (for postgres, look into servers/slapd/back-sql/rdbms_depend/pgsql/).
Yes, i was trying using the sql-create-scripts from the current versions of OpenLDAP. That was not such a good idea since they are different.
Make sure you read the back-sql related FAQ instead of Howto's: all I could find on the 'net are at least terribly outdated, if not completely wrong.
OK, i will, Axel
Quanah Gibson-Mount schrieb:
--On Wednesday, December 13, 2006 7:10 PM +0100 Axel Christiansen axel@zedx.org wrote:
Hello List, What can i do next? ii ldap-utils 2.2.23-8 OpenLDAP utilities ii libldap-2.2-7 2.2.23-8 OpenLDAP libraries ii libldap2 2.1.30-8 OpenLDAP libraries
I'd start by upgrading to a modern, supported version of OpenLDAP.
I was hoping to avoid this since it is a Debian stable Host. But i understand, will look into Debian backports or build one.
Thx, Axel
--On Thursday, December 14, 2006 6:02 PM +0100 Axel Christiansen axel@zedx.org wrote:
Quanah Gibson-Mount schrieb:
--On Wednesday, December 13, 2006 7:10 PM +0100 Axel Christiansen axel@zedx.org wrote:
Hello List, What can i do next? ii ldap-utils 2.2.23-8 OpenLDAP utilities ii libldap-2.2-7 2.2.23-8 OpenLDAP libraries ii libldap2 2.1.30-8 OpenLDAP libraries
I'd start by upgrading to a modern, supported version of OpenLDAP.
I was hoping to avoid this since it is a Debian stable Host. But i understand, will look into Debian backports or build one.
Get the 2.3.30-2 build from unstable and backport it.
--Quanah
-- Quanah Gibson-Mount Principal Software Developer ITS/Shared Application Services Stanford University GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
openldap-software@openldap.org