Any ideas why backend_clean_cache cron job get's stuck every night? Is there a way to debug what causes it to get stuck?
Same for me. v2.3.4-p2
Did you find a reason why this occurs by any chance? Will report back here if I resolve it.
I managed to fix this by adding this to env.php:
'queue' => [
'consumers_wait_for_messages' => 0
This was suggested somewhere. Mysteriously this only worked for a while and then the problem appeared again and I have not yet been able to fix this.
OK, think I have this sorted, in my instance anyway.
After a forced server reboot, looks like a cron job wasn't registered as completed, leaving it in limbo.
Running the following command in SSH showed a process running which was days old, they should only be minutes, hours at most.
ps aux | grep -i cron
Kill the process and truncate the cron_schedule table.
kill -9 [PID]
Issue came back. Sunday night, same time as week previous.
It's a recognised problem and has apparently been resolved on v2.4.1 which doesn't help when you've just got all extensions working and stable on a 2.3 release......