Caused by bug 20234, I have just let a comment to inform the 17.05 release
maintainer.
On Mon, 14 May 2018 at 18:02 Bortel, Gary wrote:
> Sigh...
>
> And so to bring this thing almost full circle, I started digging, trying
> to understand why the koha-common service wasn't starting as expected.
"Koha-zebra --start" --> "koha-start-zebra" in line 60
"koha-zebra --stop" --> "koha-stop-zebra" in line75
"koha-zebra --restart" --> "koha-restart-zebra" in line 88
gcb
Sigh...
And so to bring this thing almost full circle, I started digging, trying to
understand why the koha-common service wa
Sigh...
And so to bring this thing almost full circle, I started digging, trying to
understand why the koha-common service wasn't starting as expected. Going back
to the /etc/init.d/koha-common script and comparing 17.05.10 to 17.05.11...at
least part of the problem was staring back at lines 26
So I had a chance to go back and hit this problem again this morning...
1. I ran the latest security updates on the OS itself (Unbuntu 16.04). Checked
on Koha (17.05.10) and everything was running fine...returning search results
as expected.
2. Restarted the server several times and after each
Hi Gary
You wrote:
> That shows I shouldn't fully trust the wiki!
>
>
https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_packages#Zebra-related
You're right - it seems the current Zebra-related commands
(koha-start-zebra, koha-stop-zebra and koha-restart-zebra) have been
m
ailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Chris Cormack
Sent: Thursday, May 10, 2018 12:43 PM
To: koha@lists.katipo.co.nz
Subject: Re: [Koha] Koha 17.05 and memcached
Yep that's write, create the dirs again and start zebra with the command from
Michael.
It's the Ubuntu re
Yep that's write, create the dirs again and start zebra with the command from
Michael.
It's the Ubuntu restart that's deleting the dirs, not the upgrade.
Chris
On 11 May 2018 6:07:34 AM NZST, Michael Kuhn wrote:
>Hi
>
>You wrote:
>
> > ...
> > Tried to run sudo koha-zebra –start instance-nam
Hi
You wrote:
> ...
> Tried to run sudo koha-zebra –start instance-name…and received the
> error “sudo: koha-zebra: command not found”.
There is no such script named "koha-zebra". According to the
"koha-common" manpage available Zebra-related scripts are:
* koha-start-zebra: Start Zebra for
suggestions?
From: Chris Cormack [mailto:chr...@catalyst.net.nz]
Sent: Wednesday, May 09, 2018 11:07 AM
To: koha@lists.katipo.co.nz; Bortel, Gary ;
koha@lists.katipo.co.nz
Subject: Re: [Koha] Koha 17.05 and memcached
Did you reboot the server in between?
The OS sometimes decides to clean up /var/run
17.05.10 --> 17.05.11
>Ubuntu 16.04
>Running memcached, but not yet upgraded to Plack
>
>Thanks
>gcb
>
>
>
>-Original Message-
>From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of guille
>Sent: Monday, April 30, 2018 6:14 AM
>To: koh
Multi-tenant installation
Koha 17.05.10 --> 17.05.11
Ubuntu 16.04
Running memcached, but not yet upgraded to Plack
Thanks
gcb
-Original Message-
From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of guille
Sent: Monday, April 30, 2018 6:14 AM
To: koha@lists.katipo.co.nz
S
sorry for my english is google translator
yes, jonathan, i am testing plack in my installation, and it works fine, but
when I restart the server it disables the intranet and opac page, and
deletes at least that i know the file / var / run / koha. what am I doing
wrong. my version of koha is 17.05.
Wait guys, you are certainly doing something wrong here.
With Koha 17.05 you should use Plack, and if you are using Plack the
MEMCACHED* variables you will define in your apache config files will not
be used.
You should setup plack correctly, fill the 2 entries in your koha-conf.xml
files (memcach
So this is the relevant part of my apache config
SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml"
SetEnv MEMCACHED_SERVERS "127.0.0.1:11211"
SetEnv MEMCACHED_NAMESPACE "koha-intra"
And here is what I have on the /etc/koha/sites/library/koha-conf.xml
127.0.0.1:11211
Is it an
Hello
Can you please share entire process to make it workable and how effectively
it made your Koha fast?
With Regards,
Vinod Kumar Mishra,
Assistant Librarian,
Biju Patnaik Central Library (BPCL),
NIT Rourkela,
Sundergadh-769008,
Odisha,
India.
Mob:91+9439420860
Website: http://mishravk.com/
O
Thank you very much Guille!
Finally I made it work, but is a weird configuration... the only way to make
it work at least on 17.05, was to have part of the config in the xml file,
and the rest on the apache-configured file:
...
SetEnv MEMCACHED_SERVERS "127.0.0.1:11211"
SetEnv MEMCACHED_NAMESP
ok My english is not very well
If you have configured the file koha-conf.xml, only put in
/etc/apache2/site-enable/koha.conf the following:
SetEnv MEMCACHED_SERVERS "127.0.0.1:11211"
SetEnv MEMCACHED_NAMESPACE "koha_koha"
in both intranet and opac
and run sudo service apache2 restart
--
17 matches
Mail list logo
