You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@directory.apache.org by Tod <th...@gmail.com> on 2007/07/30 16:11:42 UTC
Error reading children of base DN
I'm getting an error reading the children entries against a Lotus Domino
server. I understand the reason for the error, but I'm having trouble
finding the offending entry. Is there some debug method I can use to
track it down?
Thanks - Tod
Re: Error reading children of base DN
Posted by Tod <th...@gmail.com>.
Stefan Seelmann wrote:
> Hi Tod,
> In the meantime you could take a look to the log file. It is located
> under <HOME>/ldapstudio/.metadata/.log
Here are the log entries. The first try is expanding the baseDN, the
second is double clicking:
!SESSION 2007-07-31 08:33:10.669
-----------------------------------------------
eclipse.buildId=unknown
java.version=1.5.0_11
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.ui 4 4 2007-07-31 08:33:20.887
!MESSAGE Invalid Menu Extension (Path is invalid):
org.eclipse.search.OpenSearchDialog
!ENTRY org.apache.directory.ldapstudio.browser.core 4 4 2007-07-31
08:33:51.120
!MESSAGE Error while reading entry
!STACK 0
org.apache.directory.ldapstudio.browser.core.internal.model.ConnectionException:
Empty Attribute is not allowed!
at
org.apache.directory.ldapstudio.browser.core.internal.model.JNDIConnectionProvider$LdifEnumerationImpl.next(JNDIConnectionProvider.java:441)
at
org.apache.directory.ldapstudio.browser.core.internal.model.ConnectionSearchHandler.search(ConnectionSearchHandler.java:152)
at
org.apache.directory.ldapstudio.browser.core.internal.model.Connection.search(Connection.java:602)
at
org.apache.directory.ldapstudio.browser.core.jobs.InitializeChildrenJob.initializeChildren(InitializeChildrenJob.java:167)
at
org.apache.directory.ldapstudio.browser.core.jobs.InitializeChildrenJob.executeBulkJob(InitializeChildrenJob.java:98)
at
org.apache.directory.ldapstudio.browser.core.jobs.AbstractAsyncBulkJob.executeAsyncJob(AbstractAsyncBulkJob.java:38)
at
org.apache.directory.ldapstudio.browser.core.jobs.AbstractEclipseJob.run(AbstractEclipseJob.java:96)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
!SUBENTRY 1 org.apache.directory.ldapstudio.browser.core 4 4 2007-07-31
08:33:51.120
!MESSAGE Empty Attribute is not allowed!
!ENTRY org.apache.directory.ldapstudio.browser.core 4 4 2007-07-31
08:34:13.103
!MESSAGE Error while reading entry
!STACK 0
org.apache.directory.ldapstudio.browser.core.internal.model.ConnectionException:
Empty Attribute is not allowed!
at
org.apache.directory.ldapstudio.browser.core.internal.model.JNDIConnectionProvider$LdifEnumerationImpl.next(JNDIConnectionProvider.java:441)
at
org.apache.directory.ldapstudio.browser.core.internal.model.ConnectionSearchHandler.search(ConnectionSearchHandler.java:152)
at
org.apache.directory.ldapstudio.browser.core.internal.model.Connection.search(Connection.java:602)
at
org.apache.directory.ldapstudio.browser.core.jobs.InitializeChildrenJob.initializeChildren(InitializeChildrenJob.java:167)
at
org.apache.directory.ldapstudio.browser.core.jobs.InitializeChildrenJob.executeBulkJob(InitializeChildrenJob.java:98)
at
org.apache.directory.ldapstudio.browser.core.jobs.AbstractAsyncBulkJob.executeAsyncJob(AbstractAsyncBulkJob.java:38)
at
org.apache.directory.ldapstudio.browser.core.jobs.AbstractEclipseJob.run(AbstractEclipseJob.java:96)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
!SUBENTRY 1 org.apache.directory.ldapstudio.browser.core 4 4 2007-07-31
08:34:13.103
!MESSAGE Empty Attribute is not allowed!
- Tod
Re: Error reading children of base DN
Posted by Tod <th...@gmail.com>.
Stefan Seelmann wrote:
>> Ok, this turned up a sizeLimitExceeded(), that seems to be part of the
>> problem. I checked with the server owner and the size limit is set to
>> 100 entries. Its a credible return that, IMHO, probably shouldn't cause
>> an error.
>
> That shouldn't cause the error. Server-side size and time limit should
> be handled in Studio. Perhaps you could try to reduce the client-side
> size limit to less than the server-side limit? You could change the
> setting in the connection properties.
I reduced the client count limit down to 50 but that didn't help.
I have access to two domino servers, one with a size limit set to 100,
and one with unlimited. The unlimited server is working, the one with a
size limit is not.
When I run a command line ldapsearch against the unlimited box, I get
all of the entries back. When run against the limited box I get back
100 entries and an expected size limit exceeded error. This behavior is
also reflected using the Jarek Gawor LDAP browser.
Just food for thought. Let me know if I can help out in any way.
- Tod
Re: Error reading children of base DN
Posted by Stefan Seelmann <se...@apache.org>.
>> Another idea is to record the transfered search request and response
>> using Wireshark. Perhaps you could post such a dump here or just create
>> another Jira and attach the dump.
>
> Ok, this turned up a sizeLimitExceeded(), that seems to be part of the
> problem. I checked with the server owner and the size limit is set to
> 100 entries. Its a credible return that, IMHO, probably shouldn't cause
> an error.
That shouldn't cause the error. Server-side size and time limit should
be handled in Studio. Perhaps you could try to reduce the client-side
size limit to less than the server-side limit? You could change the
setting in the connection properties.
> I would post the Wireshark dump but there's too much proprietary data
> involved so I can't.
Ok, I understand.
> Let me know the next steps and if there's anything
> I can do to help.
Please stand by, many thanks for your patience!
Re: Error reading children of base DN
Posted by Tod <th...@gmail.com>.
Stefan Seelmann wrote:
> Hi Tod,
>
> Another idea is to record the transfered search request and response
> using Wireshark. Perhaps you could post such a dump here or just create
> another Jira and attach the dump.
Ok, this turned up a sizeLimitExceeded(), that seems to be part of the
problem. I checked with the server owner and the size limit is set to
100 entries. Its a credible return that, IMHO, probably shouldn't cause
an error.
I would post the Wireshark dump but there's too much proprietary data
involved so I can't. Let me know the next steps and if there's anything
I can do to help.
Thanks,
Tod
Re: Error reading children of base DN
Posted by Tod <th...@gmail.com>.
Stefan Seelmann wrote:
> Hi Tod,
>
>> As I was trying out the LDAP Studio on other LDAP servers, I pointed it
>> to the Domino box to see if it would work. When I tried to expand the
>> baseDn I got the following error "Error while reading entry Empty
>> Attribute is not allowed!".
>
> Which version of LDAP Studio are you using? In 0.8.0 we fixed some
> problems with the empty DN (RootDSE).
Windows version 0.8.1. If anyone gets a chance the current version
might come in handy in Help->About LDAP Studio.
> Does the error occur when you just single-click on the baseDN entry to
> show the attributes. Or does it occur when you expand the baseDN entry?
> Note: a double-click causes both, reading the entrie's attributes and
> its children. Please try to do this actions separately, just to isolate
> the error.
Both.
>> I understand the error above but I need more information to track down
>> the entry(ies) causing that error. It would be helpful if there was a
>> way to get more details from LDAP Studio so that I could discover the
>> problem with the directory and remove it, hence my post.
>
> Unfortunately, the logging capabilities in LDAP Studio/Apache Directory
> Studio aren't satisfying yet :-(
>
> There are two Jira issues about logging and error handling:
> http://issues.apache.org/jira/browse/DIRSTUDIO-155
> http://issues.apache.org/jira/browse/DIRSTUDIO-150
> Could you please add a comment with your special case so that we don't
> forget that case when fix the issues?
Sure, no problem.
> In the meantime you could take a look to the log file. It is located
> under <HOME>/ldapstudio/.metadata/.log
>
> You could also perform a search, starting at the base DN with one-level
> scope and no returning attributes. Then you could click to every search
> result entry to see if you could read them.
>
> Another idea is to record the transfered search request and response
> using Wireshark. Perhaps you could post such a dump here or just create
> another Jira and attach the dump.
I will give these suggestions a try and get back to the list by weeks
end. I'll probably Jira the network dump.
>> Incidentally, I just tried this on ADS and I get a "Error while reading
>> entry, Unprocessed Continuation Reference(s)" error when trying to
>> expand its baseDn. That's probably better saved for a separate thread...
>
> I guess you mean Active Directory with "ADS"? (Apache Directory Server
> uses the same acronym)
Yes sorry, no disrespect intended :)
If it helps your efforts I've been using Jarek Gawor's LDAP browser for
what seems like the last 10 years. I've not found anything faster or
better until I gave this one a shot. The Eclipse interface was a great
decision and the tool overall is fantastic. Kudos to the team.
- Tod
Re: Error reading children of base DN
Posted by Stefan Seelmann <se...@apache.org>.
Hi Tod,
> As I was trying out the LDAP Studio on other LDAP servers, I pointed it
> to the Domino box to see if it would work. When I tried to expand the
> baseDn I got the following error "Error while reading entry Empty
> Attribute is not allowed!".
Which version of LDAP Studio are you using? In 0.8.0 we fixed some
problems with the empty DN (RootDSE).
Does the error occur when you just single-click on the baseDN entry to
show the attributes. Or does it occur when you expand the baseDN entry?
Note: a double-click causes both, reading the entrie's attributes and
its children. Please try to do this actions separately, just to isolate
the error.
> I don't profess the virtues of Domino's (or ADS's) compliance with LDAP
> schema standards, I am just tasked in dealing with them :)
I feel with you ;-)
> I understand the error above but I need more information to track down
> the entry(ies) causing that error. It would be helpful if there was a
> way to get more details from LDAP Studio so that I could discover the
> problem with the directory and remove it, hence my post.
Unfortunately, the logging capabilities in LDAP Studio/Apache Directory
Studio aren't satisfying yet :-(
There are two Jira issues about logging and error handling:
http://issues.apache.org/jira/browse/DIRSTUDIO-155
http://issues.apache.org/jira/browse/DIRSTUDIO-150
Could you please add a comment with your special case so that we don't
forget that case when fix the issues?
In the meantime you could take a look to the log file. It is located
under <HOME>/ldapstudio/.metadata/.log
You could also perform a search, starting at the base DN with one-level
scope and no returning attributes. Then you could click to every search
result entry to see if you could read them.
Another idea is to record the transfered search request and response
using Wireshark. Perhaps you could post such a dump here or just create
another Jira and attach the dump.
>
> Incidentally, I just tried this on ADS and I get a "Error while reading
> entry, Unprocessed Continuation Reference(s)" error when trying to
> expand its baseDn. That's probably better saved for a separate thread...
I guess you mean Active Directory with "ADS"? (Apache Directory Server
uses the same acronym)
King Regards,
Stefan Seelmann
Re: Error reading children of base DN
Posted by Tod <th...@gmail.com>.
Stefan Zoerner wrote:
> Hi Tod!
>
>> I'm getting an error reading the children entries against a Lotus
>> Domino server. I understand the reason for the error, but I'm having
>> trouble finding the offending entry. Is there some debug method I can
>> use to track it down?
>>
>
> You might want to give us more information in order to get help. Am I
> right that you use Lotus Domino as your LDAP server? What technology do
> you use to retrieve the entries (JNDI? Java at all?) etc. What does
> "offending entry" mean? If it is not compliant to the schema, why is it
> in your directory? You probably mean something else (but what?).
There is a Domino server that houses information in its NAB that is
important to our customer. I can retrieve data using perl Net::LDAP
calls, as well as with C API calls. I haven't tried JNDI but I
*suspect* similar results.
As I was trying out the LDAP Studio on other LDAP servers, I pointed it
to the Domino box to see if it would work. When I tried to expand the
baseDn I got the following error "Error while reading entry Empty
Attribute is not allowed!".
I don't profess the virtues of Domino's (or ADS's) compliance with LDAP
schema standards, I am just tasked in dealing with them :)
> Please note that this is a mailing list primarily for users of Apache
> Directory software (like ApacheDS, Directory Studio ...). If you
> questions related to IBM products, this is likely not the right place to
> ask.
I understand the error above but I need more information to track down
the entry(ies) causing that error. It would be helpful if there was a
way to get more details from LDAP Studio so that I could discover the
problem with the directory and remove it, hence my post.
Incidentally, I just tried this on ADS and I get a "Error while reading
entry, Unprocessed Continuation Reference(s)" error when trying to
expand its baseDn. That's probably better saved for a separate thread...
Thanks - Tod
Re: Error reading children of base DN
Posted by Stefan Zoerner <st...@labeo.de>.
Hi Tod!
Tod wrote:
> I'm getting an error reading the children entries against a Lotus Domino
> server. I understand the reason for the error, but I'm having trouble
> finding the offending entry. Is there some debug method I can use to
> track it down?
>
> Thanks - Tod
You might want to give us more information in order to get help. Am I
right that you use Lotus Domino as your LDAP server? What technology do
you use to retrieve the entries (JNDI? Java at all?) etc. What does
"offending entry" mean? If it is not compliant to the schema, why is it
in your directory? You probably mean something else (but what?).
Please note that this is a mailing list primarily for users of Apache
Directory software (like ApacheDS, Directory Studio ...). If you
questions related to IBM products, this is likely not the right place to
ask.
Greetings from Hamburg,
Stefan