Re^3: Using Mozilla::LDAP instead of Net::LDAP

[strat]

What does the Server log tell you?

Do you do error handling in your code? if yes, the server will tell you about timeouts etc. Which error messages is given?

[LittleGreyCat]

Strat,

there is error handling in the code; however the symptoms are:
(1) A search completes without error, returning the expected (large amount of) data.
(2) The next searches fails 'Unable to contact LDAP server' (or similar).

The server log shows that the connection was unbound after the successful search in (1) although the code did not issue an 'unbind'.

This in turn explains the unexpected failure in (2) as there is no longer a connection.

I have not yet located a log which shows any error associated with the connection which unexpectedly 'unbound'.

I have so far been unable to reproduce the fault on a test system, and I am reluctant to propose upping the server logging on an extremely heavily loaded live service.

Regards

Dave R.

[strat]

To be able to help you, I need more specific information:

1. the output of the following line after the first search: $conn->printError() if $conn->getErrorCode(); If there's no output, then also put it into the loop where you are fetching the entries.
2. which LDAP Server you use (also which patch level; e.g. IBM Tivoli Directory Server 5.2 without patches sometimes behaves strange)
3. see some code, especially the connect/bind and search properties.

[LittleGreyCat]

strat,

I am now down into the depths of Solaris using ptree and the like, and pretty sure that this is an isssue with the X.500 directory we are using.

Thanks for your help so far; what I have found is that the Mozilla LDAP we are using is not very flexible; there is very little exposed in the 'search' method and the 'API' code seems to break everything.

Investigation from the Perl end does not seem to be a good prospect.

I am now going to throw this at our directory supplier.

Regards

Dave R