openim-docker [BUG] chat-server unhealthy

OpenIM Server Version

trunk

Operating System and CPU Architecture

Linux (AMD)

Deployment Method

Docker Deployment

Bug Description and Steps to Reproduce

this is log:

[2025-07-28 15:01:38 UTC] Starting tools primarily involves component verification and other preparatory tasks. Starting /openim-server/_output/bin/tools/linux/amd64/check-free-memory -c /openim-server/config/ System available memory is sufficient: 12.05GB Starting /openim-server/_output/bin/tools/linux/amd64/check-free-memory -c /openim-server/config/ successfully Starting /openim-server/_output/bin/tools/linux/amd64/check-component -c /openim-server/config/ check-component Index: 0, Config Path: /openim-server/config/ Mongo check succeeded. Redis check succeeded. Kafka check succeeded. MinIO check succeeded. Etcd check succeeded. All components checks passed successfully. Starting /openim-server/_output/bin/tools/linux/amd64/check-component -c /openim-server/config/ successfully Starting /openim-server/_output/bin/tools/linux/amd64/seq -c /openim-server/config/ seq task Error: Redis Ping failed, Address=[localhost:16379], Username=, ClusterMode=false | -> redisutil.NewRedisClient() /go/pkg/mod/github.com/openimsdk/[email protected]/db/redisutil/redis.go:62 -> internal.Main() /openim-server/tools/seq/internal/main.go:66 -> main.main() /openim-server/tools/seq/main.go:18 seq task success! Starting /openim-server/_output/bin/tools/linux/amd64/seq -c /openim-server/config/ successfully [2025-07-28 15:01:39 UTC] All tools executed successfully [2025-07-28 15:01:39 UTC] Starting services involves multiple RPCs and APIs and may take some time. Please be patient Starting /openim-server/_output/bin/platforms/linux/amd64/openim-rpc-friend -i 0 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-rpc-user -i 0 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-msggateway -i 0 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-api -i 0 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-push -i 0 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-push -i 1 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-push -i 2 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-push -i 3 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-push -i 4 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-push -i 5 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-push -i 6 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-push -i 7 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-rpc-conversation -i 0 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-rpc-auth -i 0 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-rpc-group -i 0 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-rpc-msg -i 0 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-msgtransfer -i 0 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-msgtransfer -i 1 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-msgtransfer -i 2 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-msgtransfer -i 3 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-msgtransfer -i 4 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-msgtransfer -i 5 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-msgtransfer -i 6 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-msgtransfer -i 7 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-rpc-third -i 0 -c /openim-server/config/ Starting /openim-server/_output/bin/platforms/linux/amd64/openim-crontask -i 0 -c /openim-server/config/ [2025-07-28 15:01:39 UTC] All services are running normally. [2025-07-28 15:01:39 UTC] Display details of the ports listened to by the service: [2025-07-28 15:01:40 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-rpc-group -i 0 -c /openim-server/config/, PID: 1567 is not listening on any ports. [2025-07-28 15:01:40 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-rpc-third -i 0 -c /openim-server/config/, PID: 1604 is not listening on any ports. [2025-07-28 15:01:40 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-crontask -i 0 -c /openim-server/config/, PID: 1627 is not listening on any ports. [2025-07-28 15:01:40 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-push -i 0 -c /openim-server/config/, PID: 1557 is listening on ports: 44773, 45363 [2025-07-28 15:01:40 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-push -i 1 -c /openim-server/config/, PID: 1558 is listening on ports: 35105, 43985 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-push -i 2 -c /openim-server/config/, PID: 1559 is listening on ports: 44083, 39129 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-push -i 3 -c /openim-server/config/, PID: 1560 is listening on ports: 44187, 38703 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-push -i 4 -c /openim-server/config/, PID: 1561 is listening on ports: 41787, 44125 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-push -i 5 -c /openim-server/config/, PID: 1562 is listening on ports: 44463, 40577 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-push -i 6 -c /openim-server/config/, PID: 1563 is listening on ports: 33575, 44525 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-push -i 7 -c /openim-server/config/, PID: 1564 is listening on ports: 46115, 40743 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-rpc-auth -i 0 -c /openim-server/config/, PID: 1566 is listening on ports: 33865, 46231 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-api -i 0 -c /openim-server/config/, PID: 1556 is listening on ports: 36033, 10002 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-rpc-user -i 0 -c /openim-server/config/, PID: 1554 is listening on ports: 44303, 39941 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-msggateway -i 0 -c /openim-server/config/, PID: 1555 is listening on ports: 10001, 35567, 44329 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-rpc-msg -i 0 -c /openim-server/config/, PID: 1568 is listening on ports: 41251, 35323 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-rpc-friend -i 0 -c /openim-server/config/, PID: 1553 is listening on ports: 35321, 45165 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-msgtransfer -i 0 -c /openim-server/config/, PID: 1569 is listening on ports: 36697 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-msgtransfer -i 1 -c /openim-server/config/, PID: 1570 is listening on ports: 34117 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-msgtransfer -i 2 -c /openim-server/config/, PID: 1571 is listening on ports: 42885 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-msgtransfer -i 3 -c /openim-server/config/, PID: 1574 is listening on ports: 33005 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-msgtransfer -i 4 -c /openim-server/config/, PID: 1587 is listening on ports: 41433 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-msgtransfer -i 5 -c /openim-server/config/, PID: 1596 is listening on ports: 44269 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-msgtransfer -i 6 -c /openim-server/config/, PID: 1599 is listening on ports: 41951 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-msgtransfer -i 7 -c /openim-server/config/, PID: 1601 is listening on ports: 46835 [2025-07-28 15:01:41 UTC] Cmdline: /openim-server/_output/bin/platforms/linux/amd64/openim-rpc-conversation -i 0 -c /openim-server/config/, PID: 1565 is listening on ports: 32865, 33151

Screenshots Link

No response

Jul 29 '25 03:07 yipianchuyun

i meet this problem too.i just clone this repo and replace the [external_ip] in .env file and docker compose up -d then this problem happened. and the logs show all right .

Aug 08 '25 15:08 LaiosOvO

i try the condition check sh.it is always pending, any document or issue can help? i do not know how to fix it

docker exec -it openim-server sh -c "time mage check"

Aug 08 '25 15:08 LaiosOvO

@mo3et @caixiangyue @sskyy

Aug 08 '25 16:08 LaiosOvO

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

@Mo3 forehead @Cai Agree @Available at any time

Aug 08 '25 16:08 OpenIM-Robot

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

The same is true for me. The docker version is now in an invalid state. It is not possible to follow the guide and the logs are not reported.

Sep 15 '25 07:09 OpenIM-Robot

实验过了，虽然校验是不健康，但是不影响使用

Sep 16 '25 03:09 softdong

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

After the experiment, although the verification is unhealthy, it does not affect the use

Sep 16 '25 03:09 OpenIM-Robot

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

,

After three days of experimentation, first use the v3.7 version code, and then replace the .env content image to 3.8 image, which can be deployed normally, and it will take a long time to become healthy, without affecting the use.

Sep 16 '25 06:09 OpenIM-Robot

我也遇到了这个问题，虽然健康检查为unhealthy，但是不影响使用，不过登录的时候还是会有问题，登录按钮一直再转圈，后台也没有日志，我甚至排查了安全设备，但是重启openim-chat和openim-server后正常了

Nov 07 '25 01:11 jdjn123

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

I also encountered this problem. Although the health check is unhealthy, it does not affect the use. However, there are still problems when logging in. The login button keeps spinning in circles, and there are no logs in the background. I even checked the security device, but after restarting openim-chat and openim-server, everything was normal.

Nov 07 '25 01:11 OpenIM-Robot