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

MQTT Kafka broker example not working #279

Open
epieffe opened this issue Dec 18, 2024 · 0 comments · May be fixed by #280
Open

MQTT Kafka broker example not working #279

epieffe opened this issue Dec 18, 2024 · 0 comments · May be fixed by #280

Comments

@epieffe
Copy link

epieffe commented Dec 18, 2024

I am interested in trying Zilla as an MQTT broker that connects to Kafka, but I cannot manage to get the example in the documentation working. This seems to be the only documentation available related to MQTT, so I don't know what to do now. I hope someone can help me get the example working so I can proceed to integrate Zilla in my project.

What I did:

  1. Download the example from here.
  2. Run the example with docker compose --profile kafka --profile init-kafka up -d.
  3. Verify that Kafka is running correctly and check on kafka-ui that the topics are created.
  4. Try to connect to Zilla using the Mosquitto client, but receive error.

The Zilla container does not log anything usefull, I only see the zilla.yml content and then 'started'.

This is the output I get when I try to subscribe to a topic:

$ mosquitto_sub --url mqtt://127.0.0.1:7183/zilla
Connection error: Connection Refused: unknown reason.

This is the output I get when I try to publish a message on a topic:

$ mosquitto_pub --url mqtt://127.0.0.1:7183/zilla --message 'Hello, world'
Connection error: Connection Refused: unknown reason.
Error: A network protocol error occurred when communicating with the broker.

Tried on Windows 11 with Docker Desktop and on Debian 12.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant