Daniel, if you use plack, check your access logs with:
sudo tail -f /var/log/koha/YOURKOHASITE/plack.log
or
sudo grep opac-search /var/log/koha/YOURSITE/plack.log | more
search the list archives, there was a discussion a few weeks back about
this, and ways to use fail2ban to help with bots th
Hi,
Yes, the idea is to identify who is calling the opac-search.pl.
The opac-search.pl is not a service, therefore "someone" needs to run it.
Unless there is something that put it in a sort of endless loop or it hungs
up
Hope helps,
Alvaro
Le ven. 16 août 2024, 16:09, Daniel Owens a écrit :
Thank you for responding, Alvaro.
I hadn't recently checked apache logs. I had been checking the apache
error logs to see why apache was shutting down. But that seems to have
been resolved with memcache.
But the CPU issue remains. I am guessing you mean the access log? I
don't see much there
We are using IP.
Peter Washkevich
Systems Librarian
St. Johns County Public Library System
St. Johns County Board of County Commissioners
Library Support Services
6670 U.S. 1 South, St. Augustine, FL 32086
904-827-6923 | www.sjcpls.org
-Original Message-
From: Koha On Behalf O
Dear Colleagues,
It is good to be back in the Koha Community. Those of you whose libraries
have an online subscription to the New York Time newspaper for your
patrons- how do you authenticate your patrons to use NYT? I was thinking of
using the Koha restricted page which is available at /cgi-bin/k
Maybe https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37606
for wrong import after export of a framework ?
Best regards
S. Meynieux
Le 16/08/2024 à 14:05, spazz...@magritte.it a écrit :
Hi,
I'm here again.
As I wrote in a previous thead (
https://lists.katipo.co.nz/public/koha/202
Hi,
I'm here again.
As I wrote in a previous thead (
https://lists.katipo.co.nz/public/koha/2024-August/060888.html) I realized
that I have a corrupt default MARC bibliographic framework
I don't know why, I don't know since when.
I didn't bothered because frameworks we currently use are almost
Hi Daniel,
I agree with Alvaro's suggestion. We recently had the same problem (and the
same script opac-search.pl taking up all the CPU). A look through the
apache log files showed very frequent accesses by a number of bots. I put a
robots.txt file at the top level of the site and the problem went
8 matches
Mail list logo
