Re: [Koha-devel] oom-killer / Out of memory: Killed process 1026641 (/usr/share/koha)

2025-03-11 Thread David Cook via Koha-devel
I just had a Koha OOM killed on a small server the other day, so I feel your pain. When you startup Starman, it won't be using very much memory, but the memory usage will grow with the more requests it serves. Part of that has to do with the loading of Perl modules needed by those new requests,

Re: [Koha-devel] oom-killer / Out of memory: Killed process 1026641 (/usr/share/koha)

2025-03-11 Thread David Cook via Koha-devel
HI Michael, That opac-search.pl log looks like a bot that is really stuck. That looks like it would yield an ever growing search query. Yeah, most bots don't honour robots.txt anymore it seems. Blocking bots that self-identify with user agent strings is certainly useful, but it wouldn't bloc

Re: [Koha-devel] oom-killer / Out of memory: Killed process 1026641 (/usr/share/koha)

2025-03-11 Thread Michael Kuhn via Koha-devel
Hi Michael Yesterday you wrote: > Memcached was the process requesting more memory, not necessary the > process using a lot of memory. > Looking through the logs you attached it seems Beam.smp (which I > believe is RabbitMQ), MariaDB, and Koha Plack are the top three memory > processes. rebuild

Re: [Koha-devel] oom-killer / Out of memory: Killed process 1026641 (/usr/share/koha)

2025-03-11 Thread Michael Kuhn via Koha-devel
Hi David Today you wrote: > I actually just discovered a bug with /cgi-bin/koha/patroncards/ > create-pdf.pl which I'll be working on fixing today which could cause > resource exhaustion. I had some Starman workers using obscene amounts > of memory and CPU, and it's because they got trapped in i