When I run the script to start the index, the script hangs after a few seconds of processing these LdapContrib entries. I am not sure if that is normal. I have install the LdapContrib and LDAP plugin and I authenticate via LDAP.

root@wiki-server:/var/www/foswiki/kinosearch/bin# sudo -u www-data ./kinoindex
KinoSearch index files init
- to suppress all normal output: kinoindex -q
- LdapContrib - constructed a new LdapContrib object
- LdapContrib - called initCache
- LdapContrib - constructed a new LdapContrib object
- LdapContrib - called initCache
- LdapContrib - called getWikiNameOfLogin(AdminGroup)

-- JoelDeJesus - 19 Dec 2009

Also, running http://wiki.e-flamingo.jp/foswiki/bin/rest/SearchEngineKinoSearchPlugin/index script yields this error:

Foswiki detected an internal error - please check your Foswiki logs and webserver logs for more information.

Can't fork

-- JoelDeJesus - 19 Dec 2009

i've seen this before, but it had nothing to do with LDAP (just the LDAP was in debug mode). i'm pretty sure that you're running into a form of Item5647. i recommend that you download the latest version KinoSearchContrib (v1.23) and try again. the logs are now properly flushed, so you should be able to see which attachment it is hanging on in kinosearch/logs now. perhaps it is a password-protected file, though i have seen the indexer hang on files that weren't password-protected. i have seen the indexer hang on a file which ks_test was able to parse and produce results for, as well. :-/