User manual

Chapter 10
The output this time tells us that there is an active
zebrasry
process.
A common reason for the Zebra server being down is that it is not configured to
start up when the machines reboots.
On Debian, we use the
update -rc .d
command to set this up:
linux -4yut: /home /koha # sudo update -rc.d koha- zebra - daemon defaults
On openSuSE, we use the
chkconf ig
command to set this up:
koha @ linux: /home /koha # sudo chkconfig koha- zebra - daemon on
On openSuSE, if you are not using the
koha- zebra - daemon
service, you can
setup the
zebrasry
command in the
/etc /finit . d /boot . local
file. Edit the
boot . local
file:
koha @ linux: -> sudo vi /etc /init.d /boot. local
And add the
zebrasry
command to the file somewhere near the end of the file,
as follows:
/usr/bin/zebrasrv -f /etc/koha-dev/etc/koha-conf.xml &
There could be several reasons for the server coming down; look at the Zebra server
log file for clues:
koha @ linux: /home /koha # tail -f / etc /koha -dev /var /log /zebrasrv.log
For more information on configuring a Zebra server, see Chapter 4, Koha's Web
Installer, Cron tab, and Other Server Configurations.
Zebra index rebuild not working
You should know there is a problem with the rebuild process when changes to
catalog items -new records, edits to records, or changes in checkout statuses do not
reflect properly in search results on the OPAC and in the Staff Client.
The rebuild process may not be running due to several reasons.
If the rebuild process is setup correctly in the Crontab, you should see something like
this in the messages log:
koha @ linux: /home /koha # tail -f /var /log /messages
Jun
3 16:14:01 koha @ linux /usr /sbin /cron[4010]: (root) CMD
( /home /koha/
kohaclone /misc/ migration _tools /rebuild_zebra.pl -b -a -z » /home /koha/
logs /zebra.log 2> &1
[ 203 ]