- Koha-devel - lists.koha-community.org

Fwd: SC Status before sip2 login
by Karam Qubsi 27 Aug '19

27 Aug '19

Hello Koha Developers, Do you think we should have an option for SIP2 server to allow SC status (99) before the login (93) ? I'm not aware if anyone else before reported about such a problem, I may try to develop this feature for the community if you think it is going to be useful for others, And of course I wish someone can give me some tips about where to start, I tried to look in the SIP2 server code. and it is still not clear for me where is the place we are closing connection if not logged in. if someone can point me to that , this would be really helpful. I'm talking about the raw_transport. Thank you very much. ---------- Forwarded message --------- From: Karam Qubsi <karamqubsi(a)gmail.com> Date: Mon, Aug 26, 2019 at 6:29 PM Subject: SC Status before sip2 login To: Koha <Koha(a)lists.katipo.co.nz> Hello Koha Community, I'm working with a selfcheck machine that is sending the sc status request (99) before the login request (93) . and that is causing koha sip server to close the connection. >From official documentation of SIP * , it look like that this status message can be sent before initialising SIP login, so I'm not sure if there is an option to allow this request or even allow login without username/password as we are going to secure the connection using ssh anyway. Any ideas or tips would be highly appreciated, Thank you very much Karam . * http://multimedia.3m.com/mws/media/355361O/sip2-protocol.pdf (page 6 ) : > SC Status > The SC status message sends SC status to the ACS. It requires an ACS > Status Response message reply from the ACS. This message will be the first > message sent by the SC to the ACS once a connection has been established > (exception: the Login Message may be sent first to login to an ACS server > program). The ACS will respond with a message that establishes some of the > rules to be followed by the SC and establishes some parameters needed for > further communication. -- *Karam Qubsi* -- *Karam Qubsi*

1 0

mailing list migration
by Laurent Ducos 20 Aug '19

20 Aug '19

Hello. The mailman mailing list server for koha-community was migrated last week. Thank you Chris for your help on the area dns koha-community. the novelties are : 1 : A dedicated server on ubuntu bionic. 2 : Mailman upgrade. 3 : A better postfix configuration. 4 : Interaction whith spamassassin. 4 : Better protection with fail2ban filters. 5 : Lets encrypt certificate. 6 : Netdata monitoring. Have a good day. -- Laurent Ducos Administrateur système et réseaux chez BibLibre IT system and network administrator at BibLibre

2 1

Call for News: August 2019 Newsletter
by kohanews 14 Aug '19

14 Aug '19

I'm collecting news for the August newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: - Please include dates for past events. If I can't find dates I may not add it. - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon - For past events , **** one month back is the cut-off ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

items.itype FK constraint?
by Tomas Cohen Arazi 05 Aug '19

05 Aug '19

Why shouldn't we add it :-D -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

5 6

just a test
by laurent ducos 05 Aug '19

05 Aug '19

sorry for the noise

2 1

Koha Community Newsletter: July 2019 [ TYPO ]
by kohanews 01 Aug '19

01 Aug '19

* This is the *_/July 2019/_* newsletter, not the June newsletter! -- Chad Roseburg Editor, Koha Community Newsletter

1 0

Koha Community Newsletter: July 2019
by kohanews 01 Aug '19

01 Aug '19

The Koha Community Newsletter for June 2019 is here: https://koha-community.org/koha-community-newsletter-july-2019/ Many thanks to the folks who submitted articles and news to this month's newsletter. Please feel free to email me with any corrections or suggestions. -- Chad Roseburg Editor, Koha Community Newsletter

1 0

possible problemas with plack at koha 18.11.08
by Hugo Agud 31 Jul '19

31 Jul '19

