openimsdk
[BUG]
OpenIM Server Version
3.8
Operating System and CPU Architecture
Linux (AMD)
Deployment Method
Source Code Deployment
Bug Description and Steps to Reproduce
使用docker 部署的docker-compose.yaml ，把 kafka模块单独用一个docker-compose.yaml 放置部署时，openim-server 的日志连接报错误，弄不明白是kafaka的问题，还是openim-server的问题
127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:32.576 WARN [PID:1601] openim-msgtransfer [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toRedis"], "groupID": "redis", "error": "dial tcp: lookup kafka on 127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:40.536 WARN [PID:1518] openim-push [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toOfflinePush"], "groupID": "offlinePush", "error": "dial tcp: lookup kafka on 127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:40.536 WARN [PID:1542] openim-push [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toOfflinePush"], "groupID": "offlinePush", "error": "dial tcp: lookup kafka on 127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:40.548 WARN [PID:1563] openim-push [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toPush"], "groupID": "push", "error": "dial tcp: lookup kafka on 127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:40.551 WARN [PID:1614] openim-msgtransfer [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toRedis"], "groupID": "redis", "error": "dial tcp: lookup kafka on 127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:40.552 WARN [PID:1545] openim-push [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toPush"], "groupID": "push", "error": "dial tcp: lookup kafka on 127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:40.553 WARN [PID:1553] openim-push [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toPush"], "groupID": "push", "error": "dial tcp: lookup kafka on 127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:40.554 WARN [PID:1613] openim-msgtransfer [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toMongo"], "groupID": "mongo", "error": "dial tcp: lookup kafka on 127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:40.555 WARN [PID:1520] openim-push [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toPush"], "groupID": "push", "error": "dial tcp: lookup kafka on 127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:40.558 WARN [PID:1606] openim-msgtransfer [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toRedis"], "groupID": "redis", "error": "dial tcp: lookup kafka on 127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:40.559 WARN [PID:1519] openim-push [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toPush"], "groupID": "push", "error": "dial tcp: lookup kafka on 127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:40.559 WARN [PID:1580] openim-msgtransfer [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toMongo"], "groupID": "mongo", "error": "dial tcp: lookup kafka on 127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:40.560 WARN [PID:1528] openim-push [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toOfflinePush"], "groupID": "offlinePush", "error": "dial tcp: lookup kafka on 127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:40.573 WARN [PID:1619] openim-msgtransfer [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toRedis"], "groupID": "redis", "error": "dial tcp: lookup kafka on 127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:40.573 WARN [PID:1602] openim-msgtransfer [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toMongo"], "groupID": "mongo", "error": "dial tcp: lookup kafka on 127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:40.579 WARN [PID:1579] openim-msgtransfer [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toRedis"], "groupID": "redis", "error": "dial tcp: lookup kafka on 127.0.0.11:53: server misbehaving"} 2025-04-30 02:01:40.580 WARN [PID:1601] openim-msgtransfer [v3.8.3 ] [kafka/consumer_group.go:61] consume err {"topic": ["toMongo"], "groupID": "mongo", "error": "dial tcp: lookup kafka
Screenshots Link
No response
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.
Docker deployment only fits the situation where all components and OpenIM are deployed on a single machine.
