[Koha-devel] 3.18 zebra

Wed Jan 21 22:21:54 CET 2015

Michael,

Thank you, I'm on the same track, but being a little bit cautious. Since 
the packages were introduced (and I have not yet used them in production) a 
number of warnings have been expressed (e.g. one of our esteemed developers 
wrote 20-Aug-2013: "Because the packages put koha-common in /etc/cron.d 
that does the indexing. The fact you have reindexed as root will have 
mucked up all sorts of permissions, including breaking this cron job.")

So what I have been trying to do is imitate the cron job (that is obviously 
not running as intended.)  Basically after env. vars it is: */5 * * * * 
root test -x /usr/sbin/koha-rebuild-zebra && koha-rebuild-zebra -q 
$(koha-list --enabled)

I was questioning the 'root' (which may in itself be fairly normal for cron 
jobs) which seems to go against previous advice.  The 'test -x' is taken 
care of (the file does exist), -q defaults to bibs and auths but with no 
verbosity, so 'koha-rebuild-zebra -v -f k318' seems like a reasonable 
command line.  It's just a question of 'who' does it, and with 'what 
permissions.'

The zebra logs seem to be working OK, but I do not have 'indexer-error.log' 
anywhere on the system.

Best -- Paul

At 01:27 PM 1/21/2015 -0700, you wrote:
>Ok, I've poked around a bit with the scripts now.
>
>Looks like the few command-line tools I looked at expect to be run as 
>root.Â  The zebra logging level is hard coded in koha-start-zebra as 
>'none,fatal,warn' which should be sufficient.Â  You probably already know 
>that the zebra error log is /var/log/koha/k318/zebra-error.logÂ  You may 
>have to edit that script to change the zebra logging level, looks like the 
>value for verbose logging is 'none,fatal,warn,all' or at least that's the 
>case for zebraidx.Â  I expect zebrasrv to be the same.Â  I was wondering 
>about file-system permissions, but as long as koha-start-zebra is run as 
>root it takes care of that.
>
>The 'Indexer not running' error refers to the 
><http://rebuild_zebra.pl>rebuild_zebra.pl script, which is started as a 
>daemon by the koha-indexer command-line tool.Â  So there may also be some 
>error in there somewhere.Â  It's log is /var/log/koha/k318/indexer-error.log
>
>Hope that info helps.
>
>On Wed, Jan 21, 2015 at 1:02 PM, Michael Hafen 
><<mailto:michael.hafen at washk12.org>michael.hafen at washk12.org> wrote:
>Looks like `koha-start-zebra k318` is one of the command-line tools 
>provided by the koha-common package.Â  I'm guessing the recommended way to 
>use this too is to run it as root, and it will then sudo to the k318-koha 
>user to perform the task inside the tool.
>Seems there is an error in zebra though.Â  There should be a way to start 
>zebra with more logging, but I'm not that familiar with the command-line 
>tools.Â  Hopefully someone else knows more...
>
>On Wed, Jan 21, 2015 at 11:42 AM, Paul A 
><<mailto:paul.a at navalmarinearchive.com>paul.a at navalmarinearchive.com> wrote:
>Please bear with me -- I had no luck sorting out my search speed problem, 
>so did a packet apt-get remove, install (not purge.) All went extremely 
>well, OPAC reported "under maintenance", staff admin (logging in with 
>install name) upgraded the 3.05 database (new as requested by 
>/usr/share/koha/k318-db-request.txt), and both sites are delivering proper 
>pages through Apache (prefork+itk.)
>
>But I have a problem with Zebra. Does 'instancename-koha' really have to 
>be a sudoer? If there's a possible quick fix I'll try it, if not I'll 
>start over.
>
>Â  Â  Â  Â  k318-koha at hood:/usr/sbin$ koha-start-zebra k318
>Â  Â  Â  Â  Invalid option: --user (only works for root)
>Â  Â  Â  Â  /.../
>Â  Â  Â  Â  Starting Zebra server for k318
>Â  Â  Â  Â  Invalid option: --user (only works for root)
>Â  Â  Â  Â  /.../
>Â  Â  Â  Â  Something went wrong starting Zebra for k318.
>
>k318-koha is a valid user (non sudoer) with pw generated by Koha. I can 
>start Zebra as root, no problem, but then:
>
>Â  Â  Â  Â  k318-koha at hood:/usr/sbin$ koha-rebuild-zebra -v -f k318 [N.B. 
>not 'sudo']
>Â  Â  Â  Â  k318-koha is not in the sudoers file.Â  This incident will be 
>reported.
>Â  Â  Â  Â  Something went wrong rebuilding biblio indexes for k318
>
>and I have *not* tried reindexing as root -- ISTR dire warnings not to do 
>so on this list :)
>
>I've looked at Bug 13396 and koha-conf.xml complies.
>
>I've tried 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
>
>zebra-error log reports:
>20150121 12:49:39 k318-koha-zebra: client (pid 2132) exited with 1 status
>20150121 12:49:39 k318-koha-zebra: client (pid 2133) exited with 1 status
>20150121 12:49:39 k318-koha-zebra: client (pid 2134) exited with 1 status
>20150121 12:49:39 k318-koha-zebra: client (pid 2135) exited with 1 status
>20150121 12:49:39 k318-koha-zebra: client (pid 2136) exited with 1 status
>20150121 12:49:39 k318-koha-zebra: terminating too quickly, waiting 30 seconds
>
>but I'm not sure where '-zebra' gets concatenated to the user.
>
>Many thanks -- Paul
>
>_______________________________________________
>Koha-devel mailing list
><mailto:Koha-devel at lists.koha-community.org>Koha-devel at lists.koha-community.org
>http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
>website : <http://www.koha-community.org/>http://www.koha-community.org/
>git : <http://git.koha-community.org/>http://git.koha-community.org/
>bugs : <http://bugs.koha-community.org/>http://bugs.koha-community.org/
>
>

---
Maritime heritage and history, preservation and conservation,
research and education through the written word and the arts.
<http://NavalMarineArchive.com> and <http://UltraMarine.ca>