- Koha - lists.katipo.co.nz

SMS Failed - Where to see logs and troubleshoot.
by Aravindhan K 19 Dec '20

19 Dec '20

Hi All, We have a koha setup running with version 18.05. As of yesterday, we had sms service setup working fine , we used sms driver IN::epadhaiSMS. But now it says in notification it says notification sms failed. Where to look for logs or enable any debug logs. and /var/log/koha/library does not have much. Kindly help to resolve this issue. Thanks, Aravindhan K

1 0

Re: [Koha] Koha resource requirements
by dcook＠prosentient.com.au 18 Dec '20

18 Dec '20

Hi Barry, I think that it is reasonable to expect some minimum requirements to be listed, but it is easier said than done, since Koha is a large multi-component system. Personally, I tend to run many Koha instances on high powered servers with external database servers, so it's rare for me to be thinking about the requirements for just 1 Koha. Typically, I only run 1 Koha instance for development and testing, and I use the koha-testing-docker (https://gitlab.com/koha-community/koha-testing-docker) setup for that. Looking at that, I'm seeing probably around ~1.25GB of RAM used for an idle system, although that includes components like a Z3950 responder and SIP server that you won't need. Since it's a Dockerized environment, that's on top of whatever the OS and other installed software is needing. In my observations, I typically notice that a Starman "Plack" worker will take up about 200-500MB of RAM in its lifetime (mine right now are at 234 and 284 so I'd budget another 500MB). By default, you have 2 configured. If you wanted to shave off more memory, you could downgrade to just 1 Starman "Plack" worker. Looking at a server I do have with only 1 Koha instance... MySQL is using 357MB, Koha's Starman/Plack workers are 246MB and 190MB. The indexing daemon is 171MB. So that adds up to just under 1GB. Add in a bit more for Apache, Memcached, Zebra search engine, et cetera and you're probably up to 1-1.25GB. But that's just a snapshot around lunch time near Christmas holidays. Ultimately, your mileage may vary. If you add some swap space, which I know isn't included by default on AWS, you might have a smoother experience as well as that would help soak up some unexpected memory spikes. I don't have access to update the Downloads page to add some minimum requirements, but I think perhaps that someone should. Regarding CPU, I'd say minimum 4 CPU between all the various different Koha subcomponents for any serious usage, but you could get away with less. My koha-testing-docker uses 2 CPUs and it manages fine for me as a single user. David Cook Software Engineer Prosentient Systems Suite 7.03 6a Glen St Milsons Point NSW 2061 Australia Office: 02 9212 0899 Online: 02 8005 0595 -----Original Message----- Date: Wed, 16 Dec 2020 16:01:03 +0000 From: Barry Callahan <barryc(a)quicksilverdragon.com> To: koha(a)lists.katipo.co.nz <koha(a)lists.katipo.co.nz> Subject: [Koha] Koha resource requirements Message-ID: <010001766c48916c-b5c8c8db-d977-4dd9-adb1-83a6c5f2ae77-000000(a)email.amazonses.com> Content-Type: text/plain; charset=UTF-8 I recently started playing with Koha to see if it would help my wife and I manage our home library. Before I began, I reviewed the requirements listed on the download page ( https://koha-community.org/download-koha/ ) and the instructions for installing using the official .deb packages. One thing I thought was very conspicuously lacking was any mention of resource requirements. Naively, I assumed that meant that the requirements for running Koha would only be minimally greater than those required for a LAMPP stack serving a similar amount of traffic. Needless to say, an Amazon EC2 micro instance, which only has 1GB of RAM allocated to it is incapable of creating and enabling a single Koha library instance. Attempting to do so with no swap enabled immediately resulted in a crashed system. I resized the instance to small, with 2GB of RAM, and was able to boot the system and log in, but top showed a peak memory usage of ~1.9GB. On seeing that, I resized the server again to a medium instance with 4GB of RAM. After populating the database and adding a couple users and a few dozen items to it, the server is sitting at 1.5GB of RAM in use (not including cache) at idle. Admittedly, that includes the 500MB allocated to the local MySQL server, but still. I think I could probably be safe scaling back to a small instance if I moved the database to a remote server, which is my plan. I'd like to suggest updating the requirements section on the download page to include some information on the resources used by the koha-plack stack. At a minimum, some information about how much koha+plack would add to the memory footprint of an existing LAMP stack at idle would have saved me a fair bit of grief. Some information on how RAM usage and CPU load can be expected to scale with the number of active library instances and concurrent users would be nice, too, but less important than the base numbers, I think.

2 3

Re: [Koha] Koha 20.11 Plugins
by Tomas Cohen Arazi 17 Dec '20

17 Dec '20

Remember you need to flush memcached after tweaking the file, and better restart the plack process as well. If the file has this entries: <pluginsdir>/var/lib/koha/<instance>/plugins</pluginsdir>  <enable_plugins>1</enable_plugins> then restart all the related services: systemctl restart memcached koha-common Good luck -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

Koha 20.11 Plugins
by Nelson Mwirigi 17 Dec '20

17 Dec '20

I recently installed Koha 20.11 and am having a problem with finding or enabling plugins. There seems to be a big shift in this latest version. Most guides online refer to plugins in older Koha versions. Someone kindly assist with this. I am particularly interested in emailer plugins among others.

4 6

Koha resource requirements
by Barry Callahan 17 Dec '20

17 Dec '20

I recently started playing with Koha to see if it would help my wife and I manage our home library. Before I began, I reviewed the requirements listed on the download page ( https://koha-community.org/download-koha/ ) and the instructions for installing using the official .deb packages. One thing I thought was very conspicuously lacking was any mention of resource requirements. Naively, I assumed that meant that the requirements for running Koha would only be minimally greater than those required for a LAMPP stack serving a similar amount of traffic. Needless to say, an Amazon EC2 micro instance, which only has 1GB of RAM allocated to it is incapable of creating and enabling a single Koha library instance. Attempting to do so with no swap enabled immediately resulted in a crashed system. I resized the instance to small, with 2GB of RAM, and was able to boot the system and log in, but top showed a peak memory usage of ~1.9GB. On seeing that, I resized the server again to a medium instance with 4GB of RAM. After populating the database and adding a couple users and a few dozen items to it, the server is sitting at 1.5GB of RAM in use (not including cache) at idle. Admittedly, that includes the 500MB allocated to the local MySQL server, but still. I think I could probably be safe scaling back to a small instance if I moved the database to a remote server, which is my plan. I'd like to suggest updating the requirements section on the download page to include some information on the resources used by the koha-plack stack. At a minimum, some information about how much koha+plack would add to the memory footprint of an existing LAMP stack at idle would have saved me a fair bit of grief. Some information on how RAM usage and CPU load can be expected to scale with the number of active library instances and concurrent users would be nice, too, but less important than the base numbers, I think.

2 1

Koha make test
by ravikumar c 17 Dec '20

17 Dec '20

Hi Tried following steps mentioned at https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_git No matter what I do at the end when I open http://127.0.1.1:8080 after following all the steps, page says "The connection was reset" and Try again. Not sure what is wrong. Couldn't find any details as well in log file. Not sure how to proceed further. Appreciate any help Regards Ravi

2 1

Fields in item record entry form are too small in 20.11
by Elaine Bradtke 16 Dec '20

16 Dec '20

I'm just testing 20.11.00.000. Looking at the item record entry form, I find some of the fields are too small. Smaller than 20.05.05. Just to be sure it wasn't a fluke, I compared them using the same browser (chrome) on the same screen. I also compared it to how it looks on Firefox and it's still too small, smaller than the older version. Subfields a and b are so small that VWML only displays as V.. and j shelving control number is only an arrow. This could be an annoyance in a large branch system. Should I file a bug? Or is it only our system that's doing this? Elaine Bradtke VWML <https://www.vwml.org> Our income is severely diminished in these exceptionally uncertain times. Please help us to survive beyond this national crisis. Donate now <https://www.efdss.org/support-us>. English Folk Dance and Song Society <https://www.efdss.org> Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY Tel +44 (0) 20 7485 2206 (This number is for the English Folk Dance and Song Society in London, England. If you wish to phone me personally, send an e-mail first. I work off site) -------------------------------------------------------------------------- Registered Company No. 297142 Charity Registered in England and Wales No. 305999

2 1

Paid Support
by Anthony Snell 16 Dec '20

16 Dec '20

Respectfully request to be add as a Paid Vendor on the Koha website; thank you in advance for your consideration. Company Name: Trident Consulting Firm, LLC Contact Person: Anthony Snell Contact email: asnell(a)tridentcf.com Website: http://tridentcf.com Telephone: (803) 714-3125

2 1

Z39.50 server – some records timing out
by dudzikmichal＠wp.pl 16 Dec '20

16 Dec '20

Hi, I am writing with a request for help. It is about a causing a problem when searching for records by z39.50. (Koha version: 20.05.05.000). On the printscreen ( ibb.co ibb.co ) you will see responses for the following messages and one or two search results. It looks like it cannot retrieve some records. There are no errors in the intranet-error.log. The address of the server z39.50 from which I am searching for records is: hostname: eu.alma.exlibrisgroup.com:1921 database: 48OMNIS_NLOP I testing in yaz-client but when I show all records then yaz is stopped in Sent presentRequest. yaz-client -f conf_bn Connecting...OK. Sent initrequest. Connection accepted by v3 target. ID : 81 Name : Aleph Server/GFS/YAZ Version: ALEPH 20/1.1.1.1/2.1.32 Options: search present delSet triggerResourceCtrl scan sort extendedServices namedResultSets Elapsed: 0.110043 Sent searchRequest. Received SearchResponse. Search was a success. Number of hits: 4, setno 1 records returned: 0 Elapsed: 0.169132 Sent presentRequest (1+4). Koha is visible in the local network. The server is on 192.xx.xx.xx and I am connecting via VPN and it gets IP 10.xx.xx.xx. Is this a problem with network?? Let me know, thank you in advance. Regards Michal

1 0

Multiple Instances of Koha
by MAMCET Library 16 Dec '20

16 Dec '20

Dear all I installed koha 20.10 and ubuntu Mate 20.4 successfully. I created the Multiple Instances of Koha following error please help me. ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)

2 1