[Koha-devel] 3.18 zebra

[Michael Hafen]

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 <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
> Koha-devel at lists.koha-community.org
> http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20150121/29df1007/attachment.html>