Mosquitto MQTT constant messages in log and need time stamp

girkers · June 21, 2021, 10:44am

I am having a little issues with a couple of my Tasmota devices and checking in the Mosquitto MQTT log it is being flooded with these messages:

623128720: New connection from 172.30.32.2 on port 1883.
1623128720: Socket error on client <unknown>, disconnecting.
1623128840: New connection from 172.30.32.2 on port 1883.
1623128840: Socket error on client <unknown>, disconnecting.
1623128874: Saving in-memory database to /data/mosquitto.db.
1623128960: New connection from 172.30.32.2 on port 1883.
1623128960: Socket error on client <unknown>, disconnecting.
1623129080: New connection from 172.30.32.2 on port 1883.
1623129080: Socket error on client <unknown>, disconnecting.

I am running HA as a docker inside ESXi, my IOT network is 192.168.72.x, ESXi reports the other internal address as 172.30.22.1

No idea what the 172.30.32.2 address is.

How do I stop these unnecessary messages? AND

How do I get the log to display the proper time?
I have seen these in the documentation:

log_timestamp [ true | false ]

    Boolean value, if set to true a timestamp value will be added to each log entry. The default is true.

    Reloaded on reload signal.
log_timestamp_format format

    Set the format of the log timestamp. If left unset, this is the number of seconds since the Unix epoch. This option is a free text string which will be passed to the strftime function as the format specifier. To get an ISO 8601 datetime, for example:

    log_timestamp_format %Y-%m-%dT%H:%M:%S

I tried to add them to the Options in the Mosquitto configuration but it says it is invalid.

Help Please!

tom_l · June 21, 2021, 11:21am

It is the Home Assistant Docker network.

Sounds like the Home Assistant MQTT integration has invalid credentials. Did you store any when setting up the integration?

You shouldn’t have had to (it is automatic) but occasionally this happens during the config flow for some reason.

girkers · June 21, 2021, 11:24am

So how do I fix it?

tom_l · June 21, 2021, 11:31am

You could try deleting the MQTT integration (not the broker) and re-addding it.

Your existing devices should be restored by retained discovery messages in the broker. A restart may be required.

123 · June 21, 2021, 11:32am

I believe it’s the Supervisor container (if you are running Home Assistant OS or Home Assistant Supervised).

tom_l · June 23, 2021, 7:56am

Yeah, and I’ve just found that the error is a normal part of the supervisor operation:

github.com/home-assistant/core

Unknown client connecting to MQTT broker

opened 05:32AM - 08 Jun 21 UTC

closed 07:20AM - 08 Jun 21 UTC

delta010

integration: mqtt

### The problem in my home assistant mosquito add-on, an unknown client no clie…nt id is connecting and disconnecting as a loop forever the IP address of the client looks like a docker container IP address (172.30.32.2). my network address is 192.168.0.1 , but I can't find any what container is trying to connect .pleas help me ### What is version of Home Assistant Core has the issue? core-2021.6.2 ### What was the last working version of Home Assistant Core? core-2021.4.0 ### What type of installation are you running? Home Assistant OS ### Integration causing the issue MQTT ### Link to integration documentation on our website https://www.home-assistant.io/integrations/mqtt/ ### Example YAML snippet ```yaml logins: - username: user password: 123456789 customize: active: false folder: mosquitto certfile: fullchain.pem keyfile: privkey.pem require_certificate: false ``` ### Anything in the logs that might be useful for us? ```txt 1623126169: New connection from 192.168.0.110 on port 1883. 1623126169: New client connected from 192.168.0.110 as sonofflight1 (p2, c1, k30, u'hassio'). 1623126184: New connection from 192.168.0.117 on port 1883. 1623126184: New client connected from 192.168.0.117 as keypad (p2, c1, k30, u'hassio'). 1623126204: New connection from 172.30.32.1 on port 1883. 1623126204: New client connected from 172.30.32.1 as 2he2ok6kXNV7syNo9EIH5K (p2, c1, k60, u'hassio'). 1623126373: New connection from 172.30.32.2 on port 1883. 1623126373: Socket error on client <unknown>, disconnecting. 1623126431: New connection from 172.30.33.5 on port 1883. 1623126431: New client connected from 172.30.33.5 as mqttjs_c8632349 (p2, c1, k60, u'hassio'). 1623126493: New connection from 172.30.32.2 on port 1883. 1623126493: Socket error on client <unknown>, disconnecting. 1623126613: New connection from 172.30.32.2 on port 1883. 1623126613: Socket error on client <unknown>, disconnecting. 1623126733: New connection from 172.30.32.2 on port 1883. 1623126733: Socket error on client <unknown>, disconnecting. 1623126853: New connection from 172.30.32.2 on port 1883. 1623126853: Socket error on client <unknown>, disconnecting. 1623126973: New connection from 172.30.32.2 on port 1883. 1623126973: Socket error on client <unknown>, disconnecting. 1623127093: New connection from 172.30.32.2 on port 1883. 1623127093: Socket error on client <unknown>, disconnecting. 1623127213: New connection from 172.30.32.2 on port 1883. 1623127213: Socket error on client <unknown>, disconnecting. 1623127333: New connection from 172.30.32.2 on port 1883. 1623127333: Socket error on client <unknown>, disconnecting. 1623127453: New connection from 172.30.32.2 on port 1883. 1623127453: Socket error on client <unknown>, disconnecting. 1623127573: New connection from 172.30.32.2 on port 1883. 1623127573: Socket error on client <unknown>, disconnecting. 1623127693: New connection from 172.30.32.2 on port 1883. 1623127693: Socket error on client <unknown>, disconnecting. 1623127813: New connection from 172.30.32.2 on port 1883. 1623127813: Socket error on client <unknown>, disconnecting. 1623127933: New connection from 172.30.32.2 on port 1883. 1623127933: Socket error on client <unknown>, disconnecting. 1623127960: Saving in-memory database to /data/mosquitto.db. 1623128053: New connection from 172.30.32.2 on port 1883. 1623128053: Socket error on client <unknown>, disconnecting. 1623128173: New connection from 172.30.32.2 on port 1883. 1623128173: Socket error on client <unknown>, disconnecting. 1623128293: New connection from 172.30.32.2 on port 1883. 1623128293: Socket error on client <unknown>, disconnecting. 1623128413: New connection from 172.30.32.2 on port 1883. 1623128413: Socket error on client <unknown>, disconnecting. 1623128533: New connection from 172.30.32.2 on port 1883. 1623128533: Socket error on client <unknown>, disconnecting. 1623128653: New connection from 172.30.32.2 on port 1883. 1623128653: Socket error on client <unknown>, disconnecting. 1623128773: New connection from 172.30.32.2 on port 1883. 1623128773: Socket error on client <unknown>, disconnecting. 1623128893: New connection from 172.30.32.2 on port 1883. 1623128893: Socket error on client <unknown>, disconnecting. 1623129013: New connection from 172.30.32.2 on port 1883. 1623129013: Socket error on client <unknown>, disconnecting. 1623129133: New connection from 172.30.32.2 on port 1883. 1623129133: Socket error on client <unknown>, disconnecting. 1623129253: New connection from 172.30.32.2 on port 1883. 1623129253: Socket error on client <unknown>, disconnecting. 1623129373: New connection from 172.30.32.2 on port 1883. 1623129373: Socket error on client <unknown>, disconnecting. 1623129493: New connection from 172.30.32.2 on port 1883. 1623129493: Socket error on client <unknown>, disconnecting. 1623129613: New connection from 172.30.32.2 on port 1883. 1623129613: Socket error on client <unknown>, disconnecting. 1623129733: New connection from 172.30.32.2 on port 1883. 1623129733: Socket error on client <unknown>, disconnecting. 1623129761: Saving in-memory database to /data/mosquitto.db. 1623129853: New connection from 172.30.32.2 on port 1883. 1623129853: Socket error on client <unknown>, disconnecting. 1623129973: New connection from 172.30.32.2 on port 1883. ``` ### Additional information _No response_

123 · June 23, 2021, 2:28pm

Frenck said:

That is the supervisor checking if the add-on is still responding as part of a health check. This is expected, not a bug and actually good.

That’s interesting because I’m running the latest version of Supervisor (2021.06.3) and I don’t get those “actually good” socket errors reported in my MQTT broker’s log.

The MQTT broker is the Mosquitto Add-On but it’s version 5.1 (not the latest version 6.0.1). I don’t know if that has any bearing on the matter.

tom_l · June 23, 2021, 2:51pm

I’m running

Mosquitto addon 6.0.1
Supervisor 2021.06.3

And pretty much all I see in the Mosquitto log is this every two seconds:

2021-06-23T23:05:01: New connection from 172.30.32.2 on port 1883.
2021-06-23T23:05:01: Socket error on client <unknown>, disconnecting.

123 · June 23, 2021, 2:56pm

Looks like another reason for me to stay with version 5.1. I don’t need the log spammed with “good” connection errors.

alka79 · May 25, 2024, 4:57pm

3 years later, is there a solution to avoid the supervisor spamming mosquitto log ?

2024-05-25 17:20:08: New connection from 172.30.32.2:59354 on port 1883.
2024-05-25 17:20:08: Client <unknown> closed its connection.
2024-05-25 17:22:08: New connection from 172.30.32.2:42436 on port 1883.
2024-05-25 17:22:08: Client <unknown> closed its connection.
2024-05-25 17:24:08: New connection from 172.30.32.2:36686 on port 1883.
2024-05-25 17:24:08: Client <unknown> closed its connection.
2024-05-25 17:26:08: New connection from 172.30.32.2:35010 on port 1883.
2024-05-25 17:26:08: Client <unknown> closed its connection.
2024-05-25 17:28:08: New connection from 172.30.32.2:39460 on port 1883.
2024-05-25 17:28:08: Client <unknown> closed its connection.
2024-05-25 17:30:08: New connection from 172.30.32.2:45034 on port 1883.
2024-05-25 17:30:08: Client <unknown> closed its connection.

At first this is scary for rookie like me: WTH is this unknow client trying to connect to my broker ???

Then after googling, I find out that it is a well known, valid client. The flood of messages is only pollution hiding more important messages.

Is there a setting somewhere to avoid the flood of useless messages in the log ?

mosquitto 6.4.0
Core 2024.5.3
Supervisor 2024.05.1
Operating System 12.3
Frontend 20240501.1

Thanks

tom_l · May 25, 2024, 9:43pm

Switch off the watchdog on the add-on main page.

The add-on now wont restart if it crashes though.