-
Notifications
You must be signed in to change notification settings - Fork 56
Worker debug log? #258
Comments
@MarcinOrlowski Nope, I don't think there is such a thing. What storage adapter are you using? And: can you still see your job in the queue, or is it removed after you start the worker? Hard to help without more context! |
I use DB storage and I do check that enqueued jobs are indeed correctly stored into DB. I wrote code to monitor queues and I dump the content of the queue etc. Yet, the execution seems to just do nothing and jobs are gone after that. I got all the code in |
Weird @MarcinOrlowski! Not sure how I can help though without having some code to act on. It is a hint too that the onboarding of this repo may be too difficult. But nothing I can do currently to remedy that. |
(As there's no "Discussion" section for this repo, let me follow-up in here to avoid creating numerous tickets) I checked query log of my deployment and noticed massive bursts of PHP 8.1.17
|
The queue is simply trying to find a new job in the database. Because you schedule jobs in the future, it queries using a timestamp (the date should be of today). Perfectly normal ✔️ . |
I am facing odd issue running the SLM with Doctrine ORM, where jobs are enqueued successfully yet they seem not to execute. The worker seems to be running though as jobs are gone from the queue but their work is not done. I planted some logging into the jobs'
execute()
and this is not logged. Is there any approach/debug mode whatever I could try to exercise to debug this problem?The text was updated successfully, but these errors were encountered: