Redis sessions, cache & queues

GreXXL

ZEROPOINTBRUH can you please follow out troubleshooting guide. We will need you php flarum info output and the error within the logfile located in storage/logs.

forever

Already processed

luceos

forever check storage/logs for the error or enable debug.

forever

Already processed

luceos

forever seems your redis server isn't running or accessible.

forever

Already processed

luceos

forever 0.0.0.0 should allow access from any host that has access to the redis host. If connections still fail then either the host that runs Flarum is not on the same host as redis, or the host that runs Flarum has no access to the host that runs redis.

forever

Already processed

datitisev

forever Is the error in storage/logs the same as the one you sent a screenshot of earlier (the inability to connect to redis)?

TOWUK_ru

i install it with redis-server, have redis all schedules, but extension manager have infinity loading (2+ hours pending)

Redis server v=7.0.15 sha=00000000:0 malloc=jemalloc-5.3.0 bits=64 build=d81b8ff71cfb150e
redis conf:
bind * -::*
protected-mode no

rui5man

Does this plugin conflict with Scout Search? When I set up Redis sessions, the meisearch configured for Scout Search will not work properly. After uninstalling the plugin, it can work normally again. Is it a problem that I set up?

luceos

rui5man not that I know of.

clarkwinkelmann

rui5man the problem could be related to the use of an async queue and not specifically Redis. Are you sure the queue worker is running? If this extension has an option to only use Redis for cache and not for queue, could you check if there is a problem in that configuration?

rui5man

clarkwinkelmann Thank you for your help. It is true that the problem is with asynchronous queues. I will only use Redis for caching and not for queues. The meisearch configured for Scout Search will now work properly. Am I not configuring the queue correctly, or can it only run in this way?

clarkwinkelmann

rui5man Scout should work with asynchronous queues as well. Make sure you follow the "Queue" instructions in the README file of the Redis extension (I see it's also in the first post of this discussion) to configure the queue worker

« Previous Page