Hi Jesse,
thx for adding the link and making the other suggested corrections. I've
added your company to the list of support companies. Please check if
everything is correct and let me know if anything needs to be changed.
Regards,
Katrin
On 13.04.21 08:26, jesse...@edgetech.com.my wrote:
Hi Frank,
thank you for adding the link. I've added your company to the list of
support companies. Please check if everything is correct and let me know
if anything needs to be changed.
Best regards,
Katrin
On 19.04.21 03:21, SYDT - Frank Chou wrote:
Dear Kartrin,
We've modified our koha
Ah! I see in my logs:
Semrushbot ...
petalbot ...
AhrefsBot/7.0 ...
Although it appears to be hitting us just once a second or so. Maybe
that is enough on a 1 core system.
Once I started searching Koha docs for robots.txt I found:
José Anjos 2016-12-22 10:25:27 UTC
I added file robots.txt
Check the apache logs and find the web server log corresponding to those
requests. That should either give you a bot name you can use for a
robots.txt entry or an IP you can block at your firewall.
Joel Coehoorn
Director of Information Technology
York College of Nebraska
On Wed, Apr 21, 2021 at
Hi
Lately our library instance is peaking at 100% CPU usage. When I login
and use "htop" I can see the opac search and export is, every 30
seconds, starting and using 100% CPU for 15 seconds or so. It then stops
and 30 seconds later does it again. I'm averaging 80% CPU usage just
from this.
Thanks Joonas
I restarted memcached (/etc/init.d/restart) and now System Information
show "No warnings."
This is the first I have heard of plack. A list of the processes running
show that its not running.
I do see "koha-plack --help" shows it is installed but not enabled or
running.
Maybe
Hi,
if you restarted plack, then I wonder if it could be in memcached, try
restarting it and tell us how it goes. After restarting memached I think
you need to restart plack one more time to flush the caches there as well.
Joonas
On 21/04/2021 13:34, Mike Lake wrote:
> Hi
>
> I also am missing
Hi
I also am missing the lockdir setting. In the intranet Home/About
Koha/System Information
"Warnings regarding the system configuration":
XML configuration file
Warning:
You are missing the entry in your koha-conf.xml file. Please
add it, pointing to your Koha instance's lock dir.
I
Hello Koha world,
I wanted to share with you the timeline for the 21.05 major release:
* May 1st - "Soft" feature freeze, nothing big or with high risk of
side-effects will be included into the final release if not marked as
Passed QA
* May 4-7 - "Hard" feature freeze, nothing considered as an
9 matches
Mail list logo
