openldap-software October 2007

openldap-software@openldap.org

84 participants
107 discussions

slapcat error
by Laura Iacob 23 Oct '07

23 Oct '07

Hello there, I need some assistance with an error generated while trying to perform a slapcat. /usr/local/openldap/sbin/slapcat -d 1 -l /home/backup/output.ldif slapcat init: initiated tool. >>> dnNormalize: <cn=Subschema> <<< dnNormalize: <cn=subschema> Unrecognized database type (bdb) database bdb initialization failed. slapcat: bad configuration file! The database which is currently available in the path as set-up in slapd.conf was recently copied(binary copy) from another machine in order to perform some tests on it. slapd.conf has the exact configuration as on the the machine from which the database was copied.... However the openldap version seem to be different between the systems: on the test machine : openldap-2.0.27-22 on the production machine: openldap-2.0.23-4 Can the difference between the two cause the error? Thanks!

3 2

LDAP newb needs help.. (kinda long)
by Chuck 23 Oct '07

23 Oct '07

I am trying to add the following record stored in cwagon.ldif: dn: uid=cwagon,ou=People,dc=network,dc=com cn: Chuck Wagon sn: Wagon objectClass: top objectClass: person objectClass: posixAccount objectClass: shadowAccount userPassword: {crypt}6g8fRXiMEwg0Y uid: cwagon uidNumber: 500 gidNumber: 500 loginShell: /bin/bash homeDirectory: /home/cwagon shadowLastChange: 10877 shadowMin: 0 shadowMax: 999999 shadowInactive: -1 shadowWarning: 7 shadowFlag: 0 shadowExpire: -1 (This is indetical to an example on openldap.org, however the name and account have been changed to match my site) Here is a dump of my diretory thus far: # ldapsearch -x -b 'dc=network,dc=com' 'objectclass=*' # extended LDIF # # LDAPv3 # base <dc=network,dc=com> with scope subtree # filter: objectclass=* # requesting: ALL # # network.com dn: dc=network,dc=com dc: network objectClass: top objectClass: domain # Hosts, network.com dn: ou=Hosts,dc=network,dc=com ou: Hosts objectClass: top objectClass: organizationalUnit # Rpc, network.com dn: ou=Rpc,dc=network,dc=com ou: Rpc objectClass: top objectClass: organizationalUnit # Services, network.com dn: ou=Services,dc=network,dc=com ou: Services objectClass: top objectClass: organizationalUnit # netgroup.byuser, network.com dn: nisMapName=netgroup.byuser,dc=network,dc=com nisMapName: netgroup.byuser objectClass: top objectClass: nisMap # Mounts, network.com dn: ou=Mounts,dc=network,dc=com ou: Mounts objectClass: top objectClass: organizationalUnit # Networks, network.com dn: ou=Networks,dc=network,dc=com ou: Networks objectClass: top objectClass: organizationalUnit # People, network.com dn: ou=People,dc=network,dc=com ou: People objectClass: top objectClass: organizationalUnit # Group, network.com dn: ou=Group,dc=network,dc=com ou: Group objectClass: top objectClass: organizationalUnit # Netgroup, network.com dn: ou=Netgroup,dc=network,dc=com ou: Netgroup objectClass: top objectClass: organizationalUnit # Protocols, network.com dn: ou=Protocols,dc=network,dc=com ou: Protocols objectClass: top objectClass: organizationalUnit # Aliases, network.com dn: ou=Aliases,dc=network,dc=com ou: Aliases objectClass: top objectClass: organizationalUnit # netgroup.byhost, network.com dn: nisMapName=netgroup.byhost,dc=network,dc=com nisMapName: netgroup.byhost objectClass: top objectClass: nisMap # search result search: 2 result: 0 Success # numResponses: 14 # numEntries: 13 When I run this command it fails: # ldapadd -W -x -D "cn=Manager,dc=network,dc=com" -W -f cwagon.ldif Enter LDAP Password: warning: no attributes to add (entry="uid=cwagon,ou=People,dc=network,dc=com") adding new entry "uid=cwagon,ou=People,dc=network,dc=com" ldap_add: Protocol error (2) additional info: no attributes provided Here is my slapd.conf: include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/nis.schema allow bind_v2 pidfile /var/run/openldap/slapd.pid argsfile /var/run/openldap/slapd.args database bdb suffix "dc=network,dc=com" rootdn "cn=Manager,dc=network,dc=com" rootpw secret rootpw {SHA}W6ph5Mm5Pz8GgiULbPgzG37mj9g= directory /var/lib/ldap index objectClass eq,pres index ou,cn,mail,surname,givenname eq,pres,sub index uidNumber,gidNumber,loginShell eq,pres index uid,memberUid eq,pres,sub index nisMapName,nisMapEntry eq,pres,sub Anyone have any ideas what I'm doing wrong? I've followed the docs on openldap.org and I'm trying to insert a record identical in format to the one listed in the docs. (only the text strings have been changed) Thanks /CC

