Re: [Koha] Out of memory when Koha starts due to opac-search.pl and 500.pl

ss to make a Koha query. I didn't realise that would hit that script alias then. I'm using fail2ban but up till now just for SSH. So tonight I have been looking at a regex for Apache to match some of the errors in the Koha logs. I'll get back with how I go. Regexes :-( Thank

Re: [Koha] Out of memory when Koha starts due to opac-search.pl and 500.pl

them in your firewall. There are some that ignore the robots.txt and they can bring down a Koha server. I you look at the Apache access logs you might see that all those requests come from the same IP address. Hope this helps, Katrin On 10.07.24 13:02, Mike Lake wrote: Hi all I'm having

[Koha] Out of memory when Koha starts due to opac-search.pl and 500.pl

Hi all I'm having serious problems with my Koha instance. It serves the OPAC for the Australian Speleological Federation. We are currently on Koha 23.11 on a Debian 10.13. The system has been running fine for ages. I was getting errors from the OOM killer: oom_reaper: reaped process 1554 (o

Re: [Koha] Adding an encryption_key to koha-conf.xml

Hi On 2022-06-30 9:21 pm, David Tan wrote: Hi Mike, I had the same issue. I notice in the koha-conf.xml is missing this line __ENCRYPTION_KEY__ After adding this line, it work fine for me. David Just did the same. I added a key to my sites/opac/koha-conf.xml and now there is no more warning

Re: [Koha] Adding an encryption_key to koha-conf.xml

pt for that (open the xml, generate a key, add the missing entry, write the xml) then use koha-foreach to run it for each koha site. Regards, Jonathan Le sam. 25 juin 2022 à 12:21, Mike Lake a écrit : Hi All Just upgraded tonight from Koha 21.11.05.000 to 22.05.00-1 That all went fine. The

Re: [Koha] Adding an encryption_key to koha-conf.xml

Suggestions? On 2022-06-25 8:21 pm, Mike Lake wrote: Hi All Just upgraded tonight from Koha 21.11.05.000 to 22.05.00-1 That all went fine. The About Koha page now says: "Warning: You are missing the entry in your koha-conf.xml file. Please generate a key." I can see a place for t

[Koha] Adding an encryption_key to koha-conf.xml

