MQTT looping restart

Configuration
,
1

Hi

I recently updated to core_2023.7.3.
Since then, any Tasmota lights/switches are unavailable.

I think I have tracked it down to MQTT:

In HA log:

Failed to connect to MQTT server due to exception: [Errno 111] Connection refused

In Mosquitto broker log there seems to be a looping restart:

[15:17:41] INFO: Starting mosquitto MQTT broker...
2023-08-04 15:17:41: Warning: Mosquitto should not be run as root/administrator.
[15:17:41] INFO: Successfully send discovery information to Home Assistant.
[03:17:41] INFO: Service restart after closing
[15:17:41] INFO: Successfully send service information to the Supervisor.
[15:17:42] INFO: Starting mosquitto MQTT broker...
2023-08-04 15:17:42: Warning: Mosquitto should not be run as root/administrator.
[15:17:42] INFO: Successfully send discovery information to Home Assistant.
[15:17:42] INFO: Successfully send service information to the Supervisor.
[03:17:42] INFO: Service restart after closing
[15:17:43] INFO: Starting mosquitto MQTT broker...
2023-08-04 15:17:43: Warning: Mosquitto should not be run as root/administrator.
[15:17:43] INFO: Successfully send discovery information to Home Assistant.
[03:17:43] INFO: Service restart after closing
[15:17:43] INFO: Successfully send service information to the Supervisor.
[15:17:44] INFO: Starting mosquitto MQTT broker...
2023-08-04 15:17:44: Warning: Mosquitto should not be run as root/administrator.
...
...
...
... and on it goes....

The I tried the add-on with the watchdog turned off, but still the same, which I thought odd.
Add-on is 6.2.1.

What other relevant info can I supply that would be helpful to track this down?
The fam is upset 'cos the lights aren’t working! :grinning_face_with_smiling_eyes:
Everything was working just fine till the core update.

Thanks!!

Edit - the add-on’s CPU usage seems very high too - about 20% on an Intel NUC??

2

Updated core to 2023.8.1 and the log looks slightly different, but similar:

cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun mosquitto (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
[14:54:49] INFO: Starting NGINX for authentication handling...
s6-rc: info: service legacy-services successfully started
[14:54:49] INFO: Starting mosquitto MQTT broker...
2023-08-05 14:54:49: Warning: Mosquitto should not be run as root/administrator.
[02:54:50] INFO: Service restart after closing
[14:54:51] INFO: Starting mosquitto MQTT broker...
2023-08-05 14:54:51: Warning: Mosquitto should not be run as root/administrator.
[02:54:51] INFO: Service restart after closing
[14:54:52] INFO: Starting mosquitto MQTT broker...
2023-08-05 14:54:52: Warning: Mosquitto should not be run as root/administrator.
[02:54:52] INFO: Service restart after closing
[14:54:53] INFO: Starting mosquitto MQTT broker...
2023-08-05 14:54:53: Warning: Mosquitto should not be run as root/administrator.
[02:54:54] INFO: Service restart after closing
[14:54:55] INFO: Starting mosquitto MQTT broker...
2023-08-05 14:54:55: Warning: Mosquitto should not be run as root/administrator.
[02:54:55] INFO: Service restart after closing
[14:54:56] INFO: Starting mosquitto MQTT broker...
2023-08-05 14:54:56: Warning: Mosquitto should not be run as root/administrator.
...
...
...

Edit NM - this is just because I hadn’t restarted the MQTT specific debug logs.

3

Thanks anyway - just reinstalled the add-on and it’s all good now.
I guess the core update upset it somehow.