Re: [Koha] [EXTERNAL] Re: Reports timing out, prevents access to web interfaces

[Bales (US), Tasha R]

Hi Cab, that is in fact helpful feedback.  I've taken queries that we've used 
for years with Millennium and Oracle, and am rewriting them for Koha and MySQL. 
 So far, MySQL does seem pickier.  I have tried using the "EXPLAIN" command to 
help identify inefficient queries, but it didn't really help.  

One tactic we've tried in the past is to create views containing subsets of 
data that we need to frequently iterate over, to help decrease processing time. 
 Maybe that is an approach we could use here, but I am wary of trying to modify 
our database in any way.  Maybe a last resort.  Thanks again.  


Tasha Bales 
Enterprise Services
http://isesi.web.boeing.com/

-Original Message-
From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Cab Vinton
Sent: Thursday, October 7, 2021 03:49
To: koha 
Subject: [EXTERNAL] Re: [Koha] Reports timing out, prevents access to web 
interfaces

EXT email: be mindful of links/attachments.



I don't have any particularly helpful advice to offer, unfortunately, but I can 
confirm from personal experience that certain queries can indeed bring your 
system to a crawl. I don't think there's a solution to this unless there's a 
way to firewall report queries from the rest of Koha, or to automatically 
throttle misbehaving processes.

In my case, I'd copied & pasted a report from the wiki, but a change in Koha's 
database structure since the report's creation led to, well, very bad results.

I think your best bet is to take a really close look at the report to see if 
there are ways to achieve the same results more efficiently. In our case, this 
means seeking help from folks who are far more experienced with SQL than we are.

Best of luck!

Cab Vinton, Director
Plaistow Public Library
Plaistow, NH
___

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] [EXTERNAL] Re: Reports timing out, prevents access to web interfaces

[Bales (US), Tasha R]

Thanks for your reply, Chris.  One of our team members posited that there might 
be an issue---or something we can tweak--to decrease the priority of 
Reports/MySQL, so that it isn’t sucking the life out of the rest of the 
application.  We’ll keep investigating.


Tasha Bales
Enterprise Services
http://isesi.web.boeing.com/

From: Chris Brown [mailto:ch...@stayawake.co.uk]
Sent: Wednesday, October 6, 2021 23:40
To: Bales (US), Tasha R ; koha 

Subject: [EXTERNAL] Re: [Koha] Reports timing out, prevents access to web 
interfaces
Importance: High


EXT email: be mindful of links/attachments.




Hi Tasha,

Since I'm guessing you have access to a Linux command prompt on your server, 
you could try running "top". It would at least confirm if the CPU is saturated, 
and which processes are consuming all the CPU.

Best Regards,

Chris Brown




On Wed, Oct 6, 2021 at 10:32 PM Bales (US), Tasha R 
mailto:tasha.r.ba...@boeing.com>> wrote:
Good afternoon,

I'm experiencing an issue where if I'm working in the staff interface and kick 
off a long-running Report, I'm unable to navigate to or use Koha in any other 
browser tab, or in any other browser, either in the staff or public interface.  
I've confirmed that this affects other users working on their own machines too; 
in other words, my report interrupts their access.

I doubt that this is intended behavior.  I'm going to try to do some 
query-tuning (any suggestions for tools to use to optimize/identify inefficient 
queries?).

Any other ideas to troubleshoot this issue?  I found an old list post that 
suggested the Koha Tuning 
Guide on the Koha Wiki, 
but it isn't entirely clear to me if it is comprehensive, or if all parts are 
relevant to our issue.  I'm hesitant to blindly start changing values.  Before 
we pursue the tuning, are there any other suggestions?  Is this really a 
problem that is expected to happen?

I should add that long queries that need to be run on a routine basis, we'd run 
via cronjob.  However, I'm worried that staff who work solely on the web might 
inadvertently run a big one-off report (or do a huge record load, also a 
problem), and bring down the whole system.

FWIW, we have two processors:  Intel(R) Xeon(R) Silver 4110 CPU @ 2.10GHz.  We 
have about 1.3 million records and the same number of items.  We're using MySQL 
5.7, and Koha 20.11.06.

Regarding RAM, this is the output of the "free" command, if relevant:

totalused  freeshared   
 buff/cache   available
Mem:   65308616   203882041354324  10780021915472 
62437176
Swap:   8257532 7808256752


Tasha Bales
Enterprise Services
http://isesi.web.boeing.com/

___

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] LDAP changes from 19.xx to 21.05 ?

[Hector Gonzalez Jaime]

Hello, we recently tried to update our development server to 21.05, and 
it mostly works, but it does not like our LDAP setup, which is unchanged.


plack-error.log is filled with errors from this one:

Error while loading /etc/koha/plack.psgi: No ldapserver "hostname" 
defined in KOHA_CONF: /etc/koha/sites/clavius/koha-conf.xml at 
/usr/share/koha/lib/C4/Auth_with_ldap.pm line 58,  line 755.


Now, we did not touch our LDAP configuration, which was correct and 
working with 19.11.  Can somebody help find out what changed? Our ldap 
configuration is like this now:



 
    ip.address.for.server
    ou=users,dc=domain,dc=example,dc=org
    1
    1   
    1
uid=%s,ou=users,dc=domain,dc=example,dc=org
     

  
  
  
  Tijuana, BCN
  
  TJNA
  
  
  
  
  STUDENT
  1
    
  

Thanks.

--
Hector Gonzalez
ca...@genac.org

___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Bywater solutions Support Plugin gives 500 error

[Dhyaneshwar Shukla.]

After successful installation and configuration of  ByWater Solutions
Support Plugin  , when i try to run the plugin it gives an error 500.
Please help.
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] ElasticSearch faceted search

[Thomas Klausner]

Hi!

I'm trying to add a new facet, but it seems that the field names 
available for faceted search are hardcoded in the source code in
Koha::SearchEngine::Elasticsearch->get_facetable_fields

It also seems that any changes I make via the UI in 
admin/searchengine/elasticsearch/mappings.pl
are not saved to the DB. Is this UI not meant for updated?

Here: 
https://koha-community.org/manual/21.05/en/html/searching.html#elasticsearch-indexes
some yaml files are mentioned. Do I need to edit those files and the UI 
is just a red herring?

Greetings,
domm


-- 
#!/usr/bin/perl https://domm.plix.at
for(ref bless{},just'another'perl'hacker){s-:+-$"-g&$_.$/}
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha