redis errors after updating Open WebUI from 0.9.6 to 0.10.1
-
I've just updated my Open WebUI to 0.10.1 and the log is being spammed with this:
Jul 02 11:07:06 Cannot receive from redis... retrying in 1 secs Jul 02 11:07:06 2026-07-02 09:07:06.757 | ERROR | socketio.async_redis_manager:_redis_listen_with_retries:159 - Cannot receive from redis... retrying in 1 secs Jul 02 11:07:12 Cannot receive from redis... retrying in 1 secs Jul 02 11:07:12 2026-07-02 09:07:12.770 | ERROR | socketio.async_redis_manager:_redis_listen_with_retries:159 - Cannot receive from redis... retrying in 1 secs Jul 02 11:07:18 Cannot receive from redis... retrying in 1 secsNot sure what changed, since the redis config wasn't touched or if this has a negative impact, just wanted to let you know.
-
Yep, redis is up and running (also says so in the services tab):
Jul 02 12:56:10 13:C 02 Jul 2026 10:56:10.580 * Configuration loaded Jul 02 12:56:10 13:C 02 Jul 2026 10:56:10.580 * Redis version=8.4.0, bits=64, commit=00000000, modified=1, pid=13, just started Jul 02 12:56:10 13:C 02 Jul 2026 10:56:10.580 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.580 * Increased maximum number of open files to 10032 (it was originally set to 1024). Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.580 * monotonic clock: POSIX clock_gettime Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.581 # Failed to write PID file: Permission denied Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.581 * Loading RDB produced by version 8.4.0 Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.581 * RDB age 5188 seconds Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.581 * RDB memory usage when created 1.08 Mb Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.581 * Running mode=standalone, port=6379. Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.581 * Server initialized Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.582 * DB loaded from disk: 0.001 seconds Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.582 * Done loading RDB, keys loaded: 3, keys expired: 1. Jul 02 12:56:10 13:M 02 Jul 2026 10:56:10.582 * Ready to accept connections tcp Jul 02 12:56:10 2026-07-02 10:56:10,573 INFO spawned: 'redis' with pid 13 Jul 02 12:56:10 2026-07-02 10:56:10,574 INFO spawned: 'redis-service' with pid 14 Jul 02 12:56:10 Redis service endpoint listening on http://:::3000 Jul 02 12:56:11 2026-07-02 10:56:11,645 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Jul 02 12:56:11 2026-07-02 10:56:11,645 INFO success: redis-service entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)The errors only start to show up, when you access the site.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login