Re: [Koha] Rotating IP Address and Koha Logout
Hi Charles, To temporarily get around this problem you can disable the SessionRestrictionByIP system preference in Koha. This binds the user's session ID to their public IP address. If it changes, the session becomes invalid and Koha will prompt for a new login. The changing IP seems to be unrelated to AWS as they appear to be your ISP addresses. Does the same problem exist outside of your organisation? For example, at home or on a mobile device. If not then the problem is most likely related to an outbound proxy at your end - your IT might look into this. If it still happens elsewhere then perhaps your ISP is doing something with transparent proxying that they might be able to help you with. Regards Barry <http://www.interleaf.ie/> *Barry Cannon* Technical Director b...@interleaf.ie+353-1-286-5855 <+353%201%20286%205855> Ext: 102 A98 YD30www.interleaf.ie On Tue, 5 Jul 2022 at 00:21, Charles Kelley wrote: > Hi, all! > > My library is moving its Koha ILS to an AWS-based server. In > development, it was on a standalone laptop. > > In the testing phase on the AWS server, we have noted that the IP > address for logins changes every thirty seconds and staff are signed out > from Koha. The staff have to sign in anew and refresh. Whatever the staff > were working on -- search, record editing, uploading new records, etc. -- > may or may not survive intact. > > We don't know what causes this, but it's like > > IP 42.0.2.35 > Staff types a search query. > IP 42.0.2.35 > Staff selects Edit Record from dropdown menu. > Sudden change to IP 42.0.2.29 > Record vanishes. > Login screen appears. > New IP 42.0.2.34 > Staff logs in anew > Staff backs up two tabs (or windows) and continues. > New IP 42.02.31 > Repeat of what staff intervention at New IP 42.0.2.34 > > Eventually whatever the staff were working on is accomplished, but > logging in anew and reentering the previous steps so often are a bit > inconvenient, to state the least. > > My IT staff doesn't understand this phenomenon. We checked the system > preferences, but we haven't changed the timeouts since Koha was initially > installed. Has this been reported to the Koha development teams or on this > discussion group before? > > Does anyone have an idea what would be causing this? > > -- > よろしくお願いします。 > > -- Charles. > > Until 2022-07-15: > Charles Kelley, MLS > PSC 704 Box 1029 > APO AP 96338 > +81-80-4356-2178 [JPN cell] > > From 2022-07-18: > Charles Kelley > c/o Bob and Ronni DiGioia > 147 Mitchel Drive > Oakland, MD 21550 USA > +1-301-741-7122 [US cell] > > mnogoja...@aol.com [h] > cmkelley...@gmail.com [p] > > linkedin.com/in/cmkelleymls > Meeting Your Information Needs. Virtually. > ___ > > Koha mailing list http://koha-community.org > Koha@lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha presents an error, and no longer shows the cataloged records after a search
sorry, should be: /var/log/kern.log Barry <http://www.interleaf.ie/> *Barry Cannon* Technical Director b...@interleaf.ie+353-1-286-5855 <+353%201%20286%205855> A98 YD30www.interleaf.ie On Fri, 19 Jun 2020 at 14:29, Barry Cannon wrote: > Do you know how many simultaneous connections there are and what modules > are being used? What OS are you running? > > The logs to check are: > > /var/log/syslog > /var/log/kernlog > > If it has been some time they may have rotated and you be able to check as > below. > > /var/log/syslog.1 > /var/log/kernlog.1 > > > > > > > <http://www.interleaf.ie/> > > > *Barry Cannon* Technical Director > > b...@interleaf.ie+353-1-286-5855 <+353%201%20286%205855> > > A98 YD30www.interleaf.ie > > > > On Fri, 19 Jun 2020 at 14:22, Victor Barroso Oliveira > wrote: > >> This occurs when some people use it simultaneously! >> How can I check for syslog or kernlog OOM errors? >> >> Em sex., 19 de jun. de 2020 às 10:16, Barry Cannon >> escreveu: >> >>> Is this after the server restart? Is it possible to get usage when you >>> next experience the problem? Also, can you check the syslog or kernlog for >>> any OOM errors? That might point towards a module eating RAM. >>> >>> >>> >>> >>> >>> >>> <http://www.interleaf.ie/> >>> >>> >>> *Barry Cannon* Technical Director >>> >>> b...@interleaf.ie+353-1-286-5855 <+353%201%20286%205855> >>> >>> A98 YD30www.interleaf.ie >>> >>> >>> >>> On Fri, 19 Jun 2020 at 14:14, Victor Barroso Oliveira < >>> vbovic...@gmail.com> wrote: >>> >>>> totalusedfree shared buff/cache available >>>> Mem:8168516 724984 72002201184 243312 >>>> 7201000 >>>> >>>> Em sex., 19 de jun. de 2020 às 10:11, Barry Cannon >>>> escreveu: >>>> >>>>> Hi Victor, >>>>> It appears the server is running out of memory. How much >>>>> RAM do you have at present? >>>>> >>>>> Barry >>>>> >>>>> >>>>> >>>>> >>>>> <http://www.interleaf.ie/> >>>>> >>>>> >>>>> *Barry Cannon* Technical Director >>>>> >>>>> b...@interleaf.ie+353-1-286-5855 <+353%201%20286%205855> >>>>> >>>>> A98 YD30www.interleaf.ie >>>>> >>>>> >>>>> >>>>> On Fri, 19 Jun 2020 at 14:08, Victor Barroso Oliveira < >>>>> vbovic...@gmail.com> wrote: >>>>> >>>>>> Good Morning, >>>>>> After a time of using several operators, Koha presents an error, and >>>>>> no >>>>>> longer shows the cataloged records after a search. >>>>>> Only after the server restarts does the records appear again in a >>>>>> search. >>>>>> Following are log files that are in the var / log / koha folder >>>>>> How can I solve this? >>>>>> Thank you, >>>>>> Victor >>>>>> ___ >>>>>> >>>>>> Koha mailing list http://koha-community.org >>>>>> Koha@lists.katipo.co.nz >>>>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>>>>> >>>>> ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha presents an error, and no longer shows the cataloged records after a search
Do you know how many simultaneous connections there are and what modules are being used? What OS are you running? The logs to check are: /var/log/syslog /var/log/kernlog If it has been some time they may have rotated and you be able to check as below. /var/log/syslog.1 /var/log/kernlog.1 <http://www.interleaf.ie/> *Barry Cannon* Technical Director b...@interleaf.ie+353-1-286-5855 <+353%201%20286%205855> A98 YD30www.interleaf.ie On Fri, 19 Jun 2020 at 14:22, Victor Barroso Oliveira wrote: > This occurs when some people use it simultaneously! > How can I check for syslog or kernlog OOM errors? > > Em sex., 19 de jun. de 2020 às 10:16, Barry Cannon > escreveu: > >> Is this after the server restart? Is it possible to get usage when you >> next experience the problem? Also, can you check the syslog or kernlog for >> any OOM errors? That might point towards a module eating RAM. >> >> >> >> >> >> >> <http://www.interleaf.ie/> >> >> >> *Barry Cannon* Technical Director >> >> b...@interleaf.ie+353-1-286-5855 <+353%201%20286%205855> >> >> A98 YD30www.interleaf.ie >> >> >> >> On Fri, 19 Jun 2020 at 14:14, Victor Barroso Oliveira < >> vbovic...@gmail.com> wrote: >> >>> total usedfree shared buff/cache available >>> Mem:8168516 724984 72002201184 243312 >>> 7201000 >>> >>> Em sex., 19 de jun. de 2020 às 10:11, Barry Cannon >>> escreveu: >>> >>>> Hi Victor, >>>> It appears the server is running out of memory. How much >>>> RAM do you have at present? >>>> >>>> Barry >>>> >>>> >>>> >>>> >>>> <http://www.interleaf.ie/> >>>> >>>> >>>> *Barry Cannon* Technical Director >>>> >>>> b...@interleaf.ie+353-1-286-5855 <+353%201%20286%205855> >>>> >>>> A98 YD30www.interleaf.ie >>>> >>>> >>>> >>>> On Fri, 19 Jun 2020 at 14:08, Victor Barroso Oliveira < >>>> vbovic...@gmail.com> wrote: >>>> >>>>> Good Morning, >>>>> After a time of using several operators, Koha presents an error, and no >>>>> longer shows the cataloged records after a search. >>>>> Only after the server restarts does the records appear again in a >>>>> search. >>>>> Following are log files that are in the var / log / koha folder >>>>> How can I solve this? >>>>> Thank you, >>>>> Victor >>>>> ___ >>>>> >>>>> Koha mailing list http://koha-community.org >>>>> Koha@lists.katipo.co.nz >>>>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>>>> >>>> ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha presents an error, and no longer shows the cataloged records after a search
Is this after the server restart? Is it possible to get usage when you next experience the problem? Also, can you check the syslog or kernlog for any OOM errors? That might point towards a module eating RAM. <http://www.interleaf.ie/> *Barry Cannon* Technical Director b...@interleaf.ie+353-1-286-5855 <+353%201%20286%205855> A98 YD30www.interleaf.ie On Fri, 19 Jun 2020 at 14:14, Victor Barroso Oliveira wrote: > totalusedfree shared buff/cache available > Mem:8168516 724984 72002201184 243312 > 7201000 > > Em sex., 19 de jun. de 2020 às 10:11, Barry Cannon > escreveu: > >> Hi Victor, >> It appears the server is running out of memory. How much RAM >> do you have at present? >> >> Barry >> >> >> >> >> <http://www.interleaf.ie/> >> >> >> *Barry Cannon* Technical Director >> >> b...@interleaf.ie+353-1-286-5855 <+353%201%20286%205855> >> >> A98 YD30www.interleaf.ie >> >> >> >> On Fri, 19 Jun 2020 at 14:08, Victor Barroso Oliveira < >> vbovic...@gmail.com> wrote: >> >>> Good Morning, >>> After a time of using several operators, Koha presents an error, and no >>> longer shows the cataloged records after a search. >>> Only after the server restarts does the records appear again in a search. >>> Following are log files that are in the var / log / koha folder >>> How can I solve this? >>> Thank you, >>> Victor >>> ___ >>> >>> Koha mailing list http://koha-community.org >>> Koha@lists.katipo.co.nz >>> Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha >>> >> ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha presents an error, and no longer shows the cataloged records after a search
Hi Victor, It appears the server is running out of memory. How much RAM do you have at present? Barry <http://www.interleaf.ie/> *Barry Cannon* Technical Director b...@interleaf.ie+353-1-286-5855 <+353%201%20286%205855> A98 YD30www.interleaf.ie On Fri, 19 Jun 2020 at 14:08, Victor Barroso Oliveira wrote: > Good Morning, > After a time of using several operators, Koha presents an error, and no > longer shows the cataloged records after a search. > Only after the server restarts does the records appear again in a search. > Following are log files that are in the var / log / koha folder > How can I solve this? > Thank you, > Victor > ___ > > Koha mailing list http://koha-community.org > Koha@lists.katipo.co.nz > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Wiki and repos down?
Hi, Is anyone else experiencing issues with the Wiki and 'debian.koha-community.org' . I can't seem to get to either for most of the morning. Regards Barry Cannon Interleaf Technology http://www.interleaf.ie Tel: +35312865855 Email: b...@interleaf.ie Skype: bar.cannon <http://conference.conul.ie/> ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Koha-dev list problems
Hi, Is anyone having issues posting to koha-devel? I have tried to post 3 times in the last two days. I've even un-subscribed and re-subscribed. I have also tried different email accounts but I can't seem to get a successfully post! Regards Barry Cannon Interleaf Technology http://www.interleaf.ie Tel: +35312865855 Email: b...@interleaf.ie Skype: bar.cannon <http://conference.conul.ie/> ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] http to https
Hi,
You can create a port 80 VirtualHost and add the lines below to it. Then,
create a port 443 VirtualHost with the correct config. Be mindful of the
ServerName entry too.
You will need to enable "rewrite" too - "a2enmod rewrite".
RewriteEngine on
RewriteCond %{SERVER_PORT} ^80$
RewriteRule ^(.*)$ https://%{SERVER_NAME}$1 [L,R]
Hope this helps.
Regards
Barry Cannon
Interleaf Technology
http://www.interleaf.ie
Tel: +35312865855
Email: b...@interleaf.ie
Skype: bar.cannon
From: Koha [koha-boun...@lists.katipo.co.nz] on behalf of vinod kumar
[vinod.kumar@gmail.com]
Sent: 11 May 2016 11:30
To: koha@lists.katipo.co.nz
Subject: [Koha] http to https
Dear All
How to *http to https redirect in apache2 *
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] FW: looking for urgent help
From: Barry Cannon Sent: 10 May 2016 09:45 To: Abdulrazak Aman Subject: RE: [Koha] looking for urgent help Hi, The WIKI page ( https://wiki.koha-community.org/wiki/Category:Installation ) should get you started. If you've any queries, just post them here and help will be along presently. Koha can certainly be installed in a hosting environment but it all depends on the type of system (options) you go for. I would recommend going for the self contained VPS/VM solution. That way, you have full control over the box and you can manage your system directly. Hope this helps. Regards Barry Cannon Interleaf Technology http://www.interleaf.ie Tel: +35312865855 Email: b...@interleaf.ie Skype: bar.cannon From: Koha [koha-boun...@lists.katipo.co.nz] on behalf of Abdulrazak Aman [abdulra...@arabou.edu.sa] Sent: 10 May 2016 08:00 To: koha@lists.katipo.co.nz Subject: [Koha] looking for urgent help Hi ,, I am new in KHOA and I need help installing it on my pc ( step by step) . And can KOHA be install in hostign company like bluehost / godaddy or hostgotar and what it need !! Looking for your URGENT help !! Regrads ,,, -- *ABDULRAZAK M. NOUR AMAN* *| * *Phone: +966. 1. 274 2277 P.O.Box84901, Riyadh 11681Mobile: +966. 509055150Kingdom Of Saudi ArabiaFax: +966. 1. 2742696 Email: abdulra...@arabou.edu.sa <abdulra...@arabou.edu.sa> SKYPE: abdulrazak.aman* *Never design ur character like a Garden where any one can walk. Design it like the sky where everyone aspires to reach? Have A Nice Day* ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] mysqldump (koha-dump)
Thanks Paul, We have a few systems with dumps over 2GB and unfortunately the lock holds out the system for some minutes. Replication may be a solution but obviously involves more cost! Regards Barry Cannon Interleaf Technology http://www.interleaf.ie Tel: +35312865855 Email: b...@interleaf.ie Skype: bar.cannon From: Paul A [pau...@navalmarinearchive.com] Sent: 07 January 2016 18:07 To: Barry Cannon; koha@lists.katipo.co.nz Subject: Re: [Koha] mysqldump (koha-dump) At 03:47 PM 1/7/2016 +, Barry Cannon wrote: >Hello, > I am curious how many people use the koha-dump script to dump > their Koha database? I am particularly interested to know how people are > dealing with larger databases where mysqldump causes table locking. We looked into this (not sure what your definition of "larger database" is -- our dumps are around 670 Megs) and decided to go the hardware route using solid state drives for both the db and the backups. End result, we have less than 4 seconds "downtime" for a daily cron-job which (so far, touch wood) has not given rise to any complaints. Note that we "clean" the db before dumping, specifically sessions (with the spiders we seem to get >100,000 / 24 hours despite blocking Baidu at the firewall) and imports (our cataloguers can get very busy) -- the mail, logs (we retain only 10 days) and zebraqueue appear to be less substantial -- which saves between 50 and 100 Megs. Best -- Paul >I would typically suggest using the '--single-transaction' option but I >notice there is still one table, pending_offline_operations, that isn't >using InnoDB as it's storage engine. Best practice is to use 'lock-tables' >in this instance (mysqldump locks by default) but with a larger database >this can cause a non responsive interface for the duration of the backup. >We have sites where the one system is used by users in different time >zones, this causes a headache as "out-of-hours" doesn't exist. > >LVM snapshots would be useful but prove tricky when using hosting providers. > >Any suggestions would be welcome! > >Regards >Barry Cannon >Interleaf Technology >http://www.interleaf.ie >Tel: +35312865855 >Email: b...@interleaf.ie >Skype: bar.cannon >___ >Koha mailing list http://koha-community.org >Koha@lists.katipo.co.nz >https://lists.katipo.co.nz/mailman/listinfo/koha --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca> ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] mysqldump (koha-dump)
Hello, I am curious how many people use the koha-dump script to dump their Koha database? I am particularly interested to know how people are dealing with larger databases where mysqldump causes table locking. I would typically suggest using the '--single-transaction' option but I notice there is still one table, pending_offline_operations, that isn't using InnoDB as it's storage engine. Best practice is to use 'lock-tables' in this instance (mysqldump locks by default) but with a larger database this can cause a non responsive interface for the duration of the backup. We have sites where the one system is used by users in different time zones, this causes a headache as "out-of-hours" doesn't exist. LVM snapshots would be useful but prove tricky when using hosting providers. Any suggestions would be welcome! Regards Barry Cannon Interleaf Technology http://www.interleaf.ie Tel: +35312865855 Email: b...@interleaf.ie Skype: bar.cannon ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha 3.12 Installation
Is your apache configured to listen on port 8080? What does "sudo netstat -anplt | grep 8080" show? If nothing, try modifying /etc/apache2/ports.conf and adding "Listen 8080" then restarting apache. Regards Barry Cannon Interleaf Technology http://www.interleaf.ie Tel: +35312865855 Email: b...@interleaf.ie Skype: bar.cannon From: Koha [koha-boun...@lists.katipo.co.nz] on behalf of Balaji Ravichandran [rbalaji...@gmail.com] Sent: 21 December 2015 08:38 To: Chrispin Simasiku Sitali Cc: koha-user Subject: Re: [Koha] Koha 3.12 Installation That doesn't work.I have problems while running it on 127.0.0.1:8080 .It says server not found On 21 December 2015 at 14:03, Chrispin Simasiku Sitali <libsit...@gmail.com> wrote: > Any particular reason you want to install 3.12? Follow these links for the > recommended way. > > http://wiki.koha-community.org/wiki/Koha_on_Debian > > and > > http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages > > Cheers > > > On 21 December 2015 at 10:28, Balaji Ravichandran <rbalaji...@gmail.com> > wrote: > >> Hi, >> >> Can anyone send the link on how to install Koha 3.12 in CentOS 6.6? >> Thank You >> >> >> -- >> Regards, >> Balaji Ravichandran ( பாலாஜி ) , >> Volunteer at Free Software Foundation - Tamilnadu, >> Mobile : 9790528505 >> My Blog - balogic.wordpress.com >> ___ >> Koha mailing list http://koha-community.org >> Koha@lists.katipo.co.nz >> https://lists.katipo.co.nz/mailman/listinfo/koha >> > > > > -- > Charles Lwanga College of Education, > P. O. Box 660193, > Monze, > ZAMBIA. > > Mobile: +26 0979 869471 > +26 0966 869471 > SKYPE: Libsitali > -- Regards, Balaji Ravichandran ( பாலாஜி ) , Volunteer at Free Software Foundation - Tamilnadu, Mobile : 9790528505 My Blog - balogic.wordpress.com ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Access-IT conversion.
Hello, Has anyone any experience migrating from an Access-IT system to Koha? If so, have you any notes and/or tools you can recommend for extracting the MARC data? Regards Barry Cannon Interleaf Technology http://www.interleaf.ie Tel: +35312865855 Email: b...@interleaf.ie Skype: bar.cannon ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Multiple OPAC interfaces
Hi Robin, We are hoping to run multiple OPAC themes, pointing to the same instance, but restricted in their respective searches. A simple example may be; one Koha instance with two locations. Each location has it's own themed OPAC interface, restricted to search only that locations (for bib, item information). I did manage to get this running in the past - before the Bootstrap change - so I just wondering if there has been any substantial changes to how to implement this. Regards Barry Cannon Interleaf Technology http://www.interleaf.ie Tel: +35312865855 Email: b...@interleaf.ie Skype: bar.cannon From: Koha [koha-boun...@lists.katipo.co.nz] on behalf of Robin Sheat [ro...@catalyst.net.nz] Sent: 29 June 2015 02:57 To: koha@lists.katipo.co.nz Subject: Re: [Koha] Multiple OPAC interfaces Barry Cannon schreef op vr 26-06-2015 om 14:26 [+]: Does anyone know if there is still support for running multiple OPAC interfaces since the move to Bootstrap? I remember having some luck a few years ago but that was before the change over. What do you actually mean? If you mean just running multiple different Koha instances off one server, then that hasn't changed. If you mean having multiple OPAC themes on one Koha instance* that is still done exactly the same way, though there's not really an official way. So, I'm not quite sure exactly what your question is, but the answer is almost certainly yes :) * http://www.stratfordlibrary.govt.nz/ = http://ils.stdc.govt.nz/ are the same thing, just with different theming depending on how you reach them. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Multiple OPAC interfaces
Hello, Does anyone know if there is still support for running multiple OPAC interfaces since the move to Bootstrap? I remember having some luck a few years ago but that was before the change over. Regards Barry Cannon Interleaf Technology http://www.interleaf.ie Tel: +35312865855 Email: b...@interleaf.ie Skype: bar.cannon ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] strange behavior with a public report
Could it be the SvcMaxReportRows Syspref is set to it's default of 10. This
could be only displaying the first 10 biblios everytime the report is run?
Regards
Barry Cannon
Interleaf Technology
http://www.interleaf.ie
Tel: +35312865855
Email: b...@interleaf.ie
Skype: bar.cannon
From: Koha [koha-boun...@lists.katipo.co.nz] on behalf of Arturo Longoria
[arturo.longo...@sll.texas.gov]
Sent: 13 May 2015 15:18
To: koha@lists.katipo.co.nz
Subject: [Koha] strange behavior with a public report
Hi all,
I've come across strange behavior with a public report in Koha since our
library was upgraded to 3.18. I'm not sure if it is a bug or if I am doing
something incorrectly, and so I thought I'd ask for some input.
I've created a custom SQL report that will output basic bibliographic data for
titles that are included in a list (virtual shelf), and I have marked this
report as public so that I can access its JSON output via
/cgi-bin/koha/svc/report?id={report id}sql_params={virtual shelf number} on
the public side. The issue I'm having is that if I run this report within the
staff client, it works perfectly. If I edit the list by adding/removing titles
to it and then re-run the report in the staff client, everything is displayed
as expected.
But if I run the report on the public side to get the JSON output, the report
will only show me bib. info for the titles that were originally saved in the
list! That is, when I first create a list and access its JSON output, it works
fine. But if I then edit the list by removing a title or adding a new title,
the JSON output is not updated – it continues to show me the old contents of
the list. If I run the report through the staff client, though, it does show me
the updated contents of the list! The two outputs are different.
Any ideas on what could be causing this? The report's settings have a cache
expiry of 0 seconds (the default). I've tried setting different cache expiry
periods to see if that is the issue, but that seems to do nothing. The SQL is a
very simple select statement:
SELECT biblionumber, author, title, seriestitle, copyrightdate, notes, abstract
FROM virtualshelfcontents vsc LEFT JOIN biblio using (biblionumber)
WHERE vsc.shelfnumber = Enter shelf number
Arturo Longoria
Texas State Law Library
www.sll.texas.govhttp://www.sll.texas.gov/
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] [Koha-devel] 3.18.06 Package Warning
I seem to be getting this error on a fresh install now? Unpacking koha-common (from .../koha-common_3.18.06.1_all.deb) ... dpkg: error processing /var/cache/apt/archives/koha-common_3.18.06.1_all.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/koha-common_3.18.06.1_all.deb Regards Barry Cannon From: Koha [koha-boun...@lists.katipo.co.nz] on behalf of Robin Sheat [ro...@catalyst.net.nz] Sent: 24 April 2015 05:16 To: koha@lists.katipo.co.nz; Koha Devel Subject: Re: [Koha] [Koha-devel] 3.18.06 Package Warning Renvoize, Martin schreef op do 23-04-2015 om 12:00 [+0100]: Don't Upgrade Koha Packages to 3.18.06 yet! 3.18.06.1 packages have been uploaded that should hopefully fix this. Turns out that everyone who tested it tested fresh installs, but it only broke on upgrading. Have a good ANZAC weekend, where appropriate :) -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] [Koha-devel] 3.18.06 Package Warning
This installs 3.16.09 fine. Reverting to the stable source and running an upgrade successfully gets Koha up to the latest version (3.18.06.01). Hacky, but it works! Regards Barry Cannon From: Craig Butosi [craig.but...@rcmusic.ca] Sent: 27 April 2015 14:42 To: Barry Cannon; koha@lists.katipo.co.nz; Koha Devel Subject: RE: [Koha] [Koha-devel] 3.18.06 Package Warning Hi Barry, I too was receiving this error. Very frustrating. I installed echo deb http://debian.koha-community.org/koha oldstable main to the /etc/apt/sources.list.d koha.list file instead of echo deb http://debian.koha-community.org/koha stable main [I made sure that I deleted this entry from the /etc/apt/sources.list.d koha.list file.] This did the trick for me. I am running Ubuntu 14.04 LTS 64-bit from a VPS. Best, Craig Butosi, MA, MLIS, B Mus (Hons.) LIBRARY SERVICES MANAGER THE ROYAL CONSERVATORY TELUS Centre for Performance and Learning 273 Bloor Street West Toronto, ON M5S 1W2 416.408.2824 x338 www.rcmusic.ca -Original Message- From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Barry Cannon Sent: April-27-15 9:33 AM To: koha@lists.katipo.co.nz; Koha Devel Subject: Re: [Koha] [Koha-devel] 3.18.06 Package Warning I seem to be getting this error on a fresh install now? Unpacking koha-common (from .../koha-common_3.18.06.1_all.deb) ... dpkg: error processing /var/cache/apt/archives/koha-common_3.18.06.1_all.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/koha-common_3.18.06.1_all.deb Regards Barry Cannon From: Koha [koha-boun...@lists.katipo.co.nz] on behalf of Robin Sheat [ro...@catalyst.net.nz] Sent: 24 April 2015 05:16 To: koha@lists.katipo.co.nz; Koha Devel Subject: Re: [Koha] [Koha-devel] 3.18.06 Package Warning Renvoize, Martin schreef op do 23-04-2015 om 12:00 [+0100]: Don't Upgrade Koha Packages to 3.18.06 yet! 3.18.06.1 packages have been uploaded that should hopefully fix this. Turns out that everyone who tested it tested fresh installs, but it only broke on upgrading. Have a good ANZAC weekend, where appropriate :) -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha Note: This email message and any attachments are intended only for the use of the individual to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the recipient of this email is not the intended recipient (or the employee or agent responsible for delivering the email to the intended recipient), you are hereby notified that any review, dissemination, distribution or copying or other use of this message is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return email and delete this message and attachments from your system, thank you. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Nagios Plugin SIP2 Check
Hello, I am not sure if there is any interest in this but I created a Nagios plugin to check the status of a SIP2 server. It is derived from another module I created, a SIP2 client, but seems to work well for what I need. The link is below. The plugins should work against any SIP2 compliant server - with or without SIP authentication and/or location code requirement etc. I have tested it against Koha, Horizon and Galaxy SIP servers. http://exchange.nagios.org/directory/Plugins/Network-Protocols/*-Others/SIP2-Server-Check/details Also, sorry if posting this type of posting is frowned upon. Regards Barry http://www.oslo.ie ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Authority Indexing
Hello, We have a library that wants to impose authority control on the 752 tag, subfields a,b,d to ensure consistency in entering place names. We have added the link to GEOGR_NAME to the biblio marc framework, adjusted the utilities to extract the authorities from the bibs to include the data, run the linker to link the auths and bibs together. Modified authority-koha-indexdefs.xml to pick up the new subfields (and regenerated the XSL file) The new authorities are in the file and are searchable, and the link is visible in the marcxml in the biblioitems record, BUT the authority search only shows the $a and does not show the number of linked biblios. Also, adding a new record and authority adds to the biblio record, but does not create the authority. Would anyone have any pointers on how we configure this correctly? Regards Barry ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Moodle and Koha
Hello, Does anyone know the current status of Moodle integration and Koha? Is there any integration at all in the current release? Regards Barry ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] DOM versus GRS-1
** Sorry if this double posted - having some problem with the list ** Hello, I recently upgraded a site from Koha 3.6 to 3.8.5 (via 3.8.3). Shortly afterwards we noticed that there was quite a few biblios not appearing on the search results even though they exist in the database. After trying many, many things I decided to switch from DOM to grs-1 and rebuild the indexes. This has resolved the problem and the search results are now correct. Switching back to DOM brings back the problem. Does anyone know why this might be the case - broadly speaking. Should DOM and grs create the same index result set by using different filters or are these types of differences expected? Thanks Barry ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] DOM versus grs-1
Hello, I recently upgraded a site from Koha 3.6 to 3.8.5 (via 3.8.3). Shortly afterwards we noticed that there was quite a few biblios not appearing on the search results even though they exist in the database. After trying many, many things I decided to switch from DOM to grs-1 and rebuild the indexes. This has resolved the problem and the search results are now correct. Switching back to DOM brings back the problem. Does anyone know why this might be the case - broadly speaking. Should DOM and grs create the same index result set by using different filters or are these types of differences expected? Thanks Barry ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] LDAP - shows wrong patron account.
Hello, We have a site currently running Koha 3.6.0 against an LDAP (AD) server for authentication. On more than one occasion a borrower (different each time) has reported logging into their account with their login details but being presented with somebody else's account details. As you can imagine the site are very concerned about the security implications of this problem. I checked the session table (in case CGI::Session had generated 2 identical session id's, which should be impossible anyway) and cleared it down but it didn't take long for another user to report the problem. I will enable some more verbose logging on the LDAP connection but I am wondering if anyone else has ever experienced such a problem? Thanks ba...@oslo.ie http://www.oslo.ie ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] 3.06.02 LDAP Problem
Hello, I have a new site running 3.06.02. I have configured LDAP as authentication and it seems to connect, authenticate and create the new patron correctly. The problem is though, that once the user logs in for the first time (and hence creates the Patron record) they are met with a Error 500 screen. The actual Patron record is created and if they click the login button and login again then it will display the patron page correctly (and does for all subsequent logins). There isn't much in the logs except for a Malformed Header - opac-user.pl error. If I add a Content-type header to the opac-user.pl script (and not rely on the template to add the header) the first time user can login fine and the page shows correctly. (so this leads me to think the problem is in the page header but only on LDAP creation as a manual Patron creation is fine for first time login) I also noticed that the LDAP auto creation doesn't add an expiration date, even though it assigns the correct Parton Category. So, does anyone gave any ideas before I log a bug and start debugging it? I have used LDAP before on pre 3.06.02 sites with no problems. Thanks Barry ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] 3.06.02 LDAP Problem
Could you please include exact error message including line number? There is no line number mentioned in the log as the problem is with the header which is generated by the template file (or rather, the included header file). All that is logged is the referer URL LDAP mappings can have default values, so in our example, we want to take LDAP field hredupersonexpiredate or if it's missing 2012-12-23 using following configuration: mapping ... dateexpiry is=hredupersonexpiredate2012-12-23/dateexpiry ... /mapping This is a non runner for any of our sites. Hard coding an expiry date seems excessive. I suspect the older versions used the default expiry period from the Category Code assigned to the new user to calculate the expiry date. I plan and rebuilding this in a staging environment to recreate the problem. Hopefully, I can track the problem down and get a patch out quickly. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Problems with Apache when trying to access Koha Admin
Hello, The problem here is that 'koha' user doesn't have access to the koha database with the credentials supplied. Can you check the user and password you specified in the /etc/koha/koha-conf.xml file? (search for db_scheme and you'll see the database details below that) Once you find the details try and login to MySQL from the command line with those details: mysql -u koha --password=PutYourPasswordHere If you don't get access then you will need to login to the MySQL database (as root or dba) and grant the koha user the correct permission on the koha database as directed in the install manual (replace parts in to fit your install): grant all on kohadatabasename.* to 'kohadatabaseuser'@'localhost' identified by 'mysql-password-for-kohadatabaseuser' You should be able to run the web installer then. Hope this helps Barry ba...@oslo.ie http://www.oslo.ie From: koha-boun...@lists.katipo.co.nz [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Sangduen Pongput Sent: 07 December 2011 08:55 To: koha@lists.katipo.co.nz Subject: [Koha] Problems with Apache when trying to access Koha Admin Dear All I has a same problem as another post about Problems with Apache when trying to access Koha Admin. Have anyone explian clearly step by step how to solve that. http://lists.katipo.co.nz/public/koha/2011-December/031407.html I have installed koha 3.06.01 following the instructions online for Ubuntu 11.10. Everything went well until now. When I try to go to 127.0.0.1:8080 I get this message. Software error: Access denied for user 'koha'@'localhost' (using password: YES) at /usr/share/koha/lib/C4/Context.pm line 693. Compilation failed in require at /usr/share/koha/lib/C4/Auth.pm line 33. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 33. Compilation failed in require at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 26. BEGIN failed--compilation aborted at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 26. Any ideas on how I fix this? http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/04.gif Thank you for your kind cooperation. http://us.i1.yimg.com/us.yimg.com/i/mesg/tsmileys2/04.gif Best regards, Sangduen Pongput Librarian The Secretariat of the Senate, Bureau of Parliamentary Studies, Library and Museum Group 4 U-Thong Nai Road, Dusit District, Bangkok 10300 THAILAND Tel +662 831 9313- 4 Mobile Phone +66 89 122 5347 Fax +662 831 9308 or +662 831 9314 sangd...@senate.go.th, sangdueni...@gmail.com, sangdue...@hotmail.com, m091225...@yahoo.com ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Migration from 2.2.5 to 3.4
Hi Peter, I have just performed something similar. The information on the wiki is useful but there are lots of omissions in the document. For instance, there is no mention of how (or where) to install the 3.0 file structure. I tired many different methods but in the end I found the easiest was to do the following: - Bring up a new Koha system on the first release of Koha 3.000. - Dump the Koha 2.x database - Load the 2.2 database on the new 3.0 system - Preform the upgrade steps as listed here (http://wiki.koha-community.org/wiki/Upgrading_2.2 ) - Once the steps are taken you can then open the Webinf and run the database upgrade (if needed) - You can then continue up to the latest version of Koha Like I said, I just completed this and it went well. However, this will only take your data and if you have any customisations to your system you will need to migrate them another way. Regards Barry http://www.oslo.ie From: koha-boun...@lists.katipo.co.nz [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Peter Thompson Sent: 12 August 2011 06:35 To: koha@lists.katipo.co.nz Subject: [Koha] Migration from 2.2.5 to 3.4 Hi, Hi, I'm a complete newcomer to the world of Koha. We have an installation of Koha 2.2.5 at a remote site, and we wish to migrate the data to a new server running 3.4. Simply importing the MySQL dump file doesn't seem to do the trick - I get the borrowers but not the bibs etc. I've searched the archives, but most information about in-situ upgrades. Anyone point me in the right direction doco-wise? Peter Thompson Information Technology Communications Unit Bendigo TAFE ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