Good morning We are testing koha 18.11.08 and we are experiencing a strange behaviour that we're not able to identify, because there is no logs error, we suspect perhaps a version issue, the main thing is that we have no way of reproduce the error, it seems like a combination of actions, that we have not been able to identify It is a fresh koha's 18.11.08 install at debian 9 and upgrade from koha 3.22 database The main problem is that the server enters in a time out mode, and doesn't answer any action.... it happens usually after many login or logouts, not everytime... just 'selected' times...apache is working fine, and we're only able to recover koha if we restart plack, nothing happens if restart apache. We have identify an improve blocking template_cache, but it still happens.... Perhaps it could be hardware problem? we're a little lost.. There is pleny of logs at *opac-error.log* ¡[Wed Jul 31 09:41:58.037878 2019] [proxy_http:error] [pid 8828] (70007)*The timeout specified has expired*: [client 85.61.104.214:54219] AH01102: error reading status line from remote server httpd-UDS:0, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl?logout.x=1 [Wed Jul 31 09:41:58.037904 2019] [proxy:error] [pid 8828] [client 85.61.104.214:54219] AH00898: Error reading from remote server returned by /cgi-bin/koha/opac-image.pl, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl?logout.x=1 [Wed Jul 31 09:41:59.321815 2019] [proxy_http:error] [pid 13288] (70007)The timeout specified has expired: [client 85.61.104.214:54081] AH01102: error reading status line from remote server httpd-UDS:0, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl?logout.x=1 [Wed Jul 31 09:41:59.321880 2019] [proxy:error] [pid 13288] [client 85.61.104.214:54081] AH00898: Error reading from remote server returned by /cgi-bin/koha/opac-image.pl, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl?logout.x=1 [Wed Jul 31 09:44:17.135165 2019] [proxy_http:error] [pid 18060] (104)Connection reset by peer: [client 85.61.104.214:54166] AH01102: error reading status line from remote server httpd-UDS:0, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl [Wed Jul 31 09:44:17.135231 2019] [proxy:error] [pid 18060] [client 85.61.104.214:54166] AH00898: *Error reading from remote server returned by /cgi-bin/koha/opac-image.pl <http://opac-image.pl>*, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl [Wed Jul 31 09:44:17.135433 2019] [proxy_http:error] [pid 18059] (104)Connection reset by peer: [client 85.61.104.214:54126] AH01102: error reading status line from remote server httpd-UDS:0, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl [Wed Jul 31 09:44:17.135472 2019] [proxy:error] [pid 18059] [client 85.61.104.214:54126] AH00898: Error reading from remote server returned by /cgi-bin/koha/opac-image.pl, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl [Wed Jul 31 09:44:17.135659 2019] [proxy_http:error] [pid 18287] (104*)Connection reset by peer: [client 85.61.104.214:54200 <http://85.61.104.214:54200>]* AH01102: error reading status line from remote server httpd-UDS:0, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl [Wed Jul 31 09:44:17.135655 2019] [proxy_http:error] [pid 18061] (104)Connection reset by peer: [client 85.61.104.214:54229] AH01102: error reading status line from remote server httpd-UDS:0, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl [Wed Jul 31 09:44:17.135694 2019] [proxy:error] [pid 18287] [client 85.61.104.214:54200] AH00898: Error reading from remote server returned by /cgi-bin/koha/opac-shelves.pl, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl [Wed Jul 31 09:44:17.135700 2019] [proxy:error] [pid 18061] [client 85.61.104.214:54229] AH00898: Error reading from remote server returned by /cgi-bin/koha/opac-user.pl, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl [Wed Jul 31 09:44:17.137927 2019] [proxy_http:error] [pid 18170] (104)Connection reset by peer: [client 85.61.104.214:54203] AH01102: error reading status line from remote server httpd-UDS:0, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl [Wed Jul 31 09:44:17.140970 2019] [proxy_http:error] [pid 19542] (104)Connection reset by peer: [client 85.61.104.214:54258] AH01102: error reading status line from remote server httpd-UDS:0, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl [Wed Jul 31 09:44:17.141011 2019] [proxy:error] [pid 19542] [client 85.61.104.214:54258] AH00898: Error reading from remote server returned by /cgi-bin/koha/opac-search.pl, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl [Wed Jul 31 09:44:17.143334 2019] [proxy_http:error] [pid 19652] (104)Connection reset by peer: [client 85.61.104.214:54083] AH01102: error reading status line from remote server httpd-UDS:0, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl [Wed Jul 31 09:44:17.143376 2019] [proxy:error] [pid 19652] [client 85.61.104.214:54083] AH00898: Error reading from remote server returned by /cgi-bin/koha/opac-authorities-home.pl, referer: http://koha1811.orex.es/cgi-bin/koha/opac-main.pl *plack-error *(almost no error) Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $excluding[0] in concatenation (.) or string at /usr/share/koha/opac/cgi-bin/opac/opac-authorities-home.pl line 81. *DBIx::Class::ResultSet::_construct_results(): Unable to properly collapse has_many results in iterator mode due to order criteria - performed an eager cursor slurp underneath. Consider using ->all() instead at /usr/share/koha/lib/Koha/Objects.pm line 209* any help will be welcomed -- *Hugo Agud - Orex Digital * *www.orex.es <http://www.orex.es>* <http://www.orex.es/> [image: www.orex.es/koha] <http://www.orex.es/koha> [image: www.orex.es/vufind] <http://www.orex.es/vufind> Director Passeig Comte Vilardaga, 118 3-3 08980 -Sant Feliu de Llobregat - Tel: 933 856 138 hagud(a)orex.es · http://www.orex.es/ No imprima este mensaje a no ser que sea necesario. Una tonelada de papel implica la tala de 15 árboles y el consumo de 250.000 litros de agua. Aviso de confidencialidad Este mensaje contiene información que puede ser CONFIDENCIAL y/o de USO RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni está autorizado a recibirlo por el remitente), no está autorizado a copiar, reenviar o divulgar el mensaje o su contenido. Si ha recibido este mensaje por error, por favor, notifíquenoslo inmediatamente y bórrelo de su sistema.

