[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: OpenLDAP 2.4.10 Import Errors
Thanks for this. Having studied the standard schema files, there seems
to be no definition for the 'name' attribute (there is one entry that is
commented out, if I uncomment it out LDAP complains about duplicate
attributes) - is it somehow "built-in" to the system?
I can't even add the attributes manually via the browser - I see error
in the slapd log saying;
ntry (o=ATT,dc=npr), attribute 'openscheduledreports' not allowed
entry failed schema check: attribute 'openscheduledreports' not allowed
conn=1 op=7 RESULT tag=103 err=65 text=attribute 'openscheduledreports'
not allowed
I'm not really sure what you mean about UTF-8 and Latin-1....looking at
the LDIF export file I see data like this for the problem attributes;
vpnbookmarks: Site to Site Response
Time=/cgi-bin/VPN/s2sresp.pl?MONTH=-1m&g_
output_type=HTML&ACCOUNT_CODE=OMRNGRUA:1;FR6HLO00,BEOMR,NLOMN,DKOMRON,SE
OMR,
CHKZOM,NO615501,FIOMRON&pgsz=50
vpnscheduledreports:
999533103=outputformat>>HTML,,shortname>>Monthly%20Frame
%20Delivery%20CWT,,status>>a,,buildsLeft>>i,,date>>2001-09-03,,_id>>9995
3310
3,,lastBuild>>2008-10-01,,private>>no,,description>>,,service>>NPR,,freq
uenc
y>>w0,,userprofile>>,,domain>>,,emailrecipients>>thomas_cordier%40nl.ibm
.com
,,user>>thomas,,reportURL>>http%3A%2F%2F141.94.158.230%2Fcgi-bin%2FVPN%2
Fpca
p_frdel.pl%3FMONTH%3D-1m%26g_output_type%3DCSV%26ACCOUNT_CODE%3DCWTGRUA%
253A
1%253BCWAG%252CSECWL%252CPTCWT%252CNLCWT%252CITY634%252CGBCWT%252CDKWAGO
NS%2
52CESCWT%252CCHCWT%252CCHKWLT%252CAPTR%252CDEONL%252CFR4COA00%252CBEWGL%
26pg
sz%3D5000%26%2FALL%253AFROMROUT%253A%2521%257E%253AIGN%26%2FALL%253AFROM
ROUT
%253A%2521%257E%253AEhningen%26%2FALL%253ATOROUT%253A%2521%257E%253AIGN%
26%2
FALL%253ATOROUT%253A%2521%257E%253AEhningen,,organization>>AT%26T%20Glob
al%2
0Network%20Services
openbookmarks: Link
Usage=/cgi-bin/Opennet/link_usage.pl?ACCOUNT_CODE=&DATE=&
g_output_type=HTML&pgsz=150&tonen=Show
Regards,
Mark
-----Original Message-----
From: Hallvard Breien Furuseth [mailto:h.b.furuseth@usit.uio.no]
Sent: 02 October 2008 16:16
To: Lydon, Mark
Cc: openldap-technical@openldap.org
Subject: Re: OpenLDAP 2.4.10 Import Errors
Lydon, Mark writes:
> Root error: [LDAP: error code 21 - vpnscheduledreports: value #0
> invalid per syntax]
> 05:21:23 PM: Failed to synchronize entries Root error: [LDAP: error
> code 21 - vpnbookmarks: value #0 invalid per syntax]
> 05:21:24 PM: Failed to synchronize entries Root error: [LDAP: error
> code 21 - useraccounts: value #0 invalid per syntax]
These attributes are derived from attribute 'name', so they get
Directory String syntax (like most LDAP attributes). Directory String
in LDAPv3 takes a non-empty UTF-8 string. Maybe your attributes are
Latin-1, and your old server either is an LDAPv2 server (LDAPv2
character sets were a complete jungle) or does not check the syntax? If
so the correct fix is to convert to UTF-8. However maybe that breaks
your current applications, if they expect Latin-1... (You could hack
the schema to use another syntax, but that easily becomes a maintenance
nightmare and could have compatibility problems of its own.)
--
Hallvard