https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31561
Björn Nylén <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Björn Nylén <[email protected]> --- We're also seeing jobs stuck at NEW. From the log it seems the worker is getting the job from the queue before it is avaliable in the db. (We're on an external db-cluster wich may compound it) The job will be "ack"ed in the queue even if the process call (->process on undef) fails in the worker child. We did a hack that checks if the job exists in the db and requeues the job in the queue when not. Risk of ininite loop if it never shows up though. Not sure how big though, not live yet. Doesn't sound like Magnus' issue thou as I don't think a restart of rabbitmq would solve this as the job is already "ack"ed there -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
