Which client cannot connect to mosquitto broker

Hi everyone.

Can you tell me where Mosquitto broker stores its logs?

Rasberry has a home assistant installed that works on a closed LAN.
Mosquitto broker is installed, through which two additions to the home assistant work - Zigbee2MQTT and SDR. The integration itself is also connected, and everything works fine, no problems.

But something else wants to connect to the broker, some client:

2024-05-02 14:09:18: Client <unknown> closed his connection.
2024-05-02 14:11:18: New connection from 172.30.32.2:52848 to port 1883.
2024-05-02 14:11:18: Client <unknown> closed his connection.
2024-05-02 14:13:18: New connection from 172.30.32.2:32888 to port 1883.
2024-05-02 14:13:18: Client <unknown> closed its connection.
2024-05-02 14:15:18: New connection from 172.30.32.2:36690 to port 1883.
2024-05-02 14:15:18: Client <unknown> closed its connection.
2024-05-02 14:17:18: New connection from 172.30.32.2:45592 to port 1883.
2024-05-02 14:17:18: Client <unknown> closed its connection.
2024-05-02 14:19:18: New connection from 172.30.32.2:38546 to port 1883.

I have patiently studied the add-ons and integrations I have, but no one is asking me to connect to a broker.

Tell me how to find out who wants to connect to the broker. I’m already crazy about how to find out.

Need to identify addon using this IP. Not sure how to do this with HAOS currently.

If their is portainer addon maybe it will show ips
OR
Maybe ssh addon will allow connection so you can run docker commands to get IP

That is supervisor checking if the add-on is still running.

The client address 172.30.32.2 is on the same network as the hassio address 172.30.32.1


if that’s what you mean.
Or do you mean to determine what responds to this address?

Unfortunately no. The supervisor has an address of 32.1 and connects normally. The information is in the magazines.

Restart an addon and look at the logs for its IP address.
Repeat with next addon until you find the right one.

All core containers use the 172.30.32.xx network

how did you get this screenshot?

There are such networks

when entering network 32.0 there is no device with address 32.2

I’ll go crazy soon :face_with_symbols_over_mouth:

Run

ha supervisor info

returns 172.30.32.2

afbeelding

Great, you helped me understand what wants to connect to mqtt. :+1:
Now the question is where is the mqtt setting for hassio_supervisor?

It reads the info from the addon’s configuration page and there is nothing weird in those log entries.
It is the watchdog feature that checks if the service is running.

I already found Francis answer in another thread. After I realized that it was a guard dog.
Watchdog