Re: [Koha] Koha 17.05 and memcached
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_NAMESPACE "koha-intra" ... I receive a warning on the about koha page (Config read from ENV and koha-conf.xml), but the Status is green and running. Thank you for your help! -- View this message in context: http://koha.1045719.n5.nabble.com/Koha-17-05-and-memcached-tp5939903p5940951... Sent from the Koha-general mailing list archive at Nabble.com.
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/ ORCID ID: http://orcid.org/0000-0003-4666-7874 *"Spiritual relationship is far more precious than physical. Physical relationship divorced from spiritual is body without soul" -- Mahatma Gandhi* On Tue, Jul 25, 2017 at 8:45 PM, Adrian <aschmi@gmail.com> wrote:
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_NAMESPACE "koha-intra" ...
I receive a warning on the about koha page (Config read from ENV and koha-conf.xml), but the Status is green and running.
Thank you for your help!
-- View this message in context: http://koha.1045719.n5.nabble. com/Koha-17-05-and-memcached-tp5939903p5940951.html Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
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 <memcached_servers> 127.0.0.1:11211 </memcached_servers> Is it any faster? Not sure yet I'll need to get a word from our librarian... -- View this message in context: http://koha.1045719.n5.nabble.com/Koha-17-05-and-memcached-tp5939903p5940967... Sent from the Koha-general mailing list archive at Nabble.com.
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 (memcached_servers and memcached_namespace), and nothing else. Plack will bring much more performance than Memcached ( https://wiki.koha-community.org/wiki/Benchmark_for_16.11). Regards, Jonathan On Tue, 25 Jul 2017 at 12:15 Adrian <aschmi@gmail.com> wrote:
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_NAMESPACE "koha-intra" ...
I receive a warning on the about koha page (Config read from ENV and koha-conf.xml), but the Status is green and running.
Thank you for your help!
-- View this message in context: http://koha.1045719.n5.nabble.com/Koha-17-05-and-memcached-tp5939903p5940951... Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
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.11 -- Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
This morning we tried updating from 17.05.10 to 17.05.11. All seemed to go well, but afterwards not results were returned from a search in either the public or staff interfaces. Assuming Zebra had failed to start, I ran "koha-start-zebra instance-name", but received the error "Invalid --pidfiles argument: '/var/run/koha/instance-name/' (Directory does not exist)". Checked /var/run and...the koha directory in fact no longer existed. Reverting back to the old snapshot of this server shows that directory in place. Is this expected behavior? Resolution? 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-bounces@lists.katipo.co.nz] On Behalf Of guille Sent: Monday, April 30, 2018 6:14 AM To: koha@lists.katipo.co.nz Subject: Re: [Koha] Koha 17.05 and memcached 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.11
Did you reboot the server in between? The OS sometimes decides to clean up /var/run You can run koha-create-dirs instancename and it will sort it out Chris On 9 May 2018 3:22:43 AM NZST, "Bortel, Gary" <gary.bortel@sos.wa.gov> wrote:
This morning we tried updating from 17.05.10 to 17.05.11. All seemed to go well, but afterwards not results were returned from a search in either the public or staff interfaces. Assuming Zebra had failed to start, I ran "koha-start-zebra instance-name", but received the error "Invalid --pidfiles argument: '/var/run/koha/instance-name/' (Directory does not exist)". Checked /var/run and...the koha directory in fact no longer existed. Reverting back to the old snapshot of this server shows that directory in place.
Is this expected behavior? Resolution?
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-bounces@lists.katipo.co.nz] On Behalf Of guille Sent: Monday, April 30, 2018 6:14 AM To: koha@lists.katipo.co.nz Subject: Re: [Koha] Koha 17.05 and memcached
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.11
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Hmmm… Went back and updated to 17.05.11 again, restarted koha-common/memcached and everything seemed to be working fine. I came back and hour later and was unable to search holdings. Went back to /var/run/ and…the koha directory had disappeared again. Ran sudo koha-create-dirs and got those directories back. Tried to run sudo koha-zebra –start instance-name…and received the error “sudo: koha-zebra: command not found”. (sudo koha-rebuild-zebra -f -v instancename does seem to work!) Restarted Unbuntu…just because…and the /var/run/koha directory is missing once again! Other suggestions? From: Chris Cormack [mailto:chrisc@catalyst.net.nz] Sent: Wednesday, May 09, 2018 11:07 AM To: koha@lists.katipo.co.nz; Bortel, Gary <gary.bortel@sos.wa.gov>; 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 You can run koha-create-dirs instancename and it will sort it out Chris On 9 May 2018 3:22:43 AM NZST, "Bortel, Gary" <gary.bortel@sos.wa.gov<mailto:gary.bortel@sos.wa.gov>> wrote: This morning we tried updating from 17.05.10 to 17.05.11. All seemed to go well, but afterwards not results were returned from a search in either the public or staff interfaces. Assuming Zebra had failed to start, I ran "koha-start-zebra instance-name", but received the error "Invalid --pidfiles argument: '/var/run/koha/instance-name/' (Directory does not exist)". Checked /var/run and...the koha directory in fact no longer existed. Reverting back to the old snapshot of this server shows that directory in place. Is this expected behavior? Resolution? 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-bounces@lists.katipo.co.nz] On Behalf Of guille Sent: Monday, April 30, 2018 6:14 AM To: koha@lists.katipo.co.nz<mailto:koha@lists.katipo.co.nz> Subject: Re: [Koha] Koha 17.05 and memcached 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.11 ________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz<mailto:Koha@lists.katipo.co.nz> https://lists.katipo.co.nz/mailman/listinfo/koha -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
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 named Koha instances. * koha-restart-zebra: Restart Zebra for named Koha instances. * koha-rebuild-zebra: Rebuild the Zebra database for a Koha instance. * koha-stop-zebra: Stop Zebra for named Koha instances. Hope this helps. Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch
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 <mik@adminkuhn.ch> wrote:
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 named Koha instances. * koha-restart-zebra: Restart Zebra for named Koha instances. * koha-rebuild-zebra: Rebuild the Zebra database for a Koha instance. * koha-stop-zebra: Stop Zebra for named Koha instances.
Hope this helps.
Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Sent from my Android device with K-9 Mail. Please excuse my brevity.
That shows I shouldn't fully trust the wiki! https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_package... I'll take a third run at this next week when I'm back in the office. Thanks for all the help! gcb -----Original Message----- From: Koha [mailto:koha-bounces@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 restart that's deleting the dirs, not the upgrade. Chris On 11 May 2018 6:07:34 AM NZST, Michael Kuhn <mik@adminkuhn.ch> wrote:
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 named Koha instances. * koha-restart-zebra: Restart Zebra for named Koha instances. * koha-rebuild-zebra: Rebuild the Zebra database for a Koha instance. * koha-stop-zebra: Stop Zebra for named Koha instances.
Hope this helps.
Best wishes: Michael --
Hi Gary You wrote:
That shows I shouldn't fully trust the wiki!
https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_package... You're right - it seems the current Zebra-related commands (koha-start-zebra, koha-stop-zebra and koha-restart-zebra) have been marked as "DEPRECATED" in the Koha wiki just on May 9. Of course this is confusing when all existing versions are still using these commands. Reason seems to be that in the yet unreleased Koha 18.05 these old commands will be replaced by the new "koha-zebra" which will accept options. See: * https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17468 Instead of trusting the wiki best is probably still to use "man koha-common" because... "man is your friend". Best wishes: Michael -- Geschäftsführer · Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH · Pappelstrasse 20 · 4123 Allschwil · Schweiz T 0041 (0)61 261 55 61 · E mik@adminkuhn.ch · W www.adminkuhn.ch
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 restart, Koha was still working with the /var/run/koha directories present as expected. 3. Updated Koha (--> 17.05.11), restarted Koha and everything was still okay. 4. Restarted the server and the /var/run/koha directories had gone missing with Zebra no longer able to start. 5. If I run "sudo koha-create-dirs instance-name1" and "koha-start-zebra instance-name1"...I am able to search the catalog with results returned. 6. Restarting the OS takes down Koha yet again. My understanding is that in Ubuntu, the directories/files in /var/run are considered volatile and need to be recreated by individual services on each restart of the OS. That seems to be taking place with 17.05.10. With no change to the OS, this no longer seems to be occurring in 17.05.11. Digging through code, it looks as though this should occur when koha-zebra-ctl.sh is called. At the very least, it appears those directories should be created if "sudo /etc/init.d/koha-common start" is run...they're not. Running "sudo service --status-all" shows the koha-common service as not running, though memcached does seem to be. If I run koha-create-dirs and koha-start-zebra for all instances, then run "sudo service koha-common start"...Koha still shows as not running. Other ideas? For now, I'll leave this server running on 17.05.10 and try updating to 17.11 when 18.05 is released later this month... gcb
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
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 & 27. # Exit if the package is not installed [ -x /usr/sbin/koha-zebra ] || exit 0 WAIT!!! Wasn't I just told there is no command "koha-zebra" till 18.05??? 1. Change the command to "koha-start-zebra" 2. Restart the OS 4. koha-common is now running (sudo service --status-all) 5. And the koha directories and sub-directories under /var/run have been created as expected I'll try this with my production machine tomorrow and, hopefully, get it updated before 18.05 is released... gcb
Other ideas?
For now, I'll leave this server running on 17.05.10 and try updating to 17.11 when 18.05 is released later this month...
gcb
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
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
"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 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 & 27. # Exit if the package is not installed [ -x /usr/sbin/koha-zebra ] || exit 0 WAIT!!! Wasn't I just told there is no command "koha-zebra" till 18.05??? 1. Change the command to "koha-start-zebra" 2. Restart the OS 4. koha-common is now running (sudo service --status-all) 5. And the koha directories and sub-directories under /var/run have been created as expected I'll try this with my production machine tomorrow and, hopefully, get it updated before 18.05 is released... gcb
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 <gary.bortel@sos.wa.gov> 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. 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 & 27.
# Exit if the package is not installed [ -x /usr/sbin/koha-zebra ] || exit 0
WAIT!!! Wasn't I just told there is no command "koha-zebra" till 18.05???
1. Change the command to "koha-start-zebra" 2. Restart the OS 4. koha-common is now running (sudo service --status-all) 5. And the koha directories and sub-directories under /var/run have been created as expected
I'll try this with my production machine tomorrow and, hopefully, get it updated before 18.05 is released...
gcb
Other ideas?
For now, I'll leave this server running on 17.05.10 and try updating to 17.11 when 18.05 is released later this month...
gcb
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
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
participants (7)
-
Adrian -
Bortel, Gary -
Chris Cormack -
guille -
Jonathan Druart -
Michael Kuhn -
vinod mishra