3 3

How to set default password encryption?
by Matthias Bourillon 23 Oct '07

23 Oct '07

I could read that default password encryption could be set in OpenLDAP so that LDAP can deal with it even if the password is given in clear text. Where can this be set up?

3 2

codding the controlValue in an LDIF control field
by Antonio Alonso 22 Oct '07

22 Oct '07

Hi ! I have a doubt trying to code an "assertion control" (according to RFC 4528) in the "control" field of an LDIF file. The assertion to code is a simple "equalityMatch" filter (i.e. "attribute type = attribute value"). This is the LDIF file I was preparing (to pass to an "ldapmodify" command) # LDIF file START (it contains all the updates for a single/atomic LDAPModify op.): dn: <entry dn to update> control: 1.3.6.1.1.12 true :<controlValue> changetype: modify ... How do I code the "controlValue" (i.e. the equalityMatch filter describing the required assertion) in the LDIF file? I thought it was the BER encoding, but after reading the formal syntax definition for the control field in RFC 2849 (LDIF spec) it is not clear to me ... Thanks in advance BR / Antonio > Antonio Alonso Alarcón CUDB System Engineer > Ericsson España, S.A. Phone: +34 91339 3085 Via de los Poblados 13 Mobile: +34 609640579 (66215) 28033 Madrid, Spain Fax: +34 91339 1636 E-mail: Antonio.Alonso(a)ericsson.com

1 0

RE: Openldap upgrade/migration
by Ravi Rajasekharuni 22 Oct '07

22 Oct '07

Thanks Quanah for a quick reply. The old LINUX 6.2 server running openldap 1.2 is not operational, but all the old files (/etc/openldap, /usr/share/openldap (database) are available on a new LINUX server running Red hat Enterprise Linux 4. How can I export openldap data from old files sitting on this new Linux server.? I believe the slapcat command is only recognizes openldap 2.x databases. Is there any other way of exporting data from old openldap 1.2 version data files using a latest version of openldap tools. Please advice. Regards, -Ravi ________________________________ Ravi Rajasekharuni - Web and Data Admin Unit 2, 12 Mars Road, Lane Cove, NSW 2066 Tel: +61 2 8987 5727 Fax: +61 2 8987 5720 Web: www.au.issworld.com -----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] Sent: Tuesday, 23 October 2007 12:32 AM To: Ravi Rajasekharuni; openldap-software(a)openldap.org Subject: Re: Openldap upgrade/migration --On Monday, October 22, 2007 8:33 AM +1000 Ravi Rajasekharuni <ravi.rajasekharuni(a)au.issworld.com> wrote: > Please respond. The method for moving from one version of OpenLDAP to another (and this is pretty consistent with all directory servers) is to use LDIF. In openldap, you'd generate the LDIF file for export from your old server using the slapcat command. Since you no longer have a running server, I'm not quite sure how you expect to proceed on any of this. I wish you luck. --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

3 2

RE: Openldap upgrade/migration
by Ravi Rajasekharuni 22 Oct '07

22 Oct '07

Thanks Quanah. I am thinking of installing RED HAT LINUX 7.3 on another computer and install openldap 1.2.13. If I have the above environment, can I copy /etc/openldap and /usr/share/openldap date to this PC and export the database. I can not go back to RH LINUX 6.2 as it can not be installed on any PC hardware lower than Pentium 4. I don't have Pentium 2 or Pentium 3 PCs. I believe RH LINUX versions 7.0 and above can be installed on Pentium 4 PC. Assuming above env is right, after exporting data to LDIF format, how can import LDIF to new version of Openldap (2.2 version) running on Red Hat Enterprise Linux 4. Regards, Ravi ________________________________ Ravi Rajasekharuni - Web and Data Admin Unit 2, 12 Mars Road, Lane Cove, NSW 2066 Tel: +61 2 8987 5727 Fax: +61 2 8987 5720 Web: www.au.issworld.com -----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] Sent: Tuesday, 23 October 2007 2:45 PM To: Ravi Rajasekharuni; openldap-software(a)openldap.org Subject: RE: Openldap upgrade/migration --On Tuesday, October 23, 2007 2:06 PM +1000 Ravi Rajasekharuni <ravi.rajasekharuni(a)au.issworld.com> wrote: > > Thanks Quanah for a quick reply. > > The old LINUX 6.2 server running openldap 1.2 is not operational, but > all the old files (/etc/openldap, /usr/share/openldap (database) are > available on a new LINUX server running Red hat Enterprise Linux 4. How > can I export openldap data from old files sitting on this new Linux > server.? I believe the slapcat command is only recognizes openldap 2.x > databases. > > Is there any other way of exporting data from old openldap 1.2 version > data files using a latest version of openldap tools. Nope. You need to have 1.2 running to export it with the 1.2 tools. At least, that's my assumption, having never seen 1.2 running. :P --Quanah -- Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration

2 1

RE: slapcat error
by Srilakshmanan, Kumuthiny 22 Oct '07

22 Oct '07

Try this /usr/local/openldap/sbin/slapcat -f slapd.conf -l /home/backup/output.ldif -----Original Message----- From: openldap-software-bounces+kumuthiny.srilakshmanan=auspost.com.au(a)OpenLDAP.or g [mailto:openldap-software-bounces+kumuthiny.srilakshmanan=auspost.com.au@Ope nLDAP.org] On Behalf Of Laura Iacob Sent: Tuesday, 23 October 2007 12:34 AM To: openldap-software(a)openldap.org Subject: slapcat error Hello there, I need some assistance with an error generated while trying to perform a slapcat. /usr/local/openldap/sbin/slapcat -d 1 -l /home/backup/output.ldif slapcat init: initiated tool. >>> dnNormalize: <cn=Subschema> <<< dnNormalize: <cn=subschema> Unrecognized database type (bdb) database bdb initialization failed. slapcat: bad configuration file! The database which is currently available in the path as set-up in slapd.conf was recently copied(binary copy) from another machine in order to perform some tests on it. slapd.conf has the exact configuration as on the the machine from which the database was copied.... However the openldap version seem to be different between the systems: on the test machine : openldap-2.0.27-22 on the production machine: openldap-2.0.23-4 Can the difference between the two cause the error? Thanks! Australia Post is committed to providing our customers with excellent service. If we can assist you in any way please telephone 13 13 18 or visit our website. The information contained in this e-mail communication may be proprietary, confidential or legally professionally privileged. It is intended exclusively for the individual or entity to which it is addressed. You should only read, disclose, re-transmit, copy, distribute, act in reliance on or commercialise the information if you are authorised to do so. Australia Post does not represent, warrant or guarantee the integrity of this e-mail communication has been maintained nor that the communication is free of errors, virus or interference. If you are not the addressee or intended recipient please notify us by replying direct to the sender and then destroy any electronic or paper copy of this message. Any views expressed in this e-mail communication are taken to be those of the individual sender, except where the sender specifically attributes those views to Australia Post and is authorised to do so.

2 1

Re: SyncREPL generates high traffic to calculate delta
by Bruno Lezoray EMSM 22 Oct '07

22 Oct '07

Bruno Lezoray EMSM wrote: > Hi all, > > I have the following configuration, in OpenLDAP 2.3.32 (i know i have to > upgrade to 2.3.38): > Master -> Pivot -> Slave on 3 different servers. SyncRepl replicates in > RefreshOnly mode, a sub-tree. > > When i dump the TLS traffic during a replication of a add or delete > operation, i have around 6000 TCP packets between Master and Pivot, and > only 40 packets between Pivot and Slave. My replicated sub-tree contains 5500 > entries. So, i concluded that Pivot SyncRepl ask the entire sub-tree. > Is it a known problem ? Does it come from the configuration ? > > About this trouble, do you have a idea ? Rgds, Bruno.

2 1

loglevel question
by Piotr Wadas 22 Oct '07

22 Oct '07

Hello, Can I set "loglevel" option only for particular database, or all databases of particular backend (any slapd version) ? man slapd-<backend> does not mention about it, and the loglevel option is marked global in slapd manpage, however "GLOBAL CONFIGURATION OPTIONS Options described in this section apply to all backends, unless specifically overridden in a backend definition." Regards, Piotr

4 4

Openldap upgrade/migration
by Ravi Rajasekharuni 22 Oct '07

22 Oct '07

Hi, We have openldap 1.2.x on Redhat Linux 6.2 and due to hardware upgrade we need to migrate to Redhat Linux Enterprise 4. How can I run Openldap 1.2.x on REDHAT LINUX Enterprise 4. Alternatviley how can I migrate from 1.2.x to 2.x ? We don't have the old server running Redhat Linux 6.2/Openldap 1.2 any more and all data from openldap 1.2 version is on a tape.How can I restore this tape and mak eit work on a new hardware running higher version of linux. Please respond. Thanks. -Ravi

2 1

← Newer
1
2
3
4
5
6
7
8
...
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-software October 2007