1 0

Koha barcode - patron barcode Processing
by Jeremy Smith 30 Jul '19

30 Jul '19

Hello, I wonder if you can point use in the right direction to modify the Koha system we’ve just installed? We’ve set up a basic system to use with barcodes and barcode readers for both items and patrons. The problem is that our ID card barcodes add two leading 0s to staff IDs (7 digits vs 9 digits for students) and also the last number is not part of the ID number but the card issue number. Somehow we want to intercept the string to remove any leading zeros and also delete the last digit before it gets used as the patron number by Koha. Could you give us a pointer as to where I should be looking (i.e. any documentation or which module to look at) and what string I should be processing? I’ve found the patrons.js, in autocomplete, but suspect that is running when text is been entered, however the barcode enters the full string and probably a CR which I suspect is the equivalent of the submit being pressed. Basically I’m looking for hints as to where the string goes when the Submit button is pressed. Can anyone give me a hint? Many thanks, Jeremy P.S. I did post before but didn’t get any responses and can’t reply to me post as I didn’t get the post by email.

2 1

Re: [Koha-devel] Koha, centOS, Apache, starman => random timeout !
by Paul Poulain 26 Jul '19

26 Jul '19

That's not surprising, that's Apache calling/forwarding to starman (we're not using a socket, I don't remember why) (and we've how updated the config to have 127.0.0.1:5000 instead of localhost Le 18/07/2019 à 12:24, Stefano Bargioni a écrit : > A reverse proxy running on localhost:5000...??? > HTH. Stefano > >> On 18 Jul 2019, at 11:37, Paul Poulain <paul.poulain(a)biblibre.com >> <mailto:paul.poulain@biblibre.com>> wrote: >> >> Hello, >> >> We have a library running Koha (17.11) on his own centOS (virtual) >> server, with Apache as webserver. >> >> Everything is working smoothly, except that, from time to time (about >> once a day), it's not working anymore, any page returns: "Proxy >> error, Error reading from remote server" >> >> The logs shows nothing except a strange: >> >> [Wed Jul 10 17:17:35.732798 2019] [proxy_http:error] [pid 322] >> (70007)The timeout specified has expired: [client 1.2.3.4:32988] >> AH01102: error reading status line from remote server localhost:5000, >> referer: >> https://xxx.xxx.xxx.fr/cgi-bin/koha/catalogue/detail.pl?biblionumber=78504&… >> >> [Wed Jul 10 17:17:35.732861 2019] [proxy:error] [pid 322] [client >> 1.2.3.4:32988] AH00898: Error reading from remote server returned by >> /cgi-bin/koha/catalogue/search.pl, referer: >> https://xxx.xxx.xxx.fr/cgi-bin/koha/catalogue/detail.pl?biblionumber=78504&… >> <https://admin.panam.culture.fr/cgi-bin/koha/catalogue/detail.pl?biblionumbe…> >> >> What is stranger : after a few minutes, without any action on the >> server, everything is back, and working well. >> >> did anyone face such a problem ? any idea welcomed ! >> >> -- >> Paul Poulain, Associé-gérant / co-owner >> BibLibre, Services en logiciels libres pour les bibliothèques >> BibLibre, Open Source software and services for libraries >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel(a)lists.koha-community.org >> <mailto: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/ > -- Paul Poulain, Associé-gérant / co-owner BibLibre, Services en logiciels libres pour les bibliothèques BibLibre, Open Source software and services for libraries

2 1