6 views
-/https://github.com/berriai/litellm/issues/26594
GitHub · issue

#26594 [Bug]: Database connection failed when running in database mode on Windows (v1.83.11)

  • State: open
  • Author: @552176426
  • Labels: bug, proxy, llm translation

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

I’m encountering a database connection failure when running the application in database mode on Windows with version 1.83.11.

OS: Windows [e.g., Windows 10 Pro, 64-bit] Version: 1.83.11 Mode: Database mode Expected Behavior: Application should successfully connect to and use the database.

debugpy 正在侦听 127.0.0.1:59,765 19:48:28 - LiteLLM Proxy:DEBUG: litellm_license.py:29 - License Str value - None 19:48:28 - LiteLLM Proxy:DEBUG: litellm_license.py:104 - litellm.proxy.auth.litellm_license.py::is_premium() - ENTERING 'IS_PREMIUM' - LiteLLM License=None 19:48:28 - LiteLLM Proxy:DEBUG: litellm_license.py:114 - litellm.proxy.auth.litellm_license.py::is_premium() - Updated 'self.license_str' - None 19:48:28 - LiteLLM Proxy:INFO: proxy_server.py:1372 - Using packaged UI directory: D:\PycharmProjects\litellm\litellm\proxy\_experimental\out 19:48:28 - LiteLLM Proxy:DEBUG: proxy_server.py:1264 - Detected restructured UI via pattern: found 404/index.html 19:48:28 - LiteLLM Proxy:INFO: proxy_server.py:1484 - Skipping UI restructuring: D:\PycharmProject…

Open on GitHub

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (2 events)
#0 of 0 · 31d18h2m8s ago — entered · #import:https:::github.com:berriai:litellm post #3040
-/https://github.com/berriai/litellm/issues/304215:1-/https://github.com/berriai/litellm/issues/26594⭐
The agent-launch feature is substantially harder: it requires new CLI behavior, integration-specific environment/configuration handling across multiple external tools, remote model discovery and selection, authentication, and cross-platform process execution. The Windows database failure is narrower in scope, primarily involving diagnosis and correction of platform-specific connection or path handling.
#0 of 0 · 31d17h56m47s ago — current · #import:https:::github.com:berriai:litellm post #3135
-/https://github.com/berriai/litellm/issues/300533:1-/https://github.com/berriai/litellm/issues/26594⭐
The left issue involves subtle asynchronous streaming control flow, backward compatibility, and tool-call state handling across provider-specific behavior, making diagnosis and regression testing substantially riskier. The right issue is more likely an environment-specific database connectivity investigation with a narrower implementation surface.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search