Re: [Koha-devel] plack in production
So, we applied Dobrica's patch on bug 13815, and this solved pretty much all of our problems. We'll be doing some more testing, but it turns out it was very much encoding related. (I guess Robin's catalog is in english language and didn't have this issue.) I realize there's one thing i didn't mention in my message: we are testing plack for the staff interface, i am much more confident for the opac indeed. (So much so that we didn't even test the opac! I guess we should...) Another thing i didn't mention in my original email is that we found bad .po files can cause plack to crash: if your translated string doesn't have the same number of %s as the original, this will result in a badly formated template, which will crash plack. (e.g. an if tag that is never closed.) Somehow this doesn't induce a crash when plack is not enabled. I had always thought that if the %s count for a string was wrong, the translation engine would leave the original string. It seems it's more complicated than this. Anyway, we'll be doing more tests and i'll keep you posted about our findings! Le 20/04/2015 00:12, Robin Sheat a écrit : Gaetan Boisson schreef op do 26-03-2015 om 16:17 [+0100]: we have been talking about plack quite a lot in the last hackfest, and i must say i am not that comfortable with the technical aspects and hardly understand what the issues are, but... I apparently missed this message when it was first posted. Anyway, we have a plack system in production. I'd link you to it, but it's closed and so it'll do you no good. It is really speedy though. In this case it's needed because this library sends out monthly newsletters to its members who then all descend on the OPAC en masse, which in the pre-plack days would make it OOM or at least just give up responding. However with plack, it serves the responses fast enough that it can handle the high load with a lot more success. The script I use to convert a package install to use plack is here: http://git.catalyst.net.nz/gw?p=koha-plack.git One of these days I'll probably make a branch of Koha that includes plack support by default in the packages, or make a package that provides the appropriate diverts to switch everything on that machine to plack, I haven't decided which way to go yet. We do have a few minor issues, but nothing as severe as what you're talking about. The main problem is that user separation makes memory allocation tricky as you need to pre-allocate per koha instance, which is a bit much. At the same time, we don't want to risk giving the process read access to every koha-conf.xml as that's dangerous. We do have a solution for this (it's weird, but it'll do), I just haven't had a chance to tie it in. ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -- Gaetan Boisson Chef de projet bibliothécaire BibLibre 06 52 42 51 29 108 avenue Breteuil 13006 Marseille gaetan.bois...@biblibre.com ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] plack in production
Gaetan Boisson schreef op do 26-03-2015 om 16:17 [+0100]: we have been talking about plack quite a lot in the last hackfest, and i must say i am not that comfortable with the technical aspects and hardly understand what the issues are, but... I apparently missed this message when it was first posted. Anyway, we have a plack system in production. I'd link you to it, but it's closed and so it'll do you no good. It is really speedy though. In this case it's needed because this library sends out monthly newsletters to its members who then all descend on the OPAC en masse, which in the pre-plack days would make it OOM or at least just give up responding. However with plack, it serves the responses fast enough that it can handle the high load with a lot more success. The script I use to convert a package install to use plack is here: http://git.catalyst.net.nz/gw?p=koha-plack.git One of these days I'll probably make a branch of Koha that includes plack support by default in the packages, or make a package that provides the appropriate diverts to switch everything on that machine to plack, I haven't decided which way to go yet. We do have a few minor issues, but nothing as severe as what you're talking about. The main problem is that user separation makes memory allocation tricky as you need to pre-allocate per koha instance, which is a bit much. At the same time, we don't want to risk giving the process read access to every koha-conf.xml as that's dangerous. We do have a solution for this (it's weird, but it'll do), I just haven't had a chance to tie it in. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF signature.asc Description: This is a digitally signed message part ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] plack in production
Hello, we have tested plack a little further. We have achieved much more stability but are still encountering very serious bugs, before filing a report for each of them, i would like to ask here whether it does sound like something that is happening because of plack, and whether this has been identified before : - A vast majority of records are giving a The record you requested does not exist message when trying to display the detailed record, even though the record does seem to exist in the database, and i was even able to check out items linked to said record. - trying to place a reservation and a document from a result list results in an error, maybe unsurprisingly given the above : Can't call method field on an undefined value at /home/koha/src/C4/Items.pm line 1625. at /usr/share/perl/5.18/CGI/Carp.pm line 378 - i noticed a delay between changing circulation rules and seeing them applied when checking out items (the rule was saying i could borrow 13 items, i brought it down to 2, but was then able to checkout 3 items without getting a notice. Shortly after i was getting proper notices telling me i was exceeding the quota) - There were numerous encoding problems with non ascii characters, this might be linked to Bug 13815 - plack loose CGI qw(-utf8) flag creating incorrect utf-8 encoding everywhere; but this was not just patrons. Cataloging frameworks, authorised values, fund names were all affected. - exporting data from cgi-bin/koha/tools/export.pl also lead to a crash, which seems to be linked to UTF-8 issue too: :11: parser error : Input is not proper UTF-8, indicate encoding ! Bytes: 0x80 0x3C 0x2F 0x73 subfield code=p5.40�/subfield ^ at /home/koha/src/tools/export.pl line 683 Let me know what seems geniunely new and plack related to you and i will file the bugs. Thanks! Le 26/03/2015 16:17, Gaetan Boisson a écrit : Hello all, we have been talking about plack quite a lot in the last hackfest, and i must say i am not that comfortable with the technical aspects and hardly understand what the issues are, but... I tried it with the help of our sysops a couple days ago, and i must say koha does feel *really* fast with plack enabled. If you havent yet, you should try. It really made me realize why this should be a priority for us to get it to work. Now, it turns out it really doesn't work for us. It keeps crashing every few minutes. We haven't had time to investigate any further, but before pouring more time in this i wanted to know whether anyone was using it seriously (including for the staff interface), and what your conclusions are. Importantly, i would also like to know more about the recommended configuration, and the areas we should have a close look at in our set up. Thanks for your advice! -- Gaetan Boisson Chef de projet bibliothécaire BibLibre 06 52 42 51 29 108 avenue Breteuil 13006 Marseille gaetan.bois...@biblibre.com ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Re: [Koha-devel] plack in production
Great info Gaetan! What does everyone feel about these tests? Can we get a little feedback here so that we can get some good bugs going? The can't call method field I've seen before - but I have always chalked that up to a bad MARC record. (Please let's kill MARC ;) we can do better ;) ) The other ones I haven't seen before. Thanks, Brendan On Fri, Apr 17, 2015 at 7:00 AM, Gaetan Boisson gaetan.bois...@biblibre.com wrote: Hello, we have tested plack a little further. We have achieved much more stability but are still encountering very serious bugs, before filing a report for each of them, i would like to ask here whether it does sound like something that is happening because of plack, and whether this has been identified before : - A vast majority of records are giving a The record you requested does not exist message when trying to display the detailed record, even though the record does seem to exist in the database, and i was even able to check out items linked to said record. - trying to place a reservation and a document from a result list results in an error, maybe unsurprisingly given the above : Can't call method field on an undefined value at /home/koha/src/C4/Items.pm line 1625. at /usr/share/perl/5.18/CGI/Carp.pm line 378 - i noticed a delay between changing circulation rules and seeing them applied when checking out items (the rule was saying i could borrow 13 items, i brought it down to 2, but was then able to checkout 3 items without getting a notice. Shortly after i was getting proper notices telling me i was exceeding the quota) - There were numerous encoding problems with non ascii characters, this might be linked to Bug 13815 - plack loose CGI qw(-utf8) flag creating incorrect utf-8 encoding everywhere; but this was not just patrons. Cataloging frameworks, authorised values, fund names were all affected. - exporting data from cgi-bin/koha/tools/export.pl also lead to a crash, which seems to be linked to UTF-8 issue too: :11: parser error : Input is not proper UTF-8, indicate encoding ! Bytes: 0x80 0x3C 0x2F 0x73 subfield code=p5.40�/subfield ^ at /home/koha/src/tools/export.pl line 683 Let me know what seems geniunely new and plack related to you and i will file the bugs. Thanks! Le 26/03/2015 16:17, Gaetan Boisson a écrit : Hello all, we have been talking about plack quite a lot in the last hackfest, and i must say i am not that comfortable with the technical aspects and hardly understand what the issues are, but... I tried it with the help of our sysops a couple days ago, and i must say koha does feel *really* fast with plack enabled. If you havent yet, you should try. It really made me realize why this should be a priority for us to get it to work. Now, it turns out it really doesn't work for us. It keeps crashing every few minutes. We haven't had time to investigate any further, but before pouring more time in this i wanted to know whether anyone was using it seriously (including for the staff interface), and what your conclusions are. Importantly, i would also like to know more about the recommended configuration, and the areas we should have a close look at in our set up. Thanks for your advice! -- Gaetan Boisson Chef de projet bibliothécaire BibLibre 06 52 42 51 29 108 avenue Breteuil 13006 Marseille gaetan.bois...@biblibre.com ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/ -- --- Brendan A. Gallagher ByWater Solutions CEO Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Headquarters: Santa Barbara, CA - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com i...@bywatersolutions.com ___ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
