[Bug] 每隔一段时间服务器对所有涉及trpc的请求都无响应, 直到客户端超时 #6775

sideef5ect · 2025-03-03T11:55:31Z

sideef5ect
Mar 3, 2025

📦 Platform

Self hosting Docker

📦 Deploymenet mode

server db(lobe-chat-database image)

📌 Version

1.66.4

💻 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

curl -X GET "http://<PLACEHOLDER_DOMAIN>:3210/trpc/lambda/agent.getAgentConfig,aiProvider.getAiProviderRuntimeState,user.getUserState?batch=1&input=%7B%220%22%3A%7B%22json%22%3A%7B%22sessionId%22%3A%22inbox%22%7D%7D%2C%221%22%3A%7B%22json%22%3A%7B%22isLogin%22%3Anull%7D%2C%22meta%22%3A%7B%22values%22%3A%7B%22isLogin%22%3A%5B%22undefined%22%5D%7D%7D%7D%2C%222%22%3A%7B%22json%22%3Anull%2C%22meta%22%3A%7B%22values%22%3A%5B%22undefined%22%5D%7D%7D%7D" \
-H "Accept: */*" \
-H "Accept-Encoding: gzip, deflate, br, zstd" \
-H "Accept-Language: en,zh;q=0.9" \
-H "Content-Type: application/json" \
-H "Cookie: __Host-authjs.csrf-token=<PLACEHOLDER_CSRF_TOKEN>; LOBE_LOCALE=en-US; LOBE_THEME_APPEARANCE=dark; __Secure-authjs.callback-url=https%3A%2F%2F<PLACEHOLDER_DOMAIN>%2Fchat; ory_kratos_session=<PLACEHOLDER_SESSION>; __Secure-authjs.session-token=<PLACEHOLDER_SESSION_TOKEN>" \
-H "DNT: 1" \
-H "Priority: u=1, i" \
-H "Referer: https://<PLACEHOLDER_DOMAIN>/" \
-H "Sec-CH-UA: \"Chromium\";v=\"133\", \"Not(A:Brand\";v=\"99\"" \
-H "Sec-CH-UA-Mobile: ?0" \
-H "Sec-CH-UA-Platform: \"macOS\"" \
-H "Sec-Fetch-Dest: empty" \
-H "Sec-Fetch-Mode: cors" \
-H "Sec-Fetch-Site: same-origin" \
-H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36" \
-H "X-Lobe-Chat-Auth: <PLACEHOLDER_AUTH_TOKEN>" -vvv

* Host lobe-chat:3210 was resolved.
* IPv6: (none)
* IPv4: 10.0.3.14, 10.0.3.20
*   Trying 10.0.3.14:3210...
* Connected to lobe-chat (10.0.3.14) port 3210
> GET /trpc/lambda/agent.getAgentConfig,aiProvider.getAiProviderRuntimeState,user.getUserState?batch=1&input=%7B%220%22%3A%7B%22json%22%3A%7B%22sessionId%22%3A%22inbox%22%7D%7D%2C%221%22%3A%7B%22json%22%3A%7B%22isLogin%22%3Anull%7D%2C%22meta%22%3A%7B%22values%22%3A%7B%22isLogin%22%3A%5B%22undefined%22%5D%7D%7D%7D%2C%222%22%3A%7B%22json%22%3Anull%2C%22meta%22%3A%7B%22values%22%3A%5B%22undefined%22%5D%7D%7D%7D HTTP/1.1
> Host: lobe-chat:3210
> Accept: */*
> Accept-Encoding: gzip, deflate, br, zstd
> Accept-Language: en,zh;q=0.9
> Content-Type: application/json
> Cookie: __Host-authjs.csrf-token=<PLACEHOLDER_CSRF_TOKEN>; LOBE_LOCALE=en-US; LOBE_THEME_APPEARANCE=dark; __Secure-authjs.callback-url=https%3A%2F%2F<PLACEHOLDER_DOMAIN>%2Fchat; ory_kratos_session=<PLACEHOLDER_SESSION>; __Secure-authjs.session-token=<PLACEHOLDER_SESSION_TOKEN>
> DNT: 1
> Priority: u=1, i
> Referer: https://<PLACEHOLDER_DOMAIN>/
> Sec-CH-UA: "Chromium";v="133", "Not(A:Brand";v="99"
> Sec-CH-UA-Mobile: ?0
> Sec-CH-UA-Platform: "macOS"
> Sec-Fetch-Dest: empty
> Sec-Fetch-Mode: cors
> Sec-Fetch-Site: same-origin
> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/133.0.0.0 Safari/537.36
> X-Lobe-Chat-Auth: <PLACEHOLDER_AUTH_TOKEN>
>

if use POST, it server could immediately return error.

curl -X POST "http://lobe-chat:3210/trpc/lambda/agent.getAgentConfig,aiProvider.getAiProviderRuntimeState,user.getUserState"

{"error":{"json":{"message":"Missing content-type header","code":-32015,"data":{"code":"UNSUPPORTED_MEDIA_TYPE","httpStatus":415}}}}

🚦 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

lobehubbot · 2025-03-03T11:55:43Z

lobehubbot
Mar 3, 2025
Maintainer

👀 @sideef5ect

Thank you for raising an issue. We will investigate into the matter and get back to you as soon as possible.
Please make sure you have given us as much context as possible.
非常感谢您提交 issue。我们会尽快调查此事，并尽快回复您。请确保您已经提供了尽可能多的背景信息。

0 replies

sideef5ect · 2025-03-04T04:11:00Z

sideef5ect
Mar 4, 2025
Author

Anyone could help?🥺

0 replies

sideef5ect · 2025-03-04T08:21:19Z

sideef5ect
Mar 4, 2025
Author

server logs

docker service logs lobe-chat
lobe-chat.1.tzfxhfqgspbo@node2    | 🌐 DNS Server: [ '127.0.0.11' ]
lobe-chat.1.tzfxhfqgspbo@node2    | -------------------------------------
lobe-chat.1.tzfxhfqgspbo@node2    | [Database] Start to migration...
lobe-chat.1.tzfxhfqgspbo@node2    | ✅ database migration pass.
lobe-chat.1.tzfxhfqgspbo@node2    | -------------------------------------
lobe-chat.1.tzfxhfqgspbo@node2    |    ▲ Next.js 15.2.0
lobe-chat.1.tzfxhfqgspbo@node2    |    - Local:        http://localhost:3210
lobe-chat.1.tzfxhfqgspbo@node2    |    - Network:      http://0.0.0.0:3210
lobe-chat.1.tzfxhfqgspbo@node2    |
lobe-chat.1.tzfxhfqgspbo@node2    |  ✓ Starting...
lobe-chat.1.tzfxhfqgspbo@node2    |  ✓ Ready in 39ms
lobe-chat.1.tzfxhfqgspbo@node2    | {
lobe-chat.1.tzfxhfqgspbo@node2    |   allowDangerousEmailAccountLinking: true,
lobe-chat.1.tzfxhfqgspbo@node2    |   clientId: undefined,
lobe-chat.1.tzfxhfqgspbo@node2    |   clientSecret: undefined,
lobe-chat.1.tzfxhfqgspbo@node2    |   platformType: 'WebsiteApp',
lobe-chat.1.tzfxhfqgspbo@node2    |   profile: [Function: profile]
lobe-chat.1.tzfxhfqgspbo@node2    | }
lobe-chat.1.tzfxhfqgspbo@node2    | {
lobe-chat.1.tzfxhfqgspbo@node2    |   allowDangerousEmailAccountLinking: true,
lobe-chat.1.tzfxhfqgspbo@node2    |   clientId: undefined,
lobe-chat.1.tzfxhfqgspbo@node2    |   clientSecret: undefined,
lobe-chat.1.tzfxhfqgspbo@node2    |   platformType: 'WebsiteApp',
lobe-chat.1.tzfxhfqgspbo@node2    |   profile: [Function: profile]
lobe-chat.1.tzfxhfqgspbo@node2    | }
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /chat -> http://127.0.0.1:3210/en-US__0__dark/chat
lobe-chat.1.tzfxhfqgspbo@node2    | (node:28) [DEP0060] DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead.
lobe-chat.1.tzfxhfqgspbo@node2    | (Use `node --trace-deprecation ...` to show where the warning was created)
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /files -> http://127.0.0.1:3210/en-US__0__dark/files
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /chat -> http://127.0.0.1:3210/en-US__0__dark/chat
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] / -> http://127.0.0.1:3210/en-US__0__dark
lobe-chat.1.tzfxhfqgspbo@node2    | {
lobe-chat.1.tzfxhfqgspbo@node2    |   allowDangerousEmailAccountLinking: true,
lobe-chat.1.tzfxhfqgspbo@node2    |   clientId: undefined,
lobe-chat.1.tzfxhfqgspbo@node2    |   clientSecret: undefined,
lobe-chat.1.tzfxhfqgspbo@node2    |   platformType: 'WebsiteApp',
lobe-chat.1.tzfxhfqgspbo@node2    |   profile: [Function: profile]
lobe-chat.1.tzfxhfqgspbo@node2    | }
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] / -> http://127.0.0.1:3210/en-US__0__dark
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /discover -> http://127.0.0.1:3210/en-US__0__dark/discover
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /chat -> http://127.0.0.1:3210/en-US__0__dark/chat
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /chat -> http://127.0.0.1:3210/en-US__0__dark/chat
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] / -> http://127.0.0.1:3210/en-US__0__dark
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /chat -> http://127.0.0.1:3210/en-US__0__dark/chat
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /files -> http://127.0.0.1:3210/en-US__0__dark/files
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /discover -> http://127.0.0.1:3210/en-US__0__dark/discover
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /discover/assistant/bad-language-helper -> http://127.0.0.1:3210/en-US__0__dark/discover/assistant/bad-language-helper
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /discover/assistant/crontab-generate -> http://127.0.0.1:3210/en-US__0__dark/discover/assistant/crontab-generate
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /discover/assistant/fate-researcher -> http://127.0.0.1:3210/en-US__0__dark/discover/assistant/fate-researcher
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /discover/assistant/xiao-zhi-french-translation-asst-v-1 -> http://127.0.0.1:3210/en-US__0__dark/discover/assistant/xiao-zhi-french-translation-asst-v-1
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /chat -> http://127.0.0.1:3210/en-US__0__dark/chat
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /discover -> http://127.0.0.1:3210/en-US__0__dark/discover
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /files -> http://127.0.0.1:3210/en-US__0__dark/files
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /chat -> http://127.0.0.1:3210/en-US__0__dark/chat
lobe-chat.1.tzfxhfqgspbo@node2    | [Error: aborted] { code: 'ECONNRESET' }
lobe-chat.1.tzfxhfqgspbo@node2    |  ⨯ uncaughtException:  [Error: aborted] { code: 'ECONNRESET' }
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /files -> http://127.0.0.1:3210/en-US__0__dark/files
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] /discover -> http://127.0.0.1:3210/en-US__0__dark/discover
lobe-chat.1.tzfxhfqgspbo@node2    | [rewrite] / -> http://127.0.0.1:3210/en-US__0__dark

0 replies

arvinxx · 2025-03-04T14:32:37Z

arvinxx
Mar 4, 2025
Maintainer

看下 AI 给出的回复是否有帮助：

问题概述

用户在自托管 Docker 环境下运行 LobeChat (版本 1.66.6)，遇到以下问题：

服务器运行约 30 分钟后，所有 tRPC 请求开始持续失败，出现 HTTP 524 超时错误
重启服务器后暂时恢复正常，但约 30 分钟后再次出现相同问题
GET 请求时服务器无响应，直到客户端超时
POST 请求能立即返回错误响应

可能的原因分析

1. 内存泄漏问题

最有可能的原因是 Node.js 应用中存在内存泄漏。这与超时设置有关的内存泄漏特别符合问题描述：

服务运行一段时间后才出现问题（约30分钟）
重启后临时恢复，但问题会再次出现
请求停滞不前直到超时

Node.js 中的 setTimeout 和超时处理机制是常见的内存泄漏源。每次创建新的超时处理器但没有正确清理时，会导致内存持续增长，最终导致服务无响应。

2. 连接池耗尽

tRPC 服务可能使用了数据库连接池或其他资源池，这些池在一段时间后被耗尽：

如果连接没有正确释放，可用连接会逐渐减少
当所有连接都被占用时，新请求会被阻塞直到超时
重启服务会重置连接池，暂时解决问题

3. Docker 资源限制

在 Docker 环境中，如果没有适当设置资源限制，容器可能会遇到资源瓶颈：

内存限制过低，导致应用在负载增加时无法分配足够内存
CPU 限制导致请求处理变慢，最终堆积并超时
Docker 的网络栈可能在高负载下出现问题

4. 数据库性能问题

使用 lobe-chat-database 镜像，可能存在数据库相关问题：

随着数据增长，查询性能下降
数据库连接管理不当，导致连接泄漏
数据库锁定或死锁问题导致请求堆积

5. Nginx 代理配置问题

从问题描述看出使用了 Nginx 作为 API 网关：

Nginx 超时设置可能不匹配后端服务需求
代理缓冲区配置不足
上游连接池配置不当

建议解决方案

监控内存使用：
- 使用 node --inspect 启动服务并通过 Chrome DevTools 分析内存使用
- 添加内存监控工具如 node-memwatch 或 clinic.js
检查连接池配置：
- 审查数据库连接池设置
- 确保连接正确关闭和释放
调整 Docker 资源限制：
- 增加容器内存限制
- 监控 CPU 使用率
- 使用 docker stats 命令监控容器资源使用情况
优化 Nginx 配置：
- 调整 proxy_read_timeout 和 proxy_connect_timeout
- 增加缓冲区大小
- 确保上游连接池配置合理
更新版本：
- 检查是否有更新的 LobeChat 版本解决了此问题
- 关注 GitHub issues 中类似问题的解决方案
日志分析：
- 开启详细日志记录
- 分析服务器日志，特别关注内存使用、垃圾回收事件和错误模式

这个问题很可能是由内存泄漏引起的，特别是与 tRPC 请求处理和超时机制相关的泄漏。建议优先检查内存使用情况并监控服务运行时的资源消耗。

0 replies

lobehubbot · 2025-03-04T14:32:49Z

lobehubbot
Mar 4, 2025
Maintainer

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

See if the responses given by AI are helpful:

Based on the content of GitHub issue #6663 and related search results, I will analyze the possible reasons for the tRPC request timeout error in LobeChat:

Problem Overview

The user runs LobeChat (version 1.66.6) in a self-hosted Docker environment and encounters the following problems:

After the server was running for about 30 minutes, all tRPC requests began to fail continuously, with an HTTP 524 timeout error
Restart the server temporarily and return to normal, but the same problem occurs again after about 30 minutes
The server is unresponsive when the GET requests until the client timed out
POST request can immediately return an error response

Possible Cause Analysis

1. Memory Leak Issues

The most likely reason is that there is a memory leak in the Node.js application. This memory leak related to the timeout setting is particularly consistent with the problem description:

The service only has problems after running for a period of time (about 30 minutes)
Recover temporarily after restart, but the problem will occur again
Requests stall until timeout

setTimeout and timeout handling mechanisms in Node.js are common sources of memory leaks. Every time a new timeout processor is created but not cleaned correctly, it causes the memory to continue to grow, ultimately causing the service to be unresponsive.

2. Connection pool exhausted

The tRPC service may use a database connection pool or other resource pool that is exhausted after a period of time:

If the connection is not released correctly, the available connections will gradually decrease
When all connections are occupied, new requests will be blocked until timeout
Restarting the service will reset the connection pool, temporarily solving the problem

3. Docker resource limitations

In a Docker environment, containers may experience resource bottlenecks if resource limits are not set properly:

Memory limit is too low, causing the application to be unable to allocate sufficient memory when the load increases
CPU limits cause request processing to slow down, eventually pile up and timeout
Docker's network stack may have problems under high load

4. Database performance issues

Using the lobe-chat-database image, there may be database-related issues:

Query performance declines as data grows
Improper database connection management, resulting in connection leakage
Database locking or deadlocking issues cause request accumulation

5. Nginx proxy configuration issues

From the problem description, it is shown that Nginx is used as the API gateway:

Nginx timeout settings may not match backend service requirements
Insufficient proxy buffer configuration
Improper configuration of upstream connection pool

Suggested Solutions

Monitoring memory usage:
- Start the service with node --inspect and analyze memory usage with Chrome DevTools
- Add memory monitoring tools such as node-memwatch or clinic.js
Check the connection pool configuration:
- Review database connection pool settings
- Make sure the connection is closed and released correctly
Adjust Docker resource limits:
- Increase container memory limit
- Monitor CPU usage
- Monitor container resource usage using the docker stats command
Optimize Nginx configuration:
- Adjust proxy_read_timeout and proxy_connect_timeout
- Increase buffer size
- Ensure the upstream connection pool is configured properly
Updated Version:
- Check if there is an updated version of LobeChat that resolves this issue
- Follow solutions to similar issues in GitHub issues
Log Analysis:
- Turn on detailed logging
- Analyze server logs, paying special attention to memory usage, garbage collection events and error patterns

This problem is likely caused by memory leaks, especially those related to tRPC request handling and timeout mechanisms. It is recommended to prioritize checking memory usage and monitoring resource consumption when the service is running.

0 replies

sideef5ect · 2025-03-05T08:47:47Z

sideef5ect
Mar 5, 2025
Author

nginx 会等到超时, 然后返回499
nginx config

map $http_upgrade $connection_upgrade {
    default upgrade;
    '' close;
}

server {
    listen 443 ssl;
    
    # ssl
    include ./conf.d/util/ssl.conf;

    set $lobe_upstream_host "lobe-chat:3210";

    # no need to auth
    location /manifest.webmanifest {
        proxy_pass http://$lobe_upstream_host;
        proxy_set_header Host $host;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_http_version 1.1;
        proxy_set_header Connection $connection_upgrade;
        proxy_buffering off;
        proxy_read_timeout 3600s;
        proxy_send_timeout 3600s;
    }

    location / {
        proxy_pass http://$lobe_upstream_host;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header REMOTE-HOST $remote_addr;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade;
        
        # Cache control for static files
        add_header X-Cache $upstream_cache_status;
        set $static_file 0;
        if ( $uri ~* "\.(gif|png|jpg|css|js|woff|woff2)$" ) {
            set $static_file 1;
            expires 1m;
        }
        if ( $static_file = 0 ) {
            add_header Cache-Control no-cache;
        }
        
        # Performance optimizations
        proxy_cache off;
        proxy_buffering off;
        chunked_transfer_encoding on;
        tcp_nopush on;
        tcp_nodelay on;
        keepalive_timeout 300;
        
    }
}

0 replies

sideef5ect · 2025-03-05T08:48:31Z

sideef5ect
Mar 5, 2025
Author

如何检查数据库连接池, 用的postgres

0 replies

lobehubbot · 2025-03-05T08:48:42Z

lobehubbot
Mar 5, 2025
Maintainer

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

How to check database connection pool, use postgres

0 replies

sideef5ect · 2025-03-05T08:50:33Z

sideef5ect
Mar 5, 2025
Author

docker stats

CONTAINER ID   NAME                                                 CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O         PIDS
789fede746be   lobe-chat.1.z8vtwzxkzb628qc8b3og1cx1z        0.00%     426.4MiB / 15.58GiB   2.67%     11.8MB / 23.1MB   0B / 5.58MB       22
ba57a5e0ce96   nginx.1.oarwyfwic4q9kc97mrloozs4b            0.00%     9.406MiB / 15.58GiB   0.06%     211MB / 218MB     2.13MB / 5.8MB    5
8733938d62d3   kratos-ui-node.1.3njbxa906rmx8z5rbzj39vhkc   0.00%     65.44MiB / 15.58GiB   0.41%     7.4MB / 1.3MB     5.77MB / 2.29MB   22

0 replies

sideef5ect · 2025-03-05T08:53:09Z

sideef5ect
Mar 5, 2025
Author

升级到最新版本, 此问题依然存在

docker ps                                                                                                                                                                          1 ↵
CONTAINER ID   IMAGE                                           COMMAND                  CREATED        STATUS        PORTS             NAMES
789fede746be   lobehub/lobe-chat-database:1.68.5               "/bin/node /app/star…"   7 hours ago    Up 7 hours    3210/tcp          lobe-chat.1.z8vtwzxkzb628qc8b3og1cx1z

0 replies

sideef5ect · 2025-03-05T09:06:59Z

sideef5ect
Mar 5, 2025
Author

postgres stats

  pid  | client_addr | state  |                                                      query                                                       
-------+-------------+--------+------------------------------------------------------------------------------------------------------------------
 10345 | 172.18.0.1  | idle   | SELECT t.table_name "name", pg_catalog.obj_description(pgc.oid, 'pg_class') "comment",pgc.reltuples "table_rows"+
       |             |        | FROM information_schema.tables t                                                                                +
       |             |        | JOIN pg_catalog.pg_class pgc ON t.table_name = pgc.relname                                                      +
       |             |        | JOIN pg_catalog.pg_namespace pgn ON pgn.oid=pgc.relnamespace and pgn.nspname=t.table_schema                     +
       |             |        | WHERE t.table_type='BASE TABLE'                                                                                 +
       |             |        | AND t.table_schema='drizzle' order by t.table_name;
 12343 | 172.18.0.1  | idle   | SELECT t.table_name "name", pg_catalog.obj_description(pgc.oid, 'pg_class') "comment",pgc.reltuples "table_rows"+
       |             |        | FROM information_schema.tables t                                                                                +
       |             |        | JOIN pg_catalog.pg_class pgc ON t.table_name = pgc.relname                                                      +
       |             |        | JOIN pg_catalog.pg_namespace pgn ON pgn.oid=pgc.relnamespace and pgn.nspname=t.table_schema                     +
       |             |        | WHERE t.table_type='BASE TABLE'                                                                                 +
       |             |        | AND t.table_schema='public' order by t.table_name;
 12344 | 172.18.0.1  | active | SELECT pid, client_addr, state, query                                                                           +
       |             |        | FROM pg_stat_activity;
(3 rows)

0 replies

sideef5ect · 2025-03-07T07:13:34Z

sideef5ect
Mar 7, 2025
Author

docker container logs

lobe-chat.1.cu10k3rny4jr@node3    | [auth][error] CallbackRouteError: Read more at https://errors.authjs.dev#callbackrouteerror
lobe-chat.1.cu10k3rny4jr@node3    | [auth][cause]: r3: "response" is not a conform Token Endpoint response (unexpected HTTP status code)
lobe-chat.1.cu10k3rny4jr@node3    |     at r4 (/app/.next/server/chunks/59314.js:368:4893)
lobe-chat.1.cu10k3rny4jr@node3    |     at nz (/app/.next/server/chunks/59314.js:368:17406)
lobe-chat.1.cu10k3rny4jr@node3    |     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
lobe-chat.1.cu10k3rny4jr@node3    |     at async n2 (/app/.next/server/chunks/59314.js:368:21360)
lobe-chat.1.cu10k3rny4jr@node3    | [auth][details]: {
lobe-chat.1.cu10k3rny4jr@node3    |   "provider": "cloudflare-zero-trust"
lobe-chat.1.cu10k3rny4jr@node3    | }
lobe-chat.1.cu10k3rny4jr@node3    | [rewrite] /next-auth/error -> http://127.0.0.1:3210/en-US__0__dark/next-auth/error
lobe-chat.1.cu10k3rny4jr@node3    | [rewrite] / -> http://127.0.0.1:3210/en-US__0__dark
lobe-chat.1.cu10k3rny4jr@node3    | [auth][error] CallbackRouteError: Read more at https://errors.authjs.dev#callbackrouteerror
lobe-chat.1.cu10k3rny4jr@node3    | [auth][cause]: r3: "response" is not a conform Token Endpoint response (unexpected HTTP status code)
lobe-chat.1.cu10k3rny4jr@node3    |     at r4 (/app/.next/server/chunks/59314.js:368:4893)
lobe-chat.1.cu10k3rny4jr@node3    |     at nz (/app/.next/server/chunks/59314.js:368:17406)
lobe-chat.1.cu10k3rny4jr@node3    |     at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
lobe-chat.1.cu10k3rny4jr@node3    |     at async n2 (/app/.next/server/chunks/59314.js:368:21360)
lobe-chat.1.cu10k3rny4jr@node3    | [auth][details]: {
lobe-chat.1.cu10k3rny4jr@node3    |   "provider": "cloudflare-zero-trust"
lobe-chat.1.cu10k3rny4jr@node3    | }

0 replies

arvinxx · 2025-03-07T07:36:03Z

arvinxx
Mar 7, 2025
Maintainer

@sideef5ect 看这个报错是 auth 没连上吧？感觉你得检查下连接性的问题？

0 replies

lobehubbot · 2025-03-07T07:36:13Z

lobehubbot
Mar 7, 2025
Maintainer

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

@sideef5ect See this error is that auth is not connected, right? I feel like you have to check the connectivity problem?

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Bug] 每隔一段时间服务器对所有涉及trpc的请求都无响应, 直到客户端超时 #6775

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 14 comments

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

Select a reply

[Bug] 每隔一段时间服务器对所有涉及trpc的请求都无响应, 直到客户端超时 #6775

sideef5ect Mar 3, 2025

📦 Platform

📦 Deploymenet mode

📌 Version

💻 Operating System

🌐 Browser

🐛 Bug Description

📷 Recurrence Steps

🚦 Expected Behavior

📝 Additional Information

Replies: 14 comments

lobehubbot Mar 3, 2025 Maintainer

sideef5ect Mar 4, 2025 Author

sideef5ect Mar 4, 2025 Author

arvinxx Mar 4, 2025 Maintainer

问题概述

可能的原因分析

1. 内存泄漏问题

2. 连接池耗尽

3. Docker 资源限制

4. 数据库性能问题

5. Nginx 代理配置问题

建议解决方案

lobehubbot Mar 4, 2025 Maintainer

Problem Overview

Possible Cause Analysis

1. Memory Leak Issues

2. Connection pool exhausted

3. Docker resource limitations

4. Database performance issues

5. Nginx proxy configuration issues

Suggested Solutions

sideef5ect Mar 5, 2025 Author

sideef5ect Mar 5, 2025 Author

lobehubbot Mar 5, 2025 Maintainer

sideef5ect Mar 5, 2025 Author

sideef5ect Mar 5, 2025 Author

sideef5ect Mar 5, 2025 Author

sideef5ect Mar 7, 2025 Author

arvinxx Mar 7, 2025 Maintainer

lobehubbot Mar 7, 2025 Maintainer

sideef5ect
Mar 3, 2025

lobehubbot
Mar 3, 2025
Maintainer

sideef5ect
Mar 4, 2025
Author

sideef5ect
Mar 4, 2025
Author

arvinxx
Mar 4, 2025
Maintainer

lobehubbot
Mar 4, 2025
Maintainer

sideef5ect
Mar 5, 2025
Author

sideef5ect
Mar 5, 2025
Author

lobehubbot
Mar 5, 2025
Maintainer

sideef5ect
Mar 5, 2025
Author

sideef5ect
Mar 5, 2025
Author

sideef5ect
Mar 5, 2025
Author

sideef5ect
Mar 7, 2025
Author

arvinxx
Mar 7, 2025
Maintainer

lobehubbot
Mar 7, 2025
Maintainer