Hi All Just upgraded tonight from Koha 21.11.05.000 to 22.05.00-1 That all went fine. The About Koha page now says: "Warning: You are missing the entry in your koha-conf.xml file. Please generate a key." I can see a place for this is the koha-conf-site.xml.in file (and a suggestion to use p

Re: [Koha] How to copy patron permissions?

Hi Michael Kuhn notes: As I have written in an earlier post of this thread the current library is trying to avoid non-Koha-standard methods like (ever-changing) external Javascript or plugins. From the perspective of a sys admin that needs to maintain and upgrade a Koha instance, the minimisa

Re: [Koha] How to measure and improve Koha performance for our instance?

Hi all On 2022-01-17 5:16 pm, dc...@prosentient.com.au wrote: If you enable Plack/Starman, page loads and search times will be faster, because So I decided to try out Plack as in my first reply: First step tonight will be to read up on configuring and turning on plack for the test in

Re: [Koha] How to measure and improve Koha performance for our instance?

ge. First step tonight will be to read up on configuring and turning on plack for the test instance. Then I'll toss up doubling cpu/ram before further tests. I hope that helps. Feel free to send more questions. Thanks. Much appreciated. -Original Message- Date: Fri, 14

[Koha] How to measure and improve Koha performance for our instance?

Hi all We have a production library setup at https://opac.caves.org.au and its now ready for users to use. We also have a test instance that can be used for testing. I'm wanting to know the options for measuring and improving the performance - just basic load and search time that users percei

Re: [Koha] Error DBI Exception, maximum row size is 8126 during upgrade to Koha 21.11.01

Hi all Fridolin said: The version is indeed stored in database to compare with sources. On 2021-12-30 10:23 pm, Mike Lake wrote: Excellent. Where is this stored? I had a quick glance through the schema dump but did not see it. In mine I should see 21.11.01.000 stored or something like that

Re: [Koha] Error DBI Exception, maximum row size is 8126 during upgrade to Koha 21.11.01

some issues. The version is indeed stored in database to compare with sources. Looks like "library" version is 21.06.00.006, so previous database upgrade failed also ? This problem may be described in : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29728 Best regards, Le 2

[Koha] Error DBI Exception, maximum row size is 8126 during upgrade to Koha 21.11.01

Hi all Just upgraded tonight koha-common 21.11.01-1 to 21.11.00-1 This is on a Debian 10.11 (deb http://debian.koha-community.org/koha stable main). I got this error: ERROR - {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Row size too large. The maximum row size for the used table type,

Re: [Koha] [Koha-devel] Web install issue with 21.05.05.000

On 2021-10-31 12:06 pm, Mason James wrote: hi folks i've pushed a new package, that should fix this issue I got bitten by this bug also. On Sat arvo and during a boring meeting saw a small fractional Koha upgrade was available via apt and went ahead with the upgrade. I usually check our site

Re: [Koha] Koha common upgrades fails as rabbitmq service is not running

     localhost 61613    guest    guest      check the /etc/koha/koha-conf-site.xml.in template file, as an example then reboot On 1/07/21 11:34 pm, Mike Lake wrote: Hi Anyone had this problem? There is already a new Koha common 21.05.01-1 which will probably have the same problem if I try and u

Re: [Koha] Koha common upgrades fails as rabbitmq service is not running

Hi Anyone had this problem? There is already a new Koha common 21.05.01-1 which will probably have the same problem if I try and upgrade. Mike On 2021-06-26 22:24, Mike Lake wrote: Hi I have a problem with our library and RabbitMQ. Koha version: 21.05.00.000 on Debian 9.13 During the

[Koha] Koha common upgrades fails as rabbitmq service is not running

Hi I have a problem with our library and RabbitMQ. Koha version: 21.05.00.000 on Debian 9.13 During the latest update just tonight Setting up koha-common (21.05.00-1) ... Upgrading database schema for library <== this instance is disabled Upgrading database schema for libtest2

Re: [Koha] Very high CPU usage

.koha-community.org/bugzilla3/show_bug.cgi?id=4042#c3 I'll look at firewall solutions tomorrow and see if for a while we can set login required on OPAC searches. I'll get back if this fixes the problem. Thanks --- Mike Lake On 2021-04-21 23:23, Coehoorn, Joel wrote: Check the apache logs a

[Koha] Very high CPU usage

its averaging 800 MB used out of 2GB but swap is fully used. This system had previously been adequate so something seems to have changed. What advice for narrowing down the problem? It's not a large installation. Any links to hardware/cpu/mem/swap re

Re: [Koha] lockdir variable in koha config file

or running. Maybe best for that to be in a separate post later on :-) Thanks. --- Mike Lake On 2021-04-21 20:54, Joonas Kylmälä wrote: Hi, if you restarted plack, then I wonder if it could be in memcached, try restarting it and tell us how it goes. After restarting memached I think you need

Re: [Koha] lockdir variable in koha config file

t or what to do for the system to pickup this change? The Home/About Koha/System Information still says I am missing this setting. Thanks Mike Lake On 2021-03-21 00:45, Mark Tompsett wrote: On 2021-03-19 3:31 p.m., Tom Hanstra wrote: I am still seeing some issues with the variable "

Re: [Koha] Error in SQL during upgrade to 20.05.04

Hi Versions I'm using are: Debian_Stretch version 9.13 with sources being "deb http://debian.koha-community.org/koha stable main" Mariadb Ver 15.1 Distrib 10.1.45-MariaDB, for debian-linux-gnu --- Mike Lake On 2020-09-23 20:42, Mike Lake wrote: Hi Tonight I upgraded o

[Koha] Error in SQL during upgrade to 20.05.04

Bug 25958 - Allow LongOverdue cron to exclude specified lost values Upgrade to 20.05.04.000 done [19:42:16]: 20.05.04 release Processing triggers for man-db (2.7.6.1-2) ... Reading package lists... Building dependency tree... Reading state information... Reading extended state informatio