Did you have a look at worker-*.log? Nothing useful there? You can try to send SIGCHLD to the parent to kill the zombie. Le mar. 18 avr. 2023 à 22:09, Cindy Murdock Ames <cmurdock@ccfls.org> a écrit :
A few other things I've noticed:
- Sometimes the zombie processes will go away on their own, sometimes it seems when you retry the MARC import or whatever it was that failed. This one is really weird to me as in all my years as a sysadmin I thought it was not possible for zombie processes to go away without a reboot. But maybe that's changed and now zombies can rise from the dead. Lol.
- In looking at the jobs list in Koha, it seems that Holds queue updates are especially prone to getting stuck at a progress of null/1.
- If you reattempt a job that is stuck (ie, reattempting a MARC file upload or what not) it will often succeed. The original failed job remains with a progress of null.
c. ----------------------------------------------------------- Cindy Murdock Ames IT Services Director Meadville Public Library | CCFLS https://meadvillelibrary.org | https://ccfls.org
Please report tech support issues in Mantis: https://mantis.ccfls.org
On Tue, Apr 18, 2023 at 3:55 PM Cindy Murdock Ames <cmurdock@ccfls.org> wrote:
Yes, it's 22.11.04, package version.
----------------------------------------------------------- Cindy Murdock Ames IT Services Director Meadville Public Library | CCFLS https://meadvillelibrary.org | https://ccfls.org
On Tue, Apr 18, 2023 at 2:59 PM Jonathan Druart <jonathan.druart@bugs.koha-community.org> wrote:
Hi Cindy, Which exact version of Koha 22.11.xx? It should be the latest one. Regards, Jonathan
Le mar. 18 avr. 2023 à 19:13, Cindy Murdock Ames <cmurdock@ccfls.org> a écrit :
Hi all,
A couple weekends ago I upgraded our Koha instance from 22.05 to 22.11, and I'm having trouble with the background_jobs processes becoming zombies after a very short amount of time, necessitating a reboot. I suspect it's a misconfiguration on my part, so if someone can shed some light I'd really appreciate it!
The first symptom was our MARC imports getting stuck at "import queued", and after some digging (and thanks to the thread in this list with the subject of "Background job / Staging MARC import stuck at 0%" I found I was entirely missing the <message_broker> section in our config, so I added this:
<message_broker> <hostname>localhost</hostname> <port>61613</port> <username>guest</username> <password>guest</password> <vhost></vhost> </message_broker>
Which seemed to resolve it, but now I find that the background_jobs processes are going zombie after processing only a few jobs. Here's some info from the rabbitmq log after restarting the server:
=INFO REPORT==== 18-Apr-2023::12:23:46 === node : rabbit@ccflskoha home dir : /var/lib/rabbitmq config file(s) : /etc/rabbitmq/rabbitmq.config (not found) cookie hash : ojvkUE6eUtku7kHlx3uiFg== log : /var/log/rabbitmq/rabbit@ccflskoha.log sasl log : /var/log/rabbitmq/rabbit@ccflskoha-sasl.log database dir : /var/lib/rabbitmq/mnesia/rabbit@ccflskoha
Is it problematic that /etc/rabbitmq/rabbitmq.config is missing? Anything else I should be looking at? We're running on Ubuntu SE 18.04 if that is helpful.
Thanks much! Cindy
----------------------------------------------------------- Cindy Murdock Ames IT Services Director Meadville Public Library | CCFLS https://meadvillelibrary.org | https://ccfls.org _______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha