We are all very new to Koha and Zebra. With Zebra search turned off I can do a keyword search only. With Zebra turned on, I can’t search. I am beginning to suspect that the zebra.cfg file is either missing or in the wrong location on the Ubuntu 7.10 installation.
When I try to start the zebrasrv I get two responses:
$ sudo zebrasrv start
17:39:34-13/01 [server] Adding dynamic listener on start id=0
17:39:34-13/01 [fatal] Failed to listen on start
The zebra-biblios.cfg and zebra-authorities.cfg files seem to exist in /etc/koha/zebradb.
However, I do see a zebrasrv process running when I look at my running processes via Webmin.
|
0.0 % |
17:04 |
/usr/bin/zebrasrv -f /etc/koha/koha-conf.xml |
From: Mason James
[mailto:mason.james@liblime.com]
Sent: Sunday, January 13, 2008
2:52 PM
To: Chadwick, John, DCA
Cc: koha-devel@nongnu.org
Subject: Re: [Koha-devel] Koha 3.0
success
On 2008/01/12, at 8:47 AM, Chadwick, John, DCA wrote:
The only issue we have now is that we
can’t do a search from the OPAC. The screens display okay, but a search
by title or author of materials we have imported are not showing up in search
results.
John
Hi John,
just my 2 cents
it seems like you probably have imported your marc records ok into koha
but your zebra isnt setup, running, or indexed correctly
ive had a similar issue too
you can verify that you have koha records like this, in your DB
mysql> select * from biblio;
or
if you a result there, you have records (or, at least 1 :)
=======================================
check that your 'Nozeb' syspref is set to '0'
next, rebuild your zebra indexes again (cant hurt :), something like this....
$export KOHA_CONF="/home/mtj/koha/etc/koha-conf.xml"
$ koha/misc/migration_tools/rebuild_zebra.pl -b
which will take a few minutes. fmmv
make sure your zebrasrv process is running, and now try a OPAC search
that could take care of your issue.
Cheers, Mason
--
Mason James mason.james@liblime.com
Programmer www.liblime.com
LibLime +64 21 542 117
______________________________________________________________________
This inbound email has been scanned by the MessageLabs Email Security System.
______________________________________________________________________