-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[Deployment] Kafka check failed: NewClient failed, config: =&{Username: Password: ProducerAck: CompressType:none Addr:[localhost:19094] TLS:{EnableTLS:false CACrt: ClientCrt: ClientKey: ClientKeyPwd: InsecureSkipVerify:false}}: kafka: client has run out of available brokers to talk to: read tcp [::1]:34736->[::1]:19094: read: connection reset by peer #2518
Comments
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. |
What changes did you make to the settings |
It looks like Kafka didn't start properly from what I can see. |
thx, it works now. Docker Deploy first.then normal. both source code and docker deployment |
pls help to take a look first. thanks a lot |
|
chmod +x scripts/*.sh |
docker exec kafka /opt/bitnami/kafka/create-topic.sh |
docker exec -it mongo bash /docker-entrypoint-initdb.d/mongo-init.sh |
or |
OpenIM Server Version
3.8
Operating System and CPU Architecture
Linux (AMD)
Deployment Method
Source Code Deployment
Issue Description and Steps to Reproduce
Kafka check failed: NewClient failed, config: =&{Username: Password: ProducerAck: CompressType:none Addr:[localhost:19094] TLS:{EnableTLS:false CACrt: ClientCrt: ClientKey: ClientKeyPwd: InsecureSkipVerify:false}}: kafka: client has run out of available brokers to talk to: read tcp [::1]:34736->[::1]:19094: read: connection reset by peer
Screenshots Link
The text was updated successfully, but these errors were encountered: