-
-
Notifications
You must be signed in to change notification settings - Fork 12.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] 每隔一段时间服务器对所有涉及trpc的请求都无响应, 直到客户端超时 #6663
Labels
🐛 Bug
Something isn't working | 缺陷
Comments
Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible. |
Anyone could help?🥺 |
server logs
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
📦 Platform
Self hosting Docker
📦 Deploymenet mode
server db(lobe-chat-database image)
📌 Version
1.66.6
💻 Operating System
Other Linux, Ubuntu
🌐 Browser
Chrome
🐛 Bug Description
服务器运行大约30分钟后,TRPC请求持续失败并出现超时错误(HTTP 524)。服务器重启后会暂时恢复正常,但在类似时长后再次遇到相同问题。
如果在Chrome开发者工具中使用GET请求,服务器无响应,等待直到超时,然后返回524响应。
All trpc requests failed with timeout 524 responses.
The server could work after restart, but only for a while like 30 mins, and then the trpc can not work any more.
📷 Recurrence Steps
TRPC requests to the server consistently fail with a timeout error (HTTP 524) after the server has been running for approximately 30 minutes. The server resumes normal operation temporarily after a restart but encounters the same issue again after a similar duration.
if use the GET request from chrome dev tools, the server will freeze, wait until timeout, and give a 524 response
if use POST, it server could immediately return error.
curl -X POST "http://lobe-chat:3210/trpc/lambda/agent.getAgentConfig,aiProvider.getAiProviderRuntimeState,user.getUserState"
🚦 Expected Behavior
no error, or return error response immediately
📝 Additional Information
api gateway: nginx
upgrade to latest lobe-chat-database images seems still suffer from the same issue
The text was updated successfully, but these errors were encountered: