I would:

1) tail -f dspace.log, try to log into dspace using ldap and watch for
any useful log messages

2) if that doesn't help, capture network communication between your
dspace and ldap server:
dspace@dspace:~$ tshark -i eth0 -p -f "host 1.2.3.4" -w output.cap
user@local:~$ wireshark output.cap
This may help reval a) whether there's any communication at all and b)
any responses from the LDAP server that might fail to show up in the
dspace log.


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

-- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Reply via email to