Zebra misinterprets the <server> section for LDAP as a stanza for itself. As a result Zebra fails to run. I will be fixing this shortly, by moving and renaming the LDAP stanza. Please check back in the next week. I think the "file does not exist" error in templates is unrelated. --Joe On Fri, Jun 13, 2008 at 4:56 PM, Paul Landers <paul.landers@ttuhsc.edu> wrote:
We're evaluating Koha 3 with zebra. Both the OPAC and Intranet searches stopped returning any results once we successfully enabled LDAP support in koha-conf.xml per the man page for Auth_with_ldap.pm. The added stanza in koha-conf.xml is:
<!-- AUTHENTICATION ADDITION --> <server id="ldapserver" listenref="ldapserver"> <hostname>our_ldap_server</hostname> . . . </server>
The logged errors seem to imply zebra is choking on this stanza:
Errors logged in koha-zebradaemon-output.log -
15:49:03-13/06 [warn] Non-existent listenref 'ldapserver' in server config element 15:49:03-13/06 [fatal] Unknown element 'hostname' in config /etc/koha/ koha-conf.xml
Errors logged in koha-zebradaemon.err -
20080613 15:47:02 koha-zebra-ctl.koha: client (pid 19682) exited with 1 status 20080613 15:47:02 koha-zebra-ctl.koha: client (pid 19683) exited with 1 status 20080613 15:47:02 koha-zebra-ctl.koha: client (pid 19684) exited with 1 status 20080613 15:47:02 koha-zebra-ctl.koha: terminating too quickly, waiting 30 seconds
As a side note, l also noticed errors in koha-opac-error_log about a non-existent directory:
[Fri Jun 13 15:12:15 2008] [error] [client my_ip_address] File does not exist: /usr/share/koha/opac/htdocs/intranet-tmpl
Any assistance would be appreciated.
Thanks!