Skip to content
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] Expected 4 openim msgtransfer processes, but found 0 msgtransfer processes. #2573

Closed
goovoo opened this issue Aug 29, 2024 · 4 comments
Labels
bug Categorizes issue or PR as related to a bug.

Comments

@goovoo
Copy link

goovoo commented Aug 29, 2024

OpenIM Server Version

release-v3.6

Operating System and CPU Architecture

Linux (AMD)

Deployment Method

Docker Deployment

Bug Description and Steps to Reproduce

+++ cat openim log file >>> /openim/openim-server/_output/logs/openim-20240829.log
!!! [2024-08-29 18:37:52 CST] check process failed.

Not started processes:
Process /openim/openim-server/_output/bin/platforms/linux/amd64/openim-api is not started.
Process /openim/openim-server/_output/bin/platforms/linux/amd64/openim-crontask is not started.
Process /openim/openim-server/_output/bin/platforms/linux/amd64/openim-msggateway is not started.
Process /openim/openim-server/_output/bin/platforms/linux/amd64/openim-push is not started.
Process /openim/openim-server/_output/bin/platforms/linux/amd64/openim-rpc-auth is not started.
Process /openim/openim-server/_output/bin/platforms/linux/amd64/openim-rpc-conversation is not started.
Process /openim/openim-server/_output/bin/platforms/linux/amd64/openim-rpc-friend is not started.
Process /openim/openim-server/_output/bin/platforms/linux/amd64/openim-rpc-group is not started.
Process /openim/openim-server/_output/bin/platforms/linux/amd64/openim-rpc-msg is not started.
Process /openim/openim-server/_output/bin/platforms/linux/amd64/openim-rpc-third is not started.
Process /openim/openim-server/_output/bin/platforms/linux/amd64/openim-rpc-user is not started.
2024-08-29 18:37:52 OpenIM Stdout Log >> cat /openim/openim-server/_output/logs/openim-20240829.log
2024-08-29 18:37:52 OpenIM Stderr Log >> cat /openim/openim-server/_output/logs/openim-error-20240829.log
Error: address:[172.28.0.1:16379], username:, password:openIM123, clusterMode:false, enablePipeline:false: dial tcp 172.28.0.1:16379: connect: connection refused
Usage:
Start openIM application [flags]

Flags:
-c, --config_folder_path string path to config file folder
-h, --help help for Start

openim-crontask exit -1: dial tcp 172.28.0.1:16379: connect: connection refused
address:[172.28.0.1:16379], username:, password:openIM123, clusterMode:false, enablePipeline:false
github.com/OpenIMSDK/tools/errs.Wrap
/go/pkg/mod/github.com/!open!i!m!s!d!k/[email protected]/errs/coderr.go:128
github.com/openimsdk/open-im-server/v3/pkg/common/db/cache.NewRedis
/openim/openim-server/pkg/common/db/cache/init_redis.go:80
github.com/openimsdk/open-im-server/v3/internal/tools.InitMsgTool
/openim/openim-server/internal/tools/msg.go:67
github.com/openimsdk/open-im-server/v3/internal/tools.StartTask
/openim/openim-server/internal/tools/cron_task.go:35
github.com/openimsdk/open-im-server/v3/pkg/common/cmd.(*CronTaskCmd).addRunE.func1
/openim/openim-server/pkg/common/cmd/cron_task.go:38
github.com/spf13/cobra.(*Command).execute
/go/pkg/mod/github.com/spf13/[email protected]/command.go:983
github.com/spf13/cobra.(*Command).ExecuteC
/go/pkg/mod/github.com/spf13/[email protected]/command.go:1115
github.com/spf13/cobra.(*Command).Execute
/go/pkg/mod/github.com/spf13/[email protected]/command.go:1039
github.com/openimsdk/open-im-server/v3/pkg/common/cmd.(*RootCmd).Execute
/openim/openim-server/pkg/common/cmd/root.go:180
github.com/openimsdk/open-im-server/v3/pkg/common/cmd.(*CronTaskCmd).Exec
/openim/openim-server/pkg/common/cmd/cron_task.go:43
main.main
/openim/openim-server/cmd/openim-crontask/main.go:24
runtime.main
/usr/local/go/src/runtime/proc.go:250
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1598

[root@imserver ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
bitnami/zookeeper 3.8 2121564ec692 4 months ago 570MB
bitnami/node-exporter 1.7.0 fa9f899025de 4 months ago 146MB
ghcr.io/openimsdk/openim-server release-v3.6 c3d0a32eb083 5 months ago 587MB
ghcr.io/openimsdk/openim-chat release-v1.6 2a757b3017e8 5 months ago 286MB
ghcr.io/openimsdk/openim-web v3.5.0-docker 5832eaadfde7 7 months ago 222MB
minio/minio RELEASE.2024-01-11T07-46-16Z f5d82361e10f 7 months ago 151MB
ghcr.io/openimsdk/openim-admin toc-base-open-docker.35 3c146d363beb 7 months ago 190MB
prom/prometheus v2.48.1 ea7f826b1553 8 months ago 247MB
bitnami/kafka 3.5.1 f79889e4e4af 9 months ago 558MB
grafana/grafana 10.2.2 06e5d59b720d 9 months ago 399MB
prom/alertmanager v0.26.0 9f27df16978d 12 months ago 66.8MB
mongo 6.0.2 b70536aeb250 22 months ago 695MB
redis 7.0.0 53aa81e8adfa 2 years ago 117MB

Screenshots Link

No response

@goovoo goovoo added the bug Categorizes issue or PR as related to a bug. label Aug 29, 2024
@OpenIM-Robot
Copy link

Hello! Thank you for filing an issue.

If this is a bug report, please include relevant logs to help us debug the problem.

Join slack 🤖 to connect and communicate with our developers.

@goovoo
Copy link
Author

goovoo commented Aug 29, 2024

I didn't do anything, my service suddenly became inaccessible, I tried to execute:

  1. service docker restart

  2. reboot

  3. "docker compose down" and "docker compose up -d"

After all three methods have been tried, the openim-server container still does not start.

[root@openim-docker]# docker compose up -d
WARN[0000] /root/openim-docker/docker-compose.yaml: version is obsolete
[+] Running 14/14
✔ Network openim-docker_openim-server Created 0.1s
✔ Container grafana Started 0.1s
✔ Container mongo Started 0.1s
✔ Container kafka Started 0.1s
✔ Container openim-web Started 0.1s
✔ Container node-exporter Started 0.1s
✔ Container openim-admin Started 0.1s
✔ Container redis Started 0.1s
✔ Container zookeeper Started 0.1s
✔ Container minio Started 0.1s
✘ Container openim-server Error 0.9s
✔ Container alertmanager Created 0.0s
✔ Container openim-chat Created 0.3s
✔ Container prometheus Created 0.0s
dependency failed to start: container openim-server is unhealthy

@skiffer-git
Copy link
Member

This is usually because Kafka has crashed.
Also, I recommend upgrading to version 3.8 as soon as possible.

@skiffer-git
Copy link
Member

deploying OpenIM is smoothy in release-v3.8 version, I recommend you update to this version, if you encounter new issue, please reopen this issue or open new issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants