At 11:55 AM 1/22/2015 +1300, you wrote:
Paul A schreef op wo 21-01-2015 om 17:10 [-0500]:
However, neither OPAC ("Results of search for 'kw,wrdl: smith' No results found! No results found for that in NMA catalog) nor staff-admin ("No results match your search for 'kw,wrdl: smith' in NMA Catalog") can find anything ...
First thing to try:
sudo service koha-common restart
Thanks Robin, paul@hood:/usr/sbin$ sudo service koha-common restart * Restarting Koha ILS koha-common Stopping Zebra server for k318 SIP server for k318 not running. * Error: Indexer not running for k318 [fail] So, then it bounced me around looking for indexer, SIP server and Zebra, which all appear to start, but service koha-common restart doesn't appear to want to play: paul@hood:/usr/sbin$ sudo koha-indexer --start k318 * Starting Koha indexing daemon for k318 paul@hood:/usr/sbin$ sudo koha-start-sip k318 Starting SIP server for k318 paul@hood:/usr/sbin$ sudo koha-start-zebra k318 Starting Zebra server for k318 paul@hood:/usr/sbin$ sudo service koha-common restart * Restarting Koha ILS koha-common Zebra already stopped for instance k318. SIP server for k318 not running. * Error: Indexer not running for k318 [fail] Best and again thanks -- Paul --- Paul Adamthwaite, Ph.D., Executive Director --- Canadian Society of Marine Artists 205, Main Street, Picton, Ontario, K0K 2T0, Canada Telephone: 1 613 476 1177 E-mail: <info@ultramarine.ca> Web: <http://www.ultramarine.ca> Dedicated to Canadian marine art.
Paul A schreef op wo 21-01-2015 om 18:53 [-0500]:
So, then it bounced me around looking for indexer, SIP server and Zebra, which all appear to start, but service koha-common restart doesn't appear to want to play:
You probably don't want the indexer at this stage. By default, it's not enabled (specified in /etc/default/koha-common), though I can't remember exactly what version that came in on. You just want to make sure that zebra is correctly running. Ignore the indexer as that's not your issue here, your problem is with searching, not indexing. You never tested searching, so for all we know it's better now. If zebra is failing to start, you'll have to figure out why. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
At 01:33 PM 1/22/2015 +1300, Robin Sheat wrote:
Paul A schreef op wo 21-01-2015 om 18:53 [-0500]:
So, then it bounced me around looking for indexer, SIP server and Zebra, which all appear to start, but service koha-common restart doesn't appear to want to play: [snip] You just want to make sure that zebra is correctly running. Ignore the indexer as that's not your issue here, your problem is with searching, not indexing.
You never tested searching, so for all we know it's better now. If zebra is failing to start, you'll have to figure out why.
It is starting/running. Just rebooted the box (end of the day for me, but I appreciate you're the other side of the timezones) and $ ps -faux gives 2 entries: k318-ko+ 1283 0.0 0.0 17176 404 ? S 19:47 0:00 daemon --name=k318-koha-zebra ---errlog=/var/log/koha/k318/zebra-error.log --stdout=/var/log/koha/k318/zebra.log --output=/var/log/koha/k318/zebra-output.log --verbose=1 --respawn --delay=30 --user=k318-koha.k318-koha -- zebrsrv -v none,fatal,warn -f /etc/koha/sites/k318/koha-conf.xml k318-ko+ 1285 0.0 0.0 114000 5532 ? S 19:47 0:00 \_ zebrasrv -v none,fatal,warn -f /etc/koha/sites/k318/koha-conf.xml I have no clue as to user k318-ko+ nor where --name=k318-koha-zebra came from. koha-conf.xml has (for both bibs and auths, created by the install process): <user>k318-koha</user> <password>2YTE********Gxbk</password> HOWEVER -- I have just (since reboot) found in zebra-output.log "Failed to bind to unix:/var/run/koha/zebradb/bibliosocket [No such file or directory]" and the same for authority socket. There is no file at all by that name on this box, but a quick look at our production box finds symbolic links at /run/koha/zebradb/ (but no file by that name.) Can you tell me please how these are spawned? Maybe if I chase this down, I can get back to my search speed testing ... Thanks again -- Paul
Paul A schreef op wo 21-01-2015 om 20:36 [-0500]:
k318-ko+ 1285 0.0 0.0 114000 5532 ? S 19:47 0:00 \_ zebrasrv -v none,fatal,warn -f /etc/koha/sites/k318/koha-conf.xml
OK, so it is running.
I have no clue as to user k318-ko+
That's just a truncation of the username.
nor where --name=k318-koha-zebra came from.
It's just a name, to prevent the same thing being started twice.
koha-conf.xml has (for both bibs and auths, created by the install process): <user>k318-koha</user> <password>2YTE********Gxbk</password>
HOWEVER -- I have just (since reboot) found in zebra-output.log "Failed to bind to unix:/var/run/koha/zebradb/bibliosocket [No such file or directory]" and the same for authority socket.
That's suspect. Have you messed with the configuration? It should be creating the sockets in /var/run/koha/<instancename>/bibliosocket, etc. This is defined in the <listen> sections near the top of koha-conf.xml.
There is no file at all by that name on this box, but a quick look at our production box finds symbolic links at /run/koha/zebradb/ (but no file by that name.)
/run is not necessarily equal to /var/run. On the server I just checked, /run doesn't exist at all. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
participants (2)
-
Paul A -
Robin Sheat