LDIF?

: adding new entry "ou=RavenApps,dc=my-domain,dc=com" ldap_add: Invalid syntax (21)     additional info: objectclass: value #1 invalid per syntax I have an LDIF file called "users-example.ldif" with the contents:dn: ou=RavenApps,dc=my-domain,dc=com objectclass: dcObject objectClass

ldif-diff / ldif->ldap sync utilities

[There doesn't seem to be an active general LDAP list anymore, so I hope it's OK to post here instead.] I need an ldif-diff utility (take two LDIF dumps and produce an .LDIF to change one to the other) and maybe an LDIF->LDAP sync program like this: - Give me some control of the o

Re: LDIF?

--On Tuesday, February 23, 2016 10:39 PM + Mary Kao wrote: objectClass: organizationUnit As the error clearly states, the above is not a valid objectClass. Perhaps you mean organizationalUnit? --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. Z

Re: LDIF?

full debugging would reveal more specifics about what's going wrong. By eye, I'd guess the 'search results' entries are what's tripping that. If this LDIF file was generated via 'ldapsearch', you might want to make sure to use '-LLL' flags; read the man

Re: LDIF?

--On Wednesday, February 24, 2016 12:50 AM +0100 Emmanuel Lécharny wrote: No to mention there is a missing dc Attribute in the entry. Good point. It's unlikely the author meant to combine the two objectClasses. --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc.

Re: LDIF?

Thank you all.  It was the two issues mentioned here e.g. typo of organizationUnit and missing dc. On Tuesday, February 23, 2016 7:49 PM, Quanah Gibson-Mount wrote: --On Wednesday, February 24, 2016 12:50 AM +0100 Emmanuel Lécharny wrote: >> > No to mention there is a missing dc A

slapcat ldif backup

