[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: openldap-technical Digest, Vol 105, Issue 2
- To: "'openldap-technical@openldap.org'" <openldap-technical@openldap.org>
- Subject: RE: openldap-technical Digest, Vol 105, Issue 2
- From: "Kruger, P (Justid)" <p.kruger@justid.nl>
- Date: Wed, 3 Aug 2016 13:10:26 +0000
- Accept-language: nl-NL, en-US
- Content-language: nl-NL
- In-reply-to: <mailman.0.1470225601.18300.openldap-technical@openldap.org>
- References: <mailman.0.1470225601.18300.openldap-technical@openldap.org>
- Thread-index: AQHR7X66BXOOTT9oBUay02faZMsZTaA3NXyw
- Thread-topic: openldap-technical Digest, Vol 105, Issue 2
You could check fort he logfiles. But to get logging detailed, you need to set the loglevel.
You can save ldap logging to a separate logfile and added logging level. Below is what I've done under Linux to achieve this (nano is the editor, which could also be vi).
mkdir /var/log/ldap/
touch /var/log/ldap/ldap.log
chown ldap.ldap /var/log/ldap -R
nano /etc/rsyslog.conf
Add the following rule tot his file
# Save LDAP messages to /var/log/ldap/ldap.log
local4.* /var/log/ldap/ldap.log
Add log rotation to prevent an ever growing log file.
nano /etc/logrotate.d/ldap.log
/var/log/ldap/ldap.log {
missingok
}
service rsyslog restart
Met vriendelijke groet,
Peter Kruger
Adviseur IT-beheer
..................................................................................
Ministerie van Justitie
Justitiële Informatiedienst
Technologie/IT-beheer
Egbert Gorterstraat 6 | 7607 GB | Almelo | 2.15
Postbus 337 | 7600 AH | Almelo
..................................................................................
T 088 99 89060
M 06 511 016 92
p.kruger@justid.nl
www.justid.nl
..................................................................................
werkt op: ma, di, wo, do
..................................................................................
Van: Côme Chilliet [mailto:come@opensides.be]
Verzonden: dinsdag 2 augustus 2016 15:32
Aan: openldap-technical@openldap.org
Onderwerp: Modification of objectClass failing: how can I get details?
Hello,
I'm trying to modify an LDAP node to change its objectClasses:
dn: cn=canon-c5250,ou=printers,ou=systems,dc=xxx,dc=xxx
cn: canon-c5250
description:: Q2Fub24gSVIgQURWIEM1MjUwIA==
labeledURI: ipp://127.0.0.1
ipHostnumber: 127.0.0.1
macAddress: 12:12:12:12:12:12
objectClass: top
objectClass: gotoPrinter
I want to remove gotoPrinter objectClass which is flagged as OBSOLETE and instead use fdPrinter, ipHost and ieee802Device.
I try with an ldif with the following content:
dn: cn=canon-c5250,ou=printers,ou=systems,dc=xxx,dc=xxx
changetype: modify
replace: objectClass
objectClass: fdPrinter
objectClass: ieee802Device
objectClass: ipHost
objectClass: top
I get:
ldapadd -D cn=admin,dc=xxx,dc=xxx -f modify.ldif -W
ldap_modify: Object class violation (65)
How can I get more information? I don't know which violation that could be, as I am able to insert a second object with no problem which looks like what I want:
dn: cn=test-print,ou=printers,ou=systems,dc=xxx,dc=xxx
changetype: add
cn: test-print
description: test
labeledURI: ipp://127.0.0.1
ipHostnumber: 127.0.0.1
macAddress: 12:22:12:12:22:22
objectClass: fdPrinter
objectClass: ieee802Device
objectClass: ipHost
objectClass: top
Here are the classes definitions:
objectclass (1.3.6.1.4.1.10098.1.2.1.31 NAME 'gotoPrinter'
DESC 'GOto - Gonicus Terminal Concept, objectclass' SUP top STRUCTURAL
OBSOLETE
MUST ( cn )
MAY ( labeledURI $ description $ l $ gotoPrinterPPD $ macAddress $ ipHostNumber $ gotoUserPrinter $
gotoUserAdminPrinter $ gotoGroupPrinter $ gotoGroupAdminPrinter $
printerWindowsInfFile $ printerWindowsDriverDir $ printerWindowsDriverName) )
objectclass ( 1.3.6.1.4.1.38414.16.2.5 NAME 'fdPrinter'
DESC 'FusionDirectory printer class'
MUST ( cn )
MAY ( labeledURI $
fdPrinterWindowsInfFile $ fdPrinterWindowsDriverDir $ fdPrinterWindowsDriverName $
fdPrinterUsers $ fdPrinterAdminUsers))
Côme