Occasionally the locks in /var/lock/koha/zebradb/biblios get their ownership changed to root. I'm not sure why, because rebuild_zebra is only done in the koha crontab. I run a little program in the middle of the night which reports on the state of the server and checks those locks. When I went in to change it back this morning I got:
koha@windingcircle:~> crontab -l # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/tmp/crontab.XXXXCP19dZ installed on Mon Sep 5 09:08:13 2011) # (Cron version V5.0 -- $Id: crontab.c,v 1.12 2004/01/23 18:56:42 vixie Exp $) MAILTO=bob PERL5LIB=/usr/share/koha/lib KOHA_CONF=/etc/koha/koha-conf.xml KOHA_BIN=/usr/share/koha/bin #M H D M W #*/15 6-23 * * * /usr/share/koha/bin/migration_tools/rebuild_zebra.pl -b -a -z >/dev/null 0 4 * * * /usr/share/koha/bin/migration_tools/rebuild_zebra.pl -b -a -r >/dev/null koha@windingcircle:~> env | grep -i koha GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/koha/.gtkrc-2.0-kde4:/home/koha/.gtkrc-2.0-qtengine:/home/koha/.gtkrc-2.0:/home/koha/.kde4/share/config/gtkrc-2.0 PERL5LIB=/usr/share/koha/lib GTK_RC_FILES=/etc/gtk/gtkrc:/home/koha/.gtkrc::/home/koha/.kde4/share/config/gtkrc GS_LIB=/home/koha/.fonts USER=koha MAIL=/var/spool/mail/koha PWD=/home/koha KOHA_CONF=/etc/koha/koha-conf.xml HOME=/home/koha LOGNAME=koha QT_PLUGIN_PATH=/home/koha/.kde4/lib64/kde4/plugins/:/usr/lib64/kde4/plugins/ koha@windingcircle:~> /usr/share/koha/bin/migration_tools/rebuild_zebra.pl -b -a -r 09:22:13-05/09 zebraidx(25533) [warn] No such record type: dom./etc/koha/zebradb/authorities/etc/dom-config-marc.xml 09:23:28-05/09 zebraidx(25559) [warn] No such record type: grs.marcxml.record koha@windingcircle:~> uname -a Linux windingcircle 2.6.34.10-0.2-desktop #1 SMP PREEMPT 2011-07-20 18:48:56 +0200 x86_64 x86_64 x86_64 GNU/Linux koha@windingcircle:~> cat /etc/issue Welcome to openSUSE 11.3 "Teal" - Kernel \r (\l).
After running that, I get no results on any search. I tried switching back to nozebra and did a rebuild_nozebra.pl. Searching finds biblios but no items. How do I find the record that's causing the problem? Is there any way I can get Koha running again? I just upgraded to Koha 3.04.04 -- Bob