rectory (2). Restore from backup! 5471c421 backend_startup_one (type=mdb, suffix="dc=seibercom,dc=net"): bi_db_open failed! (2) slap_startup failed LDIF Backup Failed Exit Code: 0 I ran the slapcat command under "truss" and this is the output: mmap(0x0,32768,PROT_READ|PROT_WRI

Default LDIF Configuration

When running slapd with -f etc/openldap/slapd.ldif, I receive the following line 5: unknown directive outside backend info and database definitions. By default slapd is using the .conf file instead, which works fine. This is the default ldif file, and line 5 seems to be the same as line 2

LDIF and cn=config

Hello, I'm trying to figure out what's happening with my LDAP. I insert an LDIF modifying a schema in cn=schema,cn=config, OpenLDAP gives me an error "No such object", but it still does the modification. How can I do to avoid having this error while the modification is w

Re: slapcat ldif backup

h file or directory (2). Restore from backup! 5471c421 backend_startup_one (type=mdb, suffix="dc=seibercom,dc=net"): bi_db_open failed! (2) slap_startup failed LDIF Backup Failed Exit Code: 0 I ran the slapcat command under "truss" and this is the output: stat("

Re: Default LDIF Configuration

Trent Dierking wrote: > When running slapd with -f etc/openldap/slapd.ldif, I receive the following See slapd(8) for the differences of command-line options -f and -F. Ciao, Michael. smime.p7s Description: S/MIME Cryptographic Signature

Convert *.schema to *.ldif

I don't see any description in the admin guide about how to convert a *.schema file into a *.ldif file. Google tells me that most people are using slaptest with the -F and -f parameters with a specially crafted slapd.conf file. As the person who is responsible for a *.schema file and dev

Openldap configuration import LDIF

hi, i have install OpenLdap in a UbuntuServer, in virtual with VirtualBox. Now i want to import in Eclipse via Ldap Browser one file LDIF. I have a FQDN like this, ldap.***.***.com, and i add this in /etc/hosts this FQDN with a ip address 192.168.1.156, the ip is my Server. Now the problem

Encoded entries on LDIF file

Hello all, I'm trying to import an LDIF file where some users have values that appear to be encoded on the file. The values have two : (i.e. ::) and appear like this: # entry-id: 36545 dn: uid=someuser,ou=funcionarios,ou=pessoal,o=xxx,c=xxx l:: UkYgLSAyqiBFc3RhbmNpYQ== This isn't

Error 53 applying syncrepl LDIF

Hello all, In a syncrepl setup, I understand that the syncrepl specification is defined on the consumer server. I understand this to mean that I should apply my LDIF (that adds the olcSyncrepl attribute to my config and hdb backends) on the consumer server. However, ldapadd was only successful in

about LDIF operation by API

It seems nothing is provided for operating LDIF. How to implement ldif export and import with C/C++ in OpenLDAP. gtalk:freeespe...@gmail.com

Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX

Hello, OpenLDAP version: 2.3.43-12 (CentOS 5.5), 64-bit. In order to enable ppolicy overlay, I am trying to create the relevant entries, as specified in http://www.openldap.org/doc/admin24/overlays.html#Password%20Policies I import two LDIFs, first: dn: ou=Policies,dc=example,dc=com objectClas

OpenLDAP mirror replication ldif format

Hi there, I recently installed a new Debian 6 and OpenLDAP to test the new ldif format configuration. The problem is that I do not have any base configuration to use slaptest to migrate my config to ldif format. My main concern is now to find a manual/tutorial, to be able to setup a mirror

export directory in LDIF format

I have a strange problem exporting my directory into LDIF format. I am using the "mdb" format with openldap. /usr/local/sbin/slapcat -l MyDomain.net.ldif -b "dc=MyDomain,dc=net" If I run this command after starting "slapd", it works fine. However, I have this config

Logging with LDIF format style

Hi ! Is there any way (overlay, script, patch, ...) to have OpenLDAP log with LDIF format style for easier debugging ? Sylvain

Re: Convert *.schema to *.ldif

On Tue, Apr 3, 2012 at 9:28 AM, Francis Swasey wrote: > I don't see any description in the admin guide about how to convert a > *.schema file into a > *.ldif file.  Google tells me that most people are using slaptest with the -F > and -f parameters > with a specially cra

Re: Convert *.schema to *.ldif

should be a fairly simple set of transformations.  Looking at the *.schema and *.ldif > that are provided with the openldap source - I am left wondering how they were created, since > they have comments, they were obviously not created via the slaptest -F -f method. > > I would like to

Re: Convert *.schema to *.ldif

Francis Swasey wrote: I don't see any description in the admin guide about how to convert a *.schema file into a *.ldif file. Google tells me that most people are using slaptest with the -F and -f parameters with a specially crafted slapd.conf file. As the person who is responsible

Re: Convert *.schema to *.ldif

On 4/3/12 11:50 AM, Howard Chu wrote: >> I don't see any description in the admin guide about how to convert a >> *.schema file into a >> *.ldif file. Google tells me that most people are using slaptest with the >> -F and -f parameters >> with a special

Re: Convert *.schema to *.ldif

Le 03/04/12 20:39, Francis Swasey a écrit : On 4/3/12 11:50 AM, Howard Chu wrote: I don't see any description in the admin guide about how to convert a *.schema file into a *.ldif file. Google tells me that most people are using slaptest with the -F and -f parameters with a spec

Re: Convert *.schema to *.ldif

On 3/4/2012 9:39 μμ, Francis Swasey wrote: If anyone is interested, I've thrown together a short perl script I believe it would be useful to all of us (I am interested too)! So, if it's OK with you, it would be nice of you if you published it here. Thanks, Nick

Re: Convert *.schema to *.ldif

Le 4/4/12 2:03 PM, Jonathan Clarke a écrit : Le 03/04/12 20:39, Francis Swasey a écrit : On 4/3/12 11:50 AM, Howard Chu wrote: I don't see any description in the admin guide about how to convert a *.schema file into a *.ldif file. Google tells me that most people are using slaptest

import ldif does not work

Hi list, I am fighting with openldap for some time now and I can't get it to work. I started clean. I've followed this tutorial, and everything works fine. I used followed the example and only changed dc=company,dc=com into dc=mycompany,dc=org. Then I want to import this file, because I am busy

Re: Openldap configuration import LDIF

Am Thu, 22 Aug 2013 14:49:02 +0200 schrieb felas : > hi, > > i have install OpenLdap in a UbuntuServer, in virtual with VirtualBox. > Now i want to import in Eclipse via Ldap Browser one file LDIF. > > I have a FQDN like this, ldap.***.***.com, and i add this > in /etc/host

Re: Openldap configuration import LDIF

On 08/22/13 14:49 +0200, felas wrote: i have install OpenLdap in a UbuntuServer, in virtual with VirtualBox. Now i want to import in Eclipse via Ldap Browser one file LDIF. I have a FQDN like this, ldap.***.***.com, and i add this in /etc/hosts this FQDN with a ip address 192.168.1.156, the ip

Re: Openldap configuration import LDIF

thanks!, i re configure my slapd, i no touch the /etc/hosts file, and qhen i open Eclipse and LDAP Browser the connection is ok and the authentication too, but now when i try to import this file LDIF my error is: No such object...help please.. 2013/8/22 Dan White > On 08/22/13 14:49 +0

Re: Openldap configuration import LDIF

2013/8/22 Dan White On 08/22/13 14:49 +0200, felas wrote: i have install OpenLdap in a UbuntuServer, in virtual with VirtualBox. Now i want to import in Eclipse via Ldap Browser one file LDIF. I have a FQDN like this, ldap.***.***.com, and i add this in /etc/hosts this FQDN with a ip

Re: Openldap configuration import LDIF

hi, my ldif file start with: dn: ou=student,ou=people,dc=university,dc=org objectClass: organizationalUnit ou: student userPassword:: e01ENX1renFqNTdyF4M1V1M2RWxVeEY4S3VRoo0= my localserver ldap.conf is: BASE dc=university,dc=org URI ldap://192.168.1.2 you need a cn=config ? or a

Re: Openldap configuration import LDIF

2013/8/22 Dan White I an unable to come up with a theory as to how the /etc/hosts modification is causing the "No such object" error. I believe the devil is in the details here - that is, you likely have bad data in your ldif file. Double check your ldif file carefully. On 08/2

Re: Openldap configuration import LDIF

theory as to how the /etc/hosts >>> modification >>> is causing the "No such object" error. >>> >>> I believe the devil is in the details here - that is, you likely have bad >>> data in your ldif file. Double check your ldif file carefully. &

RE: Openldap configuration import LDIF

> Sorry i move first step in openlad, so, the all output in my Eclipse is > in attachment. > what do you mean Does ou=people,dc=university,dc=org exist? , you mean > in the server configuration? >  If you want to store ou=student,ou=people,dc=university,dc=org then the object with DN ou=people,

Re: Openldap configuration import LDIF

=org must first be created. If that's your problem, add it to the top of your ldif file. -- Dan White

Re: Openldap configuration import LDIF

If i try slapcat -n1 i have result in a email attachment "slapcat", and if i add on the top the file LDIF ou=people,dc=university,dc=org, the error is LDAP: error code 17 - dn: attribute type undefined, for details i add a email attachment "error" 2013/8/22 Dan White >

RE: Openldap configuration import LDIF

> Date: Fri, 23 Aug 2013 10:02:39 +0200 > Subject: Re: Openldap configuration import LDIF > From: fela...@gmail.com > To: dwh...@olp.net > CC: openldap-technical@openldap.org > > If i try slapcat -n1 i have result in a email attachment &

Re: Openldap configuration import LDIF

i create a (example) Ldif in email attachment, thanks. The file is withoout add " ou=people,dc=university,dc=org" in the top 2013/8/23 Chris Card > > > Date: Fri, 23 Aug 2013 10:02:39 +0200 > > Subject: Re: Openldap configuration i

RE: Openldap configuration import LDIF

> Date: Fri, 23 Aug 2013 11:01:52 +0200 > Subject: Re: Openldap configuration import LDIF > From: fela...@gmail.com > To: ctc...@hotmail.com > CC: openldap-technical@openldap.org > > i create a (example) Ldif in email attachment

Re: Openldap configuration import LDIF

A ok. if you want i can post the log file from my Eclipse too. 2013/8/23 Chris Card > > > Date: Fri, 23 Aug 2013 11:01:52 +0200 > > Subject: Re: Openldap configuration import LDIF > > From: fela...@gmail.com > > To: ctc...@hotmail.com

RE: Openldap configuration import LDIF

> Date: Fri, 23 Aug 2013 11:01:52 +0200 > Subject: Re: Openldap configuration import LDIF > From: fela...@gmail.com > To: ctc...@hotmail.com > CC: openldap-technical@openldap.org > > i create a (example) Ldif in email attachment

Re: Openldap configuration import LDIF

I try to remove and i post you the log file 2013/8/23 Chris Card > > > Date: Fri, 23 Aug 2013 11:01:52 +0200 > > Subject: Re: Openldap configuration import LDIF > > From: fela...@gmail.com > > To: ctc...@hotmail.com > > CC

RE: Openldap configuration import LDIF

> Date: Fri, 23 Aug 2013 11:25:29 +0200 > Subject: Re: Openldap configuration import LDIF > From: fela...@gmail.com > To: ctc...@hotmail.com > CC: openldap-technical@openldap.org > > I try to remove and i post you the log file  #!RESU

Re: Openldap configuration import LDIF

a ok, and how i can define this in my schema? 2013/8/23 Chris Card > > > Date: Fri, 23 Aug 2013 11:25:29 +0200 > > Subject: Re: Openldap configuration import LDIF > > From: fela...@gmail.com > > To: ctc...@hotmail.com > > CC

RE: Openldap configuration import LDIF

> Date: Fri, 23 Aug 2013 11:58:52 +0200 > Subject: Re: Openldap configuration import LDIF > From: fela...@gmail.com > To: ctc...@hotmail.com > CC: openldap-technical@openldap.org > > a ok, and how i can define this in my schema?  openld

Re: Openldap configuration import LDIF

g 2013 11:25:29 +0200 > Subject: Re: Openldap configuration import LDIF > From: fela...@gmail.com <mailto:fela...@gmail.com> > To: ctc...@hotmail.com <mailto:ctc...@hotmail.com> > CC: openldap-technical@openldap.org <mailto:openldap-technical@openlda

Re: Openldap configuration import LDIF

n might be: why do you need objectClass: mmXinec > or where is it from. > > >> 2013/8/23 Chris Card mailto:ctc...@hotmail.com>> >> >> __**__ >> > Date: Fri, 23 Aug 2013 11:25:29 +0200 >> > Subject: Re:

Re: Encoded entries on LDIF file

On 01/04/2010 07:33 PM, Diego Lima wrote: Hello all, I'm trying to import an LDIF file where some users have values that appear to be encoded on the file. The values have two : (i.e. ::) and appear like this: # entry-id: 36545 dn: uid=someuser,ou=funcionarios,ou=pessoal,o=xxx,c=

Re: Encoded entries on LDIF file

Diego Lima writes: > I'm trying to import an LDIF file where some users have values that appear > to be encoded on the file. The values have two : (i.e. ::) and appear like > this: See the ldif(5) manpage. '::' means that the attribute value is base64-encoded in the LDIF

Re: Error 53 applying syncrepl LDIF

--On Friday, January 29, 2010 1:56 PM -0700 Hung Luu wrote: Hello all, In a syncrepl setup, I understand that the syncrepl specification is defined on the consumer server. I understand this to mean that I should apply my LDIF (that adds the olcSyncrepl attribute to my config and hdb backends

Re: Error 53 applying syncrepl LDIF

and this to mean that I should >> apply my LDIF (that adds the olcSyncrepl attribute to my config and hdb >> backends) on the consumer server. However, ldapadd was only successful in >> configuring my config backend for syncrepl, which is defined first in the >> LDIF, an

Re: Error 53 applying syncrepl LDIF

--On Friday, January 29, 2010 2:39 PM -0700 Hung Luu wrote: Are you able to get it to work with ldapadd as well? I'm getting a segmentation fault using ldapmodify (installed as part of openldap-clients.x86_64 rpm 2.3.43-3.el5). I would suggest you use a 2.4 version of ldapmodify and/or ldapa

Re: Error 53 applying syncrepl LDIF

leader in open source messaging and collaboration > This is interesting -- if I apply the hdb LDIF _before_ the config LDIF then ldapadd has no complaints. Reversing the order of my entries in the LDIF so the olcSyncrepl attribute is added to the hdb backend first did the trick. dn: olcDatabase

Re: about LDIF operation by API

> It seems nothing is provided for operating LDIF. How to implement ldif > export and import with C/C++ in OpenLDAP. In HEAD there is a not yet released API for parsing LDIF into data structures. See ITS#6194. p.

Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX

--On January 13, 2011 11:42:29 AM +0600 Konstantin Boyandin wrote: Hello, OpenLDAP version: 2.3.43-12 (CentOS 5.5), 64-bit. In order to enable ppolicy overlay, I am trying to create the relevant entries, as specified in http://www.openldap.org/doc/admin24/overlays.html#Password%20Policie

Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX

13.01.2011 11:55, Quanah Gibson-Mount пишет: > > > --On January 13, 2011 11:42:29 AM +0600 Konstantin Boyandin > wrote: > >> Hello, >> >> OpenLDAP version: 2.3.43-12 (CentOS 5.5), 64-bit. >> >> In order to enable ppolicy overlay, I am trying to create the relevant >> entries, as specified in >>

Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX

...@openldap.org To: Quanah Gibson-Mount Cc: openldap-technical@openldap.org Sent: Wed Jan 12 23:38:54 2011 Subject: Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX 13.01.2011 11:55, Quanah Gibson-Mount пишет: > > > --On January 13, 2011 11:42:29 AM +0600 Konstantin Boyandin >

Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX

Original Message - > From: openldap-technical-boun...@openldap.org > > To: Quanah Gibson-Mount > Cc: openldap-technical@openldap.org > Sent: Wed Jan 12 23:38:54 2011 > Subject: Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX > > 13.01.2011 11:55, Quanah Gibson-Mo

Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX

Perhaps try man slapo_ppolicy - it should hopefully provide the limits and acceptable values and compare with your ldif to find the cause of "Error description: An invalid attribute value was specified." Alternative: reduce the number of attributes (divide and conquer) to find th

Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX

ap.org Sent: Wed Jan 12 23:38:54 2011 Subject: Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX 13.01.2011 11:55, Quanah Gibson-Mount пишет: --On January 13, 2011 11:42:29 AM +0600 Konstantin Boyandin wrote: Hello, OpenLDAP version: 2.3.43-12 (CentOS 5.5), 64-bit. In order to e

Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX

Konstantin Boyandin wrote: Hello, OpenLDAP version: 2.3.43-12 (CentOS 5.5), 64-bit. In order to enable ppolicy overlay, I am trying to create the relevant entries, as specified in http://www.openldap.org/doc/admin24/overlays.html#Password%20Policies I import two LDIFs, first: dn: ou=Policies

Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX

Am Thu, 13 Jan 2011 11:42:29 +0600 schrieb Konstantin Boyandin : > Hello, > > OpenLDAP version: 2.3.43-12 (CentOS 5.5), 64-bit. > > In order to enable ppolicy overlay, I am trying to create the relevant > entries, as specified in > > http://www.openldap.org/doc/admin24/overlays.html#Password%20

Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX

ou > the actual error message sent from the server. OpenLDAP slapd will > always identify the actual attribute and value that causes an error. I > suggest you try importing this entry with OpenLDAP's ldapadd and examine > the error message from there. I tried importing with slapadd

Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX

Chris Jacobs wrote: Perhaps try man slapo_ppolicy The man page name is slapo-ppolicy(5). - it should hopefully provide the limits and acceptable values and compare with your ldif to find the cause of "Error description: An invalid attribute value was specified." Alternative:

Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX

13.01.2011 14:16, Pierangelo Masarati writes: > Chris Jacobs wrote: >> Perhaps try man slapo_ppolicy > > The man page name is slapo-ppolicy(5). > >> - it should hopefully provide the limits and acceptable values and >> compare with your ldif to find the cause of &qu

Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX

entry (line=22) The error above refers to the allowed value of pwdAttribute, which can only be userPassword now. The problem is the value for this attribute in LDIF *is* userPassword, as in the cited sample. I checked the LDIF - no 'invisible' characters around the value. Sounds like yo

Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX

Pierangelo Masarati wrote: Chris Jacobs wrote: Perhaps try man slapo_ppolicy The man page name is slapo-ppolicy(5). - it should hopefully provide the limits and acceptable values and compare with your ldif to find the cause of "Error description: An invalid attribute value was spec

Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX

Konstantin Boyandin wrote: Or check the archives, e.g. : for some time, in OpenLDAP 2.3, the pwdAttribute could only contain OIDs. Thank you very much! After I changed the string to pwdAttribute: 2.5.4.35 the import was a

Re: Problems importing ppolicy LDIF: LDAP_INVALID_SYNTAX

Pierangelo Masarati wrote: Konstantin Boyandin wrote: Or check the archives, e.g. : for some time, in OpenLDAP 2.3, the pwdAttribute could only contain OIDs. Thank you very much! After I changed the string to pwdAttribute:

Re: OpenLDAP mirror replication ldif format

o use cn=config rather than the slapd.conf setup. On Wed, Jun 29, 2011 at 12:17:10PM +0200, Simon Massart wrote: >Hi there, > >I recently installed a new Debian 6 and OpenLDAP to test the new ldif >format configuration. > >The problem is that I do not have any b

Re: export directory in LDIF format

--On November 10, 2014 at 7:00:58 AM -0500 Jerry wrote: I have a strange problem exporting my directory into LDIF format. I am using the "mdb" format with openldap. /usr/local/sbin/slapcat -l MyDomain.net.ldif -b "dc=MyDomain,dc=net" slapcat does not require sl

Re: export directory in LDIF format

On Mon, 10 Nov 2014 07:42:44 -0800 Quanah Gibson-Mount wrote: > --On November 10, 2014 at 7:00:58 AM -0500 Jerry > wrote: > > > I have a strange problem exporting my directory into LDIF format. I am > > using the "mdb" format with openldap. > > > > /

Re: export directory in LDIF format

On Tue, Nov 11, 2014 at 07:46:19AM -0500, Jerry wrote: > This is the actual code I am using in CRON: > > nice /usr/local/sbin/slapcat -f /usr/local/etc/openldap/slapd.conf -b > "dc=MyDomain,dc=net" -l usr/home/gerard/LDAP_Backup/MyDomain.net.ldif Try running it under 'strace' so you can see wh

manually editing LDIF files with schema

Hello, I wrote a test schema file adding one attribute - ipPhone. I found some "tutorials" explaining how to write a schema file then convert it into LDIF using slaptest(8). The authors of these tutorials [found by me] all manually edit slaptest(8)-generated LDIF files

LDIF modify in a replication server

Hi all, I'm trying to do a LDIF import (via Apache Directory Studio) after a replication issue. The goal is to correct a replication error. The problem is that when I try to import the LDIF file, I'm receiving the following error : > #!ERROR [LDAP: error code 53 - shadow conte

Re: Logging with LDIF format style

--On Thursday, November 17, 2016 3:27 PM +0100 Sylvain wrote: Hi ! Is there any way (overlay, script, patch, ...) to have OpenLDAP log with LDIF format style for easier debugging ? man slapo-accesslog ? DESCRIPTION The Access Logging overlay can be used to record all

Re: Logging with LDIF format style

s there any way (overlay, script, patch, ...) to have OpenLDAP log with >> LDIF format style for easier debugging ? >> > > man slapo-accesslog ? > > DESCRIPTION > The Access Logging overlay can be used to record all accesses > to a > given backend d

Re: import ldif does not work

m into > dc=mycompany,dc=org. ... > dn: o=mycompany.org Which is it you want: dc=mycompany,dc=org or o=mycompany.org ? > But when I want to import, I get this: > > [root@CentOS-01 cn=config]# ldapadd -W -D cn=admin,dc=mycompany,dc=org -v > -x -f /tmp/mycompanyorg.ldif So the LDI

Re: import ldif does not work

Indeed, it had to be mycompany. Thank you very much, it now works! Regards, Karntol On Thu, Jul 19, 2012 at 8:39 PM, Karntol Dernsef wrote: > Hi list, > > I am fighting with openldap for some time now and I can't get it to work. > > I started clean. > I've followed this tutorial, and everything

Re: manually editing LDIF files with schema

--On Thursday, December 04, 2014 11:00 AM +0200 Igor Shmukler wrote: Hello, I wrote a test schema file adding one attribute - ipPhone. I found some "tutorials" explaining how to write a schema file then convert it into LDIF using slaptest(8). The authors of these tutorials [found

Antw: Re: export directory in LDIF format

>>> Jerry schrieb am 11.11.2014 um 13:46 in Nachricht <2014074619.038904f6@scorpio>: [...] > This is the actual code I am using in CRON: > > nice /usr/local/sbin/slapcat -f /usr/local/etc/openldap/slapd.conf -b > "dc=MyDomain,dc=net" -l usr/home/gerard/LDAP_Backup/MyDomain.net.ldif > > Ori

slapadd 4096-character LDIF line length limitation

I wanted to ask if someone could shed some light on the 4096 character LDIF line length limitation, which seems to have been introduced sometime after 2.4.25. I learned about this the hard way, while trying to slapadd an LDIF file with long jpegPhoto attributes (e.g. 50K+) which loaded just

luseradd 30 minutes after restore ldif backup.

I install a new server with LDAP: slapd 2.4.39 And database "MDB". After installation, I use luseradd and adds the user very quickly. But if I restored a backup file BKP.LDIF another server you are running with bdb. /etc/init.d/slapd stop rm -f / var / lib / ldap / * -v -l slapadd /root/BKP.LDI

Failure while importing an exported ldif file

Hi @All, now while my ldapserver is working on my testmachine, i'am trying to import my ldif files. I read the thread http://www.openldap.org/lists/openldap-software/200711/msg00069.html but the import isn't working for me. abirndt@lvps83-169-33-218:~/openldap_2axels-company$ su

ldif, a person with city and country

I am not sure how to structure this. Are there any ldif file around I can have a look that deal with subscriptions like this? Jobst

Re: Correct way to load LDIF in mirrormode

contextCSN Ahh... That's of course right. But that will also more than double the time needed to load a backup on a mirrormode setup. This procedure should only be needed if the LDIF doesn't already contain correct CSNs. If you're loading a backup from a 2.4 slapcat you can jus

Re: Correct way to load LDIF in mirrormode

consistent entryCSN and contextCSN Ahh... That's of course right. But that will also more than double the time needed to load a backup on a mirrormode setup. This procedure should only be needed if the LDIF doesn't already contain correct CSNs. If you're loading a backup from a

Re: Correct way to load LDIF in mirrormode

1 this ensures you have consistent entryCSN and contextCSN Ahh... That's of course right. But that will also more than double the time needed to load a backup on a mirrormode setup. This procedure should only be needed if the LDIF doesn't already contain correct CSNs. If you&#x

Re: Correct way to load LDIF in mirrormode

the slapcat from server 1 this ensures you have consistent entryCSN and contextCSN Ahh... That's of course right. But that will also more than double the time needed to load a backup on a mirrormode setup. This procedure should only be needed if the LDIF doesn't already contain co

Re: Correct way to load LDIF in mirrormode

Pierangelo Masarati wrote: But if I'm loading the same data into both servers in a mirromode setup, then I shouldn't really have any use for the old CSN values, should I? So instead of sed/perl chaing the CSN's I could just remove them from the LDIF and let sladadd generate new

Re: Correct way to load LDIF in mirrormode

sing the slapcat from server 1 > > this ensures you have consistent entryCSN and contextCSN > So can i say that in mirrormode, there is never a need to provide -S unless you are initializing the first server (sid 1) from a ldif without valid CSN's etc, eg. by providing the "-S 1 -w&quo

Re: Correct way to load LDIF in mirrormode

the SID of server 1) > and -w > > - slapcat server 1 > > - slapadd server 2 using the slapcat from server 1 > > this ensures you have consistent entryCSN and contextCSN > > > So can i say that in mirrormode, there is never a need to provide -S >

Re: Correct way to load LDIF in mirrormode

On Sat, Nov 21, 2009 at 7:10 PM, Howard Chu wrote: > > If this is true, then would i also be correct is saying that -S > > only sets a parameter to enable the -w option to set the SID correctly > > in CSN's etc? and that the value provided by -S has no effect if -w is > > not provided ? > > No.

Re: Correct way to load LDIF in mirrormode

Brett @Google wrote: > On Sat, Nov 21, 2009 at 7:10 PM, Howard Chu > wrote: > > > If this is true, then would i also be correct is saying that -S > > only sets a parameter to enable the -w option to set the SID correctly > > in CSN's etc? and that the value pro

Re: Correct way to load LDIF in mirrormode

imal entryCSN, which becomes the contextCSN (either recently generated, or provided as part of the LDIF being loaded) If the -S is not provided, it defaults to 0. Thanks for your patience.. Cheers Brett

Re: Correct way to load LDIF in mirrormode

gt; > If the -w option is provided, then the entryCSN's are searched for the > maximal entryCSN, which becomes the contextCSN (either recently generated, > or provided as part of the LDIF being loaded) > > If the -S is not provided, it defaults to 0. Just to clarify (your first st

Textual LDIF backup strategies for busy LDAP clusters

Dear Folks, our old backup system for our LDAP clusters using slurpd is as follows: 1. A dedicated slave (we call it a "sync") has a replogfile configured. 2. A cron job moves the replog file to a backup directory every 15 minutes. 3. Another cron job runs every 24 hours, which: a. Stop

slapcat generate extra "space" characters in LDIF output

Hello I'm in trouble with slapcat when generating a LDIF file it puts some extra "space" characters into some dn longer than 80 characters. is there a way to change the output format of slapcat command to generate lines longer than 80 characters in the LDIF file ? I need this

  1   2   >