Перестал работать веб. интерфейс и mosquitto после отключения электричества

Добрый день!
Сработало УЗО и перестали работать все устройства. Порты RS1 и RS2 питание не выдают, модули работают. Перекинул питание на ИП, все устройства видит и работают.
На контроллере установлено дополнительно ПО Bary.

Перестал работать веб. интерфейс:
Не удалось подключиться к wss://apj7tqyp.http.wirenboard.cloud/mqtt

Перестал работать москито:
root@wirenboard-APJ7TQYP:~# systemctl status mosquitto.service
● mosquitto.service - Mosquitto MQTT Broker
Loaded: loaded (/lib/systemd/system/mosquitto.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/mosquitto.service.d
└─override.conf
Active: failed (Result: exit-code) since Tue 2025-07-22 11:24:18 UTC; 5min ago
Docs: man:mosquitto.conf(5)
man:mosquitto(8)
Process: 2165 ExecStartPre=/bin/mkdir -m 740 -p /var/log/mosquitto (code=exited, status=0/SUCCESS)
Process: 2178 ExecStartPre=/bin/chown mosquitto:mosquitto /var/log/mosquitto (code=exited, status=0/SUCCESS)
Process: 2183 ExecStartPre=/bin/mkdir -m 740 -p /run/mosquitto (code=exited, status=0/SUCCESS)
Process: 2189 ExecStartPre=/bin/chown mosquitto:mosquitto /run/mosquitto (code=exited, status=0/SUCCESS)
Process: 2193 ExecStartPre=/bin/chown mosquitto:mosquitto /run/mosquitto (code=exited, status=0/SUCCESS)
Process: 2201 ExecStartPre=/bin/chmod g+x /run/mosquitto (code=exited, status=0/SUCCESS)
Process: 2204 ExecStart=/usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf (code=exited, status=3)
Main PID: 2204 (code=exited, status=3)
CPU: 152ms

Jul 22 11:24:18 wirenboard-APJ7TQYP systemd[1]: mosquitto.service: Scheduled restart job, restart counter is at 5.
Jul 22 11:24:18 wirenboard-APJ7TQYP systemd[1]: Stopped Mosquitto MQTT Broker.
Jul 22 11:24:18 wirenboard-APJ7TQYP systemd[1]: mosquitto.service: Start request repeated too quickly.
Jul 22 11:24:18 wirenboard-APJ7TQYP systemd[1]: mosquitto.service: Failed with result ‘exit-code’.
Jul 22 11:24:18 wirenboard-APJ7TQYP systemd[1]: Failed to start Mosquitto MQTT Broker.

Диагностический архив смогу подгрузить вечером…

Добрый день.
Проверьте пожалуйста - не включен ли в конфиге mosquitto persistance true/
Если да - выключите (измените на false).
Но без логов и точной версии ПО - это предположение.

Place your local configuration in /etc/mosquitto/conf.d/

A full description of the configuration file is at

/usr/share/doc/mosquitto/examples/mosquitto.conf.example

listener 1883 0.0.0.0
allow_anonymous true

pid_file /run/mosquitto/mosquitto.pid

# # # # # # # # # # # # # # persistence is disabled by default. enable in /etc/mosquitto/conf.d/000persistence.conf

persistence_location /var/lib/mosquitto/

log_dest syslog

include_dir /usr/share/wb-configs/mosquitto
include_dir /etc/mosquitto/conf.d

Это если смотреть по сервисам
oot@wirenboard-APJ7TQYP:~# systemctl list-units --type=service
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
avahi-daemon.service loaded active running Avahi mDNS/DNS-SD Stack
bary.service loaded active running bary
bluetooth.service loaded active running Bluetooth service
cron.service loaded active running Regular background program processing daemon
dbus.service loaded active running D-Bus System Message Bus
● fstrim.service loaded failed failed Discard unused blocks on filesystems from /etc/fstab
getty@tty1.service loaded active running Getty on tty1
ifupdown-pre.service loaded active exited Helper to synchronize boot up for ifupdown
kmod-static-nodes.service loaded active exited Create list of static device nodes for the current kernel
knxd.service loaded active running KNX Daemon
ModemManager.service loaded active running Modem Manager
● mosquitto.service loaded failed failed Mosquitto MQTT Broker
netplug.service loaded active running LSB: Brings up/down network automatically
networking.service loaded active exited Raise network interfaces
NetworkManager-wait-online.service loaded active exited Network Manager Wait Online
NetworkManager.service loaded active running Network Manager
nginx.service loaded active running A high performance web server and a reverse proxy server
ntp.service loaded active running Network Time Service
polkit.service loaded active running Authorization Manager
serial-getty@ttyS0.service loaded active running Serial Getty on ttyS0
ssh.service loaded active running OpenBSD Secure Shell server
systemd-fsck-root.service loaded active exited File System Check on Root Device
systemd-fsck@dev-mmcblk0p6.service loaded active exited File System Check on /dev/mmcblk0p6
systemd-journal-flush.service loaded active exited Flush Journal to Persistent Storage
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running User Login Management
systemd-modules-load.service loaded active exited Load Kernel Modules
systemd-random-seed.service loaded active exited Load/Save Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-sysusers.service loaded active exited Create System Users
systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories
systemd-udev-trigger.service loaded active exited Coldplug All udev Devices
systemd-udevd.service loaded active running Rule-based Manager for Device Events and Files
systemd-update-utmp.service loaded active exited Update UTMP about System Boot/Shutdown
systemd-user-sessions.service loaded active exited Permit User Sessions
user-runtime-dir@0.service loaded active exited User Runtime Directory /run/user/0
user@0.service loaded active running User Manager for UID 0
watchdog.service loaded active running watchdog daemon
wb-cloud-agent-frpc.service loaded active running fast reverse proxy client for Wiren Board Cloud (default)
● wb-cloud-agent-telegraf.service loaded failed failed telegraf metric sender for Wiren Board Cloud (default)
wb-cloud-agent.service loaded active running Wiren Board Cloud Agent (default)
wb-configs-early.service loaded active exited prepare mounts and symlinks to config files
wb-configs.service loaded active running watch config files
wb-connection-manager.service loaded active running Network connections management service for Wiren Board devices
wb-device-manager.service loaded active running Wiren Board modbus devices manager
wb-hwconf-manager.service loaded active exited Initialize Wiren Board Device Tree overlays
wb-init.service loaded active exited Initialize Wiren Board on successful boot
wb-knxd-config.service loaded active exited KNXD Configurator for Wiren Board
wb-mqtt-adc.service loaded activating start-pre start MQTT Driver for ADC
● wb-mqtt-confed.service loaded failed failed Wiren Board configuration editor backend
● wb-mqtt-db.service loaded failed failed Wiren Board database logger
● wb-mqtt-gpio.service loaded failed failed MQTT Driver for GPIO-controlled switches
● wb-mqtt-iec104.service loaded failed failed Wiren Board MQTT to IEC 60870-5-104 gateway
● wb-mqtt-logs.service loaded failed failed Wiren Board journald to MQTT gateway
wb-mqtt-metrics.service loaded active running metrics sender
● wb-mqtt-nm-helper.service loaded failed failed Virtual MQTT devices management service for Network Manager connections
● wb-mqtt-opcua.service loaded failed failed Wiren Board MQTT to OPC UA gateway
wb-mqtt-w1.service loaded activating auto-restart Kernel 1-Wire MQTT driver for WB-HomA
wb-systime-adjust.service loaded active exited Compensation of systime in PPM from value, stored in device-tree (with opposite sign)
wb-usb-otg.service loaded active exited USB Debug Network
wb-watch-update.service loaded active running Wiren Board firmware update service
wpa_supplicant.service loaded active running WPA supplicant

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.

64 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use ‘systemctl list-unit-files’.
(дополнительно прикреплю скрин)

Плюс подскажите, как сделать диагностический файл через SSH. Не могу команду найти.
Если скажите, как выяснить версию ПО, то направлю

Создание архива описано в документации.

diag_APJ7TQYP_2025-07-22-17.53.54.zip (306,1 КБ)

Jul 22 17:27:09 wirenboard-APJ7TQYP mosquitto[6313]: 1753205229: Error: per_listener_settings must be set before any other security settings.
Jul 22 17:27:09 wirenboard-APJ7TQYP mosquitto[6313]: 1753205229: Error found at /etc/mosquitto/conf.d/00default_listener.conf:11.
Jul 22 17:27:09 wirenboard-APJ7TQYP mosquitto[6313]: 1753205229: Error found at /etc/mosquitto/mosquitto.conf:17.

А именно mosquitto.conf
Зачем там описан listner?
То есть - почему в этом конфиге и для какой цели с такими параметрами? Ну, скорее всего кто-то добавил некорректные записи с момента прошлого запуска, с 23 февраля.

Добавляли, так как в Bary не подтягивался mosquitto и не модуль зигби.
Все работало. Перестало после отключения электричество. Пропало питание с портов…

Советую привести к обычному виду. И - вот так добавленное - неверно принципиально. И никакого влияния не могло оказывать на запущенном сервисе. А уже перезапуск - не удался бы (ну, так и произошло).

Можете направить стандартный конфиг?

Вот он:

# Place your local configuration in /etc/mosquitto/conf.d/
#
# A full description of the configuration file is at
# /usr/share/doc/mosquitto/examples/mosquitto.conf.example

pid_file /run/mosquitto/mosquitto.pid

# # # persistence is disabled by default. enable in /etc/mosquitto/conf.d/000persistence.conf
persistence_location /var/lib/mosquitto/

log_dest syslog

include_dir /usr/share/wb-configs/mosquitto
include_dir /etc/mosquitto/conf.d


Добрый вечер!
Корректировка помогла запустить веб интерфейс и датчики (питание на портах), но не работает модуль Ригби в приложении Bary, как я понимаю, нужно куда-то вставить:
listener 1883 0.0.0.0
allow_anonymous true

Вопрос только куда?

Получился конфликт в двух конфигах. по итогу все работает. Два раза запрос на порт 1883 был

Ну отлично, рад.