[Chandler] Setting QUEUE_CONNECTION to redis causes Chandler not working

[vnghia]

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github (I've searched it).
• I agree to follow Monica's Code of Conduct.

Bug description

Setting QUEUE_CONNECTION to redis causes Chandler not working. It seems that the job dispatched to the queues never get executed.

Steps to reproduce

1. Setting QUEUE_CONNECTION to redis.

Expected behavior

Without executing these jobs, Chandler is pretty unusable and missing a lot of things:

• Modules 🔔 Update on the project #6626 (comment).
• Currencies 🔔 Update on the project #6626 (comment).
• Default values for a lot of settings.
• Email sending. I am suspecting this is the cause of Monica Mailer no longer working, tries to force TLS? #6820 (comment)

I am expecting that these values are filled and email sending is working.

Environment

Your own self-hosted instance (v5 a.k.a chandler version or main branch)

Version of Monica

cddf7f9

Installation method

Docker image

Web server

None

Database engine version

PostgreSQL

Additional info

All three of my settings: CACHE_DRIVER, QUEUE_CONNECTION and SESSION_DRIVER are set to redis but the other two are working fine. I have to change QUEUE_CONNECTION to sync to get Chandler working (including sending email notification).

/cc @stephenwade

[mlaradji]

I confirm that this also happens when the database used is MariaDB. As @vnghia mentioned, setting QUEUE_CONNECTION to sync resolves the issue.

[djaiss]

This is concerning. I don't try to use Chandler with Redis, I always use the database driver, and it's working well.

@asbiin do you happen to use Redis locally?

[vnghia]

Yes I use Redis locally with docker-compose. One thing I observe when Redis is used that the thing like default template or so is not added.

[asbiin]

I do use redis localy yes (see the recent sail feature), and I don't have any issue with it so far....

In any case if there is an issue, it's more likely a Laravel issue, as we have nothing specific there. Don't hesitate to open an issue on Laravel.