[GH-ISSUE #15979] issue: Sporadic "no running event loop" errors #33268

Closed
opened 2026-04-25 07:11:29 -05:00 by GiteaMirror · 11 comments
Owner

Originally created by @Ithanil on GitHub (Jul 24, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15979

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Git Clone

Open WebUI Version

0.6.18

Ollama Version (if applicable)

No response

Operating System

Debian 12

Browser (if applicable)

No response

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

No errors popping up.

Actual Behavior

Since upgrading from 0.6.15 to 0.6.18, I see new, sporadic errors messages popping up. They don't appear to correspond to any user-facing malfunction, as they relate to the execution of cleanup tasks, but nevertheless this is a seemingly new behavior that I want to report.

If anyone else sees similar logs or has more insight, please feel free to comment.

Steps to Reproduce

Multi-Replica setup with Redis Sentinel

Logs & Screenshots

Logs, cut&redacted:

2025-07-23 00:13:47.252 | WARNING  | open_webui.socket.main:periodic_usage_pool_cleanup:148 - Failed to acquire cleanup lock after retries. Skipping cleanup. - {}
......
Exception ignored in: <coroutine object cleanup_task at 0x7fe24f1ea890>
Traceback (most recent call last):
  File "/app/backend/open_webui/tasks.py", line 86, in cleanup_task
    await redis_cleanup_task(redis, task_id, id)
  File "/app/backend/open_webui/tasks.py", line 64, in redis_cleanup_task
    if (await pipe.scard(f"{REDIS_ITEM_TASKS_KEY}:{item_id}").execute())[-1] == 0:
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/client.py", line 1590, in execute
    conn = await self.connection_pool.get_connection()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/connection.py", line 1141, in get_connection
    await self.ensure_connection(connection)
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/connection.py", line 1174, in ensure_connection
    await connection.connect()
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/sentinel.py", line 60, in connect
    return await self.retry.call_with_retry(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/retry.py", line 71, in call_with_retry
    return await do()
           ^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/sentinel.py", line 50, in _connect_retry
    await self.connect_to(await self.connection_pool.get_master_address())
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/sentinel.py", line 40, in connect_to
    await super().connect()
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/connection.py", line 296, in connect
    await self.connect_check_health(check_health=True)
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/connection.py", line 317, in connect_check_health
    await self.on_connect_check_health(check_health=check_health)
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/connection.py", line 458, in on_connect_check_health
    await self.read_response()
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/sentinel.py", line 74, in read_response
    return await super().read_response(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/connection.py", line 614, in read_response
    await self.disconnect(nowait=True)
  File "/usr/local/lib/python3.11/site-packages/redis/asyncio/connection.py", line 469, in disconnect
    async with async_timeout(self.socket_connect_timeout):
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/asyncio/timeouts.py", line 145, in timeout
    loop = events.get_running_loop()
           ^^^^^^^^^^^^^^^^^^^^^^^^^
RuntimeError: no running event loop

......
2025-07-23 00:16:59.297 | INFO     | open_webui.routers.openai:get_all_models:392 - get_all_models() - {}
2025-07-23 00:16:59.306 | INFO     | open_webui.config:__getattr__:260 - Updated OPENAI_API_BASE_URLS from Redis: ['REDACTED'] - {}
2025-07-23 00:16:59.311 | INFO     | open_webui.config:__getattr__:260 - Updated OPENAI_API_KEYS from Redis: ['REDACTED'] - {}
2025-07-23 00:16:59.318 | INFO     | open_webui.config:__getattr__:260 - Updated OPENAI_API_CONFIGS from Redis: {'0': {}} - {}
2025-07-23 00:16:59.407 | INFO     | open_webui.utils.plugin:install_frontmatter_requirements:241 - No requirements found in frontmatter. - {}
2025-07-23 00:16:59.409 | INFO     | open_webui.utils.plugin:load_function_module_by_id:147 - Loaded module: function_reasoning_toggle - {}
2025-07-23 00:17:03.800 | INFO     | open_webui.config:__getattr__:260 - Updated ENABLE_DIRECT_CONNECTIONS from Redis: False - {}
2025-07-23 00:17:03.808 | INFO     | open_webui.config:__getattr__:260 - Updated ENABLE_NOTES from Redis: False - {}
2025-07-23 00:17:03.873 | INFO     | open_webui.config:__getattr__:260 - Updated FILE_MAX_COUNT from Redis: 5 - {}

......

2025-07-23 00:17:46.462 | INFO     | open_webui.routers.openai:get_all_models:392 - get_all_models() - {}
2025-07-23 00:17:53.347 | INFO     | open_webui.config:save:202 - Saving 'TASK_MODEL' to the database - {}
2025-07-23 00:17:53.356 | INFO     | open_webui.config:save:202 - Saving 'TASK_MODEL_EXTERNAL' to the database - {}
2025-07-23 00:17:53.365 | INFO     | open_webui.config:save:202 - Saving 'ENABLE_TITLE_GENERATION' to the database - {}
2025-07-23 00:17:53.372 | INFO     | open_webui.config:save:202 - Saving 'TITLE_GENERATION_PROMPT_TEMPLATE' to the database - {}
2025-07-23 00:17:53.379 | INFO     | open_webui.config:save:202 - Saving 'ENABLE_FOLLOW_UP_GENERATION' to the database - {}
2025-07-23 00:17:53.385 | INFO     | open_webui.config:save:202 - Saving 'FOLLOW_UP_GENERATION_PROMPT_TEMPLATE' to the database - {}
2025-07-23 00:17:53.392 | INFO     | open_webui.config:save:202 - Saving 'IMAGE_PROMPT_GENERATION_PROMPT_TEMPLATE' to the database - {}
2025-07-23 00:17:53.399 | INFO     | open_webui.config:save:202 - Saving 'ENABLE_AUTOCOMPLETE_GENERATION' to the database - {}
2025-07-23 00:17:53.407 | INFO     | open_webui.config:save:202 - Saving 'AUTOCOMPLETE_GENERATION_INPUT_MAX_LENGTH' to the database - {}
2025-07-23 00:17:53.413 | INFO     | open_webui.config:save:202 - Saving 'TAGS_GENERATION_PROMPT_TEMPLATE' to the database - {}
2025-07-23 00:17:53.419 | INFO     | open_webui.config:save:202 - Saving 'ENABLE_TAGS_GENERATION' to the database - {}
2025-07-23 00:17:53.427 | INFO     | open_webui.config:save:202 - Saving 'ENABLE_SEARCH_QUERY_GENERATION' to the database - {}
2025-07-23 00:17:53.434 | INFO     | open_webui.config:save:202 - Saving 'ENABLE_RETRIEVAL_QUERY_GENERATION' to the database - {}
2025-07-23 00:17:53.440 | INFO     | open_webui.config:save:202 - Saving 'QUERY_GENERATION_PROMPT_TEMPLATE' to the database - {}
2025-07-23 00:17:53.446 | INFO     | open_webui.config:save:202 - Saving 'TOOLS_FUNCTION_CALLING_PROMPT_TEMPLATE' to the database - {}
......
2025-07-23 00:18:01.619 | INFO     | open_webui.config:__getattr__:260 - Updated ENABLE_BASE_MODELS_CACHE from Redis: True - {}
2025-07-23 00:18:01.629 | INFO     | open_webui.routers.openai:get_all_models:392 - get_all_models() - {}

Additional Information

Just want to understand what could be the cause or what has changed here.

Originally created by @Ithanil on GitHub (Jul 24, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/15979 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Git Clone ### Open WebUI Version 0.6.18 ### Ollama Version (if applicable) _No response_ ### Operating System Debian 12 ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior No errors popping up. ### Actual Behavior Since upgrading from 0.6.15 to 0.6.18, I see **new**, _sporadic_ errors messages popping up. They don't appear to correspond to any user-facing malfunction, as they relate to the execution of cleanup tasks, but nevertheless this is a seemingly new behavior that I want to report. If anyone else sees similar logs or has more insight, please feel free to comment. ### Steps to Reproduce Multi-Replica setup with Redis Sentinel ### Logs & Screenshots Logs, cut&redacted: ``` 2025-07-23 00:13:47.252 | WARNING | open_webui.socket.main:periodic_usage_pool_cleanup:148 - Failed to acquire cleanup lock after retries. Skipping cleanup. - {} ...... Exception ignored in: <coroutine object cleanup_task at 0x7fe24f1ea890> Traceback (most recent call last): File "/app/backend/open_webui/tasks.py", line 86, in cleanup_task await redis_cleanup_task(redis, task_id, id) File "/app/backend/open_webui/tasks.py", line 64, in redis_cleanup_task if (await pipe.scard(f"{REDIS_ITEM_TASKS_KEY}:{item_id}").execute())[-1] == 0: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/redis/asyncio/client.py", line 1590, in execute conn = await self.connection_pool.get_connection() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/redis/asyncio/connection.py", line 1141, in get_connection await self.ensure_connection(connection) File "/usr/local/lib/python3.11/site-packages/redis/asyncio/connection.py", line 1174, in ensure_connection await connection.connect() File "/usr/local/lib/python3.11/site-packages/redis/asyncio/sentinel.py", line 60, in connect return await self.retry.call_with_retry( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/redis/asyncio/retry.py", line 71, in call_with_retry return await do() ^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/redis/asyncio/sentinel.py", line 50, in _connect_retry await self.connect_to(await self.connection_pool.get_master_address()) File "/usr/local/lib/python3.11/site-packages/redis/asyncio/sentinel.py", line 40, in connect_to await super().connect() File "/usr/local/lib/python3.11/site-packages/redis/asyncio/connection.py", line 296, in connect await self.connect_check_health(check_health=True) File "/usr/local/lib/python3.11/site-packages/redis/asyncio/connection.py", line 317, in connect_check_health await self.on_connect_check_health(check_health=check_health) File "/usr/local/lib/python3.11/site-packages/redis/asyncio/connection.py", line 458, in on_connect_check_health await self.read_response() File "/usr/local/lib/python3.11/site-packages/redis/asyncio/sentinel.py", line 74, in read_response return await super().read_response( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/redis/asyncio/connection.py", line 614, in read_response await self.disconnect(nowait=True) File "/usr/local/lib/python3.11/site-packages/redis/asyncio/connection.py", line 469, in disconnect async with async_timeout(self.socket_connect_timeout): ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/asyncio/timeouts.py", line 145, in timeout loop = events.get_running_loop() ^^^^^^^^^^^^^^^^^^^^^^^^^ RuntimeError: no running event loop ...... 2025-07-23 00:16:59.297 | INFO | open_webui.routers.openai:get_all_models:392 - get_all_models() - {} 2025-07-23 00:16:59.306 | INFO | open_webui.config:__getattr__:260 - Updated OPENAI_API_BASE_URLS from Redis: ['REDACTED'] - {} 2025-07-23 00:16:59.311 | INFO | open_webui.config:__getattr__:260 - Updated OPENAI_API_KEYS from Redis: ['REDACTED'] - {} 2025-07-23 00:16:59.318 | INFO | open_webui.config:__getattr__:260 - Updated OPENAI_API_CONFIGS from Redis: {'0': {}} - {} 2025-07-23 00:16:59.407 | INFO | open_webui.utils.plugin:install_frontmatter_requirements:241 - No requirements found in frontmatter. - {} 2025-07-23 00:16:59.409 | INFO | open_webui.utils.plugin:load_function_module_by_id:147 - Loaded module: function_reasoning_toggle - {} 2025-07-23 00:17:03.800 | INFO | open_webui.config:__getattr__:260 - Updated ENABLE_DIRECT_CONNECTIONS from Redis: False - {} 2025-07-23 00:17:03.808 | INFO | open_webui.config:__getattr__:260 - Updated ENABLE_NOTES from Redis: False - {} 2025-07-23 00:17:03.873 | INFO | open_webui.config:__getattr__:260 - Updated FILE_MAX_COUNT from Redis: 5 - {} ...... 2025-07-23 00:17:46.462 | INFO | open_webui.routers.openai:get_all_models:392 - get_all_models() - {} 2025-07-23 00:17:53.347 | INFO | open_webui.config:save:202 - Saving 'TASK_MODEL' to the database - {} 2025-07-23 00:17:53.356 | INFO | open_webui.config:save:202 - Saving 'TASK_MODEL_EXTERNAL' to the database - {} 2025-07-23 00:17:53.365 | INFO | open_webui.config:save:202 - Saving 'ENABLE_TITLE_GENERATION' to the database - {} 2025-07-23 00:17:53.372 | INFO | open_webui.config:save:202 - Saving 'TITLE_GENERATION_PROMPT_TEMPLATE' to the database - {} 2025-07-23 00:17:53.379 | INFO | open_webui.config:save:202 - Saving 'ENABLE_FOLLOW_UP_GENERATION' to the database - {} 2025-07-23 00:17:53.385 | INFO | open_webui.config:save:202 - Saving 'FOLLOW_UP_GENERATION_PROMPT_TEMPLATE' to the database - {} 2025-07-23 00:17:53.392 | INFO | open_webui.config:save:202 - Saving 'IMAGE_PROMPT_GENERATION_PROMPT_TEMPLATE' to the database - {} 2025-07-23 00:17:53.399 | INFO | open_webui.config:save:202 - Saving 'ENABLE_AUTOCOMPLETE_GENERATION' to the database - {} 2025-07-23 00:17:53.407 | INFO | open_webui.config:save:202 - Saving 'AUTOCOMPLETE_GENERATION_INPUT_MAX_LENGTH' to the database - {} 2025-07-23 00:17:53.413 | INFO | open_webui.config:save:202 - Saving 'TAGS_GENERATION_PROMPT_TEMPLATE' to the database - {} 2025-07-23 00:17:53.419 | INFO | open_webui.config:save:202 - Saving 'ENABLE_TAGS_GENERATION' to the database - {} 2025-07-23 00:17:53.427 | INFO | open_webui.config:save:202 - Saving 'ENABLE_SEARCH_QUERY_GENERATION' to the database - {} 2025-07-23 00:17:53.434 | INFO | open_webui.config:save:202 - Saving 'ENABLE_RETRIEVAL_QUERY_GENERATION' to the database - {} 2025-07-23 00:17:53.440 | INFO | open_webui.config:save:202 - Saving 'QUERY_GENERATION_PROMPT_TEMPLATE' to the database - {} 2025-07-23 00:17:53.446 | INFO | open_webui.config:save:202 - Saving 'TOOLS_FUNCTION_CALLING_PROMPT_TEMPLATE' to the database - {} ...... 2025-07-23 00:18:01.619 | INFO | open_webui.config:__getattr__:260 - Updated ENABLE_BASE_MODELS_CACHE from Redis: True - {} 2025-07-23 00:18:01.629 | INFO | open_webui.routers.openai:get_all_models:392 - get_all_models() - {} ``` ### Additional Information Just want to understand what could be the cause or what has changed here.
GiteaMirror added the bug label 2026-04-25 07:11:29 -05:00
Author
Owner

@rgaricano commented on GitHub (Jul 24, 2025):

It seem that the cause is a timeout trying to connect to redis, and a uncached exception of the call:
5fbfe2bdca/backend/open_webui/tasks.py (L86)

maybe you can find more info in redis logs.
(I didn't saw that errors in my end)

<!-- gh-comment-id:3112728905 --> @rgaricano commented on GitHub (Jul 24, 2025): It seem that the cause is a timeout trying to connect to redis, and a uncached exception of the call: https://github.com/open-webui/open-webui/blob/5fbfe2bdcadf5f157926f6551891e4dc0802b9f3/backend/open_webui/tasks.py#L86 maybe you can find more info in redis logs. (I didn't saw that errors in my end)
Author
Owner

@Ithanil commented on GitHub (Jul 24, 2025):

Yes, might be there was a timeout due to lost packets. Redis was running fine.

I was kinda triggered by the "No Running event loop" and know there has been a major change in how Redis Sentinel connections are handled (https://github.com/open-webui/open-webui/pull/15718), plus refactoring in the tasks code. So I thought I'd better bring this up to be sure.

<!-- gh-comment-id:3112756906 --> @Ithanil commented on GitHub (Jul 24, 2025): Yes, might be there was a timeout due to lost packets. Redis was running fine. I was kinda triggered by the "No Running event loop" and know there has been a major change in how Redis Sentinel connections are handled (https://github.com/open-webui/open-webui/pull/15718), plus refactoring in the tasks code. So I thought I'd better bring this up to be sure.
Author
Owner

@tjbck commented on GitHub (Jul 24, 2025):

@sihyeonn

<!-- gh-comment-id:3114497484 --> @tjbck commented on GitHub (Jul 24, 2025): @sihyeonn
Author
Owner

@sihyeonn commented on GitHub (Jul 24, 2025):

Thank you for your @tjbck mentions. I'll check it as soon as possible!

<!-- gh-comment-id:3114876017 --> @sihyeonn commented on GitHub (Jul 24, 2025): Thank you for your @tjbck mentions. I'll check it as soon as possible!
Author
Owner

@sihyeonn commented on GitHub (Jul 25, 2025):

@Ithanil Hi, thank you for reporting this issue!

Just to confirm — are you referring to the logs appearing during the shutdown process?
Have you observed shutdowns occurring frequently or under specific conditions?

Let us know if you can share more details.

<!-- gh-comment-id:3116519843 --> @sihyeonn commented on GitHub (Jul 25, 2025): @Ithanil Hi, thank you for reporting this issue! Just to confirm — are you referring to the logs appearing during the shutdown process? Have you observed shutdowns occurring frequently or under specific conditions? Let us know if you can share more details.
Author
Owner

@Ithanil commented on GitHub (Jul 25, 2025):

Hi @sihyeonn, thanks looking into this. To my understanding, there was no shutdown, the container kept running fine, just as was the Redis. I just reported these logs because they appeared unusual to me.

<!-- gh-comment-id:3116548817 --> @Ithanil commented on GitHub (Jul 25, 2025): Hi @sihyeonn, thanks looking into this. To my understanding, there was no shutdown, the container kept running fine, just as was the Redis. I just reported these logs because they appeared unusual to me.
Author
Owner

@rgaricano commented on GitHub (Jul 25, 2025):

could it be due because sentinel isn't installed/configurated and there isn't a master?
redis-cli -p 6379

sentinel monitor

<!-- gh-comment-id:3116730907 --> @rgaricano commented on GitHub (Jul 25, 2025): could it be due because sentinel isn't installed/configurated and there isn't a master? `redis-cli -p 6379` >` sentinel monitor`
Author
Owner

@Ithanil commented on GitHub (Jul 25, 2025):

@Ithanil No, we are running with Redis Sentinel for at least 4 months now (and IMO failover was working perfectly fine even before https://github.com/open-webui/open-webui/pull/15718, as it should be per 67ab74d705/redis/sentinel.py (L367)). As I said, there is no really an issue except for some unusual error messages related to this cleanup task popping up like once per day. So if noone else sees anything similar, it might be just coincidence.

<!-- gh-comment-id:3116747837 --> @Ithanil commented on GitHub (Jul 25, 2025): @Ithanil No, we are running with Redis Sentinel for at least 4 months now (and IMO failover was working perfectly fine even before https://github.com/open-webui/open-webui/pull/15718, as it should be per https://github.com/redis/redis-py/blob/67ab74d705b4c1d00d600c500596af7a68abfd56/redis/sentinel.py#L367). As I said, there is no really an issue except for some unusual error messages related to this cleanup task popping up like once per day. So if noone else sees anything similar, it might be just coincidence.
Author
Owner

@rgaricano commented on GitHub (Jul 25, 2025):

Ok, sorry for the intervention, I just want to understand the process well.

<!-- gh-comment-id:3116993194 --> @rgaricano commented on GitHub (Jul 25, 2025): Ok, sorry for the intervention, I just want to understand the process well.
Author
Owner

@Ithanil commented on GitHub (Jul 25, 2025):

@Ithanil No, we are running with Redis Sentinel for at least 4 months now (and IMO failover was working perfectly fine even before #15718, as it should be per 67ab74d705/redis/sentinel.py (L367)). As I said, there is no really an issue except for some unusual error messages related to this cleanup task popping up like once per day. So if noone else sees anything similar, it might be just coincidence.

That said, the error did appear again few moments ago so I'm still leaning towards some kind of regression between 0.6.15 and 0.6.18

<!-- gh-comment-id:3117109885 --> @Ithanil commented on GitHub (Jul 25, 2025): > [@Ithanil](https://github.com/Ithanil) No, we are running with Redis Sentinel for at least 4 months now (and IMO failover was working perfectly fine even before [#15718](https://github.com/open-webui/open-webui/pull/15718), as it should be per https://github.com/redis/redis-py/blob/67ab74d705b4c1d00d600c500596af7a68abfd56/redis/sentinel.py#L367). As I said, there is no really an issue except for some unusual error messages related to this cleanup task popping up like once per day. So if noone else sees anything similar, it might be just coincidence. That said, the error *did* appear again few moments ago so I'm still leaning towards some kind of regression between 0.6.15 and 0.6.18
Author
Owner

@Ithanil commented on GitHub (Jul 29, 2025):

I think that hint is worth looking into: https://github.com/open-webui/open-webui/pull/16014#issuecomment-3127300738

<!-- gh-comment-id:3131481700 --> @Ithanil commented on GitHub (Jul 29, 2025): I think that hint is worth looking into: https://github.com/open-webui/open-webui/pull/16014#issuecomment-3127300738
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#33268