- Koha - lists.katipo.co.nz

Koha capacity planning advice?
by Chris Brown 03 Aug '17

03 Aug '17

Gentle Reader, We are considering using Koha amongst a group of volunteer-run libraries here in Sheffield (UK). We'd probably host it on a machine "in the cloud" and I am looking for advice on how much capacity we need to plan for (CPU power, RAM, disk space etc). As a very rough guide, we might need to support up to six libraries each with around 4,000 books and 1,000 users. It is hard to estimate transaction rates but I wouldn't anticipate we would ever exceed 20 checkout/checkin operations per minute (aggregated over all the libraries) and the average would be much less. Any advice would be appreciated. In particular if anyone is hosting Koha using Amazon Web Services, which machine type are you using? Thanks and Best Regards, Chris Brown (Volunteer at Greenhill Library, Sheffield)

2 1

Re: [Koha] [Important] Update your MySQL|MariaDB configuration to avoid data loss
by Jonathan Druart 03 Aug '17

03 Aug '17

Vinod, Yes you should create the file to make sure the situation will not appear again for other rows. For the corrupted records (the ones returned by the SQL queries), please follow bug 19016. Regards, Jonathan On Thu, 3 Aug 2017 at 05:00 vinod mishra <mishravk79(a)gmail.com> wrote: > Dear All, > > I am using Koha 16.11.07 and because of below problems i faced lot of > transaction related issues, since it was start of the koha so i simply > deleted all circulation history (Very less which came along with test > database during setup) and now things work fine. I did not upgraded koha > too and using RFID which is configured via Koha SIP. Everything is working > fine now but as per the instruction i run commands and found some output > while excecuted below three so please suggest. Please suggest should i > create the file as suggested in the chain of email? or leave it as it is. > > > SELECT r.reserve_id FROM reserves r JOIN old_reserves o ON r.reserve_id=o.reserve_id; > > SELECT b.biblionumber FROM biblio b JOIN deletedbiblio db ON b.biblionumber=db.biblionumber; > > SELECT i.itemnumber FROM items i JOIN deleteditems di ON i.itemnumber=di.itemnumber; > > > > 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 Wed, Aug 2, 2017 at 3:15 PM, Jon Knight <J.P.Knight(a)lboro.ac.uk> wrote: > >> On Tue, 1 Aug 2017, Bortel, Gary wrote: >> >>> For a multi-tenant installation with multiple MySQL databases... >>> >>> "The Solution" ( >>> https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix) >>> recommends adding "init-file=/var/lib/mysql/init-file_kohadev.sql" in the >>> my.cnf MySQL configuration file, then creating the appropriately configured >>> "init-file_kohadev.sql" file. Where there are multiple Koha databases, >>> should one add multiple "init-file=..." statements to my.cnf as well as >>> multiple init-file_kohadev.sql files? Or will MySQL only accept one >>> init-file directive in which case the .sql file would include multiple >>> blocks of code...one for each database? >>> >> >> I'd say that its up to you really - both will work. If you use just one >> "init-file_kohadev.sql" file you'll just have to repeat all the SQL, just >> changing the database in the "use" line. If you've got lots of Koha >> instances that file is going to be quite long. >> >> Personally for tidiness and ease of maintenance I'd probably opt for one >> init file per Koha database, as those would be clearer and could then be >> maintained more easily using normal Linux command line tools and a few Perl >> scripts. I assume people hosting lots of tenants are probably using tools >> like Ansible to set up provisioning of a new Koha instance so these files >> would be created from a template and just one line added/removed from the >> my.conf file. >> >> Jon >> >> _______________________________________________ >> Koha mailing list http://koha-community.org >> Koha(a)lists.katipo.co.nz >> https://lists.katipo.co.nz/mailman/listinfo/koha >> > >

1 0

Koha Acquisition Module - problems when modifying the price, conversion rate and currency while receving the order
by Paul Pandian 03 Aug '17

03 Aug '17

Hi, We at The Institute of Mathematical Sciences, Chennai, India have been successfully been using all the modules of Koha including serials module. We have recently upgraded to the version 16.11.05 from 3.22 without any issues. We request Koha developers to kindly look at the following issues with regard to Acquisition module: 1. Koha->Acquisitions->Vendor->Receive shipment 2. Invoice details are filled in -> Next 3. Under receipt summary, select the basket and receive the item If no changes are required like price, currency and conversion rates etc, then no problem and finish the receiving. But, when we need to change the price or currency or conversion rates, then option available to effect the change is only through editing the orderline number (by clicking the orderline number) in the receipt summary page. In Koha 3.22: While editing the order line number, the URL passes two parameters viz.1. ordernumber and 2.booksellerid as shown below: http://library.imsc.res.in:8001/cgi-bin/koha/acqui/neworderempty.pl?ordernu… As you may notice, the parameters passed in the URL hold good for books acquisition. But for the serials, subscriptionid is another important parameter to be passed in the URL to identify the particular serial subscription. This is not provided in Version 3.22. We manually pass this subscriptionid parameter in the URL as below to acheive the functionality: http://10.96.68.205:8001/cgi-bin/koha/acqui/neworderempty.pl?ordernumber=4&… In Koha 16.11.05 In 16.11.05, the subscriptionid as a parameter is also being passed alongwith ordernumber, booksellerid in the URL while editing the orderline for change of price, currency and conversion rate when receiving the item as follows: For Serials: http://10.96.68.172:8001/cgi-bin/koha/acqui/neworderempty.pl?ordernumber=79… This works without any problem (It is being fixed in the 16.11.05 which was a bug in 3.22) For Books: http://10.96.68.172:8001/cgi-bin/koha/acqui/neworderempty.pl?ordernumber=79… As you may notice in the above URL, there is no subscriptionid value as it is a book, hence the following error occured: Software error: Cannot insert order: Mandatory parameter basketno is missing at /usr/share/koha/intranet/cgi-bin/acqui/addorder.pl line 289. We have to manually remove the parameter &subscriptionid=, then only are we able to process the invoice and receive the book. THIS IS A BUG. Many of you who use acquistion for both books and Serials must have come across the above problems and request the Koha Developers community to kindly spare some to fix these problems at the earliest. Looking forward to your help! Thanks and Regards, Paul Pandian and Maruthu Pandiyan Institute of Mathematical Sciences CIT Campus, Taramani Chennai 600113, India

2 3

Is this an error about Koha?
by Luis Moises Rojas 02 Aug '17

02 Aug '17

Hello everybody, Our server only have Koha, this critical error: The "HTTP: Apache Struts 2 Remote Code Execution (CVE-2017-5638)" . I said this, because struts (as you know) is for MVC programing structure. Thanks. -- *Luis Moisés Rojas P.*

2 1

Impossible to renew items
by mpw 02 Aug '17

02 Aug '17

I'm running Koha version 17.05.01 on Debian 8.8. I'm setting up a new library. I have checked out eight books. In the renewable column they are all listed as "Not renewable (0 of 0 renewals remaining)". Several people have suggested removing all the circulation and fine rules and creating a single rule the holds for all patron types and all item types. For example here: http://koha.1045719.n5.nabble.com/All-items-quot-not-renewable-quot-td59254… I've tried that several times but none of the tries ever made any difference. Right now I only have one rule: Patron category - All Item type - All Current checkouts allowed - 20 Renewals allowed - 3 Renewal period - 14 Automatic renewal - no Since somebody in the above mentioned thread said that this might be a bug, I opened a bug report but they referred me back to this list because it's supposedly just a configuration problem. I have set the option that enables the "Override renewal limit" checkbox so I can trick the system into renewing books, but that's just a workaround and I'd like to get to the root of the problem. I've been going around in circles here for well over a week. Can anybody point me in the right direction? -- View this message in context: http://koha.1045719.n5.nabble.com/Impossible-to-renew-items-tp5941578.html Sent from the Koha-general mailing list archive at Nabble.com.

3 5

Searching capability dies every few days - Zebra problem?
by mpw 02 Aug '17

02 Aug '17

I'm running Koha version 17.05.01 on Debian 8.8. I set up Koha a few months ago and we're still learning the system. One thing we've noticed that presumably is not normal is that every few days the searching capability dies for some reason or other. My guess is that it has something to do with Zebra. I occasionally get a message from my logrotate cronjob: Zebra already stopped for instance xxx. When I check, there are no koha or zebra processes running. I can restore the search capability by restarting Koha with "invoke-rc.d koha-common restart". Presumably some daemon or other dies but I haven't been able to figure out which one. Maybe it happens during the regular cronjobs? Does anybody have any idea how I can figure out what's happening? One workaround I'm considering is setting up a regular cronjob to restart koha-common regularly, but that doesn't strike me as being a very elegant solution. -- View this message in context: http://koha.1045719.n5.nabble.com/Searching-capability-dies-every-few-days-… Sent from the Koha-general mailing list archive at Nabble.com.

3 3

Results of the poll "Ready to help the Koha community?"
by Jonathan Druart 02 Aug '17

02 Aug '17

Hello everybody, I have published the results of the poll, launched at the beginning of the 17.11 development release cycle. https://koha-community.org/answers-of-the-poll-ready-to-help-the-koha-commu… There are the results, and a list of remarks and notes that people did. I tried to give them answers. I let you comment, if you have something to add. Regards, Jonathan

2 1

After Upgrade no biblio_metadata and mo marcxml
by gevos 01 Aug '17

01 Aug '17

Overyesterday We have updated ubuntu server and the koha was updated too. Apparently because of the mysql 5.7 the script somehow failed and we have landed to a point where only from 30.000 books only 2 books landed to the book_metadata. and we don't have now the original column marcxml in biblioitems :((((((((((((((((( -- View this message in context: http://koha.1045719.n5.nabble.com/After-Upgrade-no-biblio-metadata-and-mo-m… Sent from the Koha-general mailing list archive at Nabble.com.

5 4

checkin problem
by Sahadeo Taware 01 Aug '17

01 Aug '17

Dear Friends When I checkin the book following error is shown Check in message The item has not been checked in due to a configuration issue in your system. You must ask an administrator to take a look at the about page <http://192.168.35.196:8080/cgi-bin/koha/about.pl#sysinfo> and search for the "data problems" section -- Sahadeo D. Taware Librarian, M.L.I.Sc., NET Thakur College of Science and Commerce Thakur Village, Kandivli(E), Mumbai 400101 Mob. No 9324912816 Office 28870627 Extn. 126

3 2

Slips and Notices
by Luis Moises Rojas 01 Aug '17

01 Aug '17

Hello everybody: There is not way, even the table: LETTER have data: 1. Nothing is display on the screen. 2. I can not save a new one. Any idea? Thanks -- *Luis Moisés Rojas P.*

1 0