После перезагрузки во все устройства отправилась "1"

Программное обеспечение
1

Здравствуйте.
словил следующий баг:
контроллер самостоятельно перезагрузился, до или после перезагрузки во все устройства была отправлена 1.
файл лога во вложении
момент прихода единиц на устройства “19 сент. 2022 г. 11:21:12:000”

" Batch No 6.8.2B/2 557
log_20220919T112138.log (76.5 КБ)

Current uptime

0d 1h 37m

DTS Version

HW Revision

6.8.2

Manufacturing Date

2021-12-23 12:15:32+00:00

Reboot

Release name

wb-2207

Release suite

testing

Short SN

AJVPIIOI

Temperature Grade

industrial"

2

Добрый день.
В приведенном логе вижу:

2022-09-19T08:18:55.663Z [wb-rules] Device "ppp0" does not exist.
2022-09-19T08:18:55.642Z [wb-rules] INFO: network/Wi-Fi 2 IP: failed to convert value '', passing raw
2022-09-19T08:18:55.473Z [wb-rules] INFO: network/Ethernet IP: failed to convert value '', passing raw
2022-09-19T08:18:55.189Z [wb-mqtt-serial] WARNING: [modbus] failed to read 1 holding(s) @ 49999 of device modbus:5: Serial protocol error: malformed response: invalid crc
2022-09-19T08:18:53.915Z [wb-mqtt-serial] WARNING: [modbus] failed to read 5 coil(s) @ 5100 of device modbus:189: Serial protocol error: server device is busy
2022-09-19T08:18:40.730Z [wb-mqtt-serial] WARNING: [modbus] failed to read 5 coil(s) @ 5100 of device modbus:189: Serial protocol error: server device is busy
2022-09-19T08:18:28.995Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr3_29/controls/K3/on : 0
2022-09-19T08:18:28.979Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr3_29/controls/K2/on : 0
2022-09-19T08:18:28.979Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr3_29/controls/K2/on : 0
2022-09-19T08:18:28.970Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr3_29/controls/K1/on : 0
2022-09-19T08:18:28.953Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr3_53/controls/K2/on : 0
2022-09-19T08:18:28.942Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr3_53/controls/K1/on : 0
2022-09-19T08:18:28.931Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr6c_11/controls/K6/on : 0
2022-09-19T08:18:28.921Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr6c_11/controls/K5/on : 0
2022-09-19T08:18:28.911Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr6c_11/controls/K4/on : 0
2022-09-19T08:18:28.893Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr6c_11/controls/K3/on : 0
2022-09-19T08:18:28.871Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr6c_11/controls/K2/on : 0
2022-09-19T08:18:28.866Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr6c_11/controls/K1/on : 0
2022-09-19T08:18:28.866Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr6c_11/controls/K1/on : 0
2022-09-19T08:18:28.859Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr6c_18/controls/K3/on : 0
2022-09-19T08:18:28.854Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr6c_18/controls/K2/on : 0
2022-09-19T08:18:28.848Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr6c_18/controls/K1/on : 0
2022-09-19T08:18:28.838Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr3_24/controls/K3/on : 0
2022-09-19T08:18:28.829Z [nodered] 19 Sep 08:18:28 - [info] [wirenboard-out:afe6b6f1.2a1be8] Published to mqtt topic: /devices/wb-mr3_24/controls/K2/on : 0
2022-09-19T08:18:28.659Z [ssh] Disconnected from 103.38.4.238 port 59376 [preauth]
2022-09-19T08:18:28.655Z [ssh] Received disconnect from 103.38.4.238 port 59376:11: Bye Bye [preauth]
2022-09-19T08:18:28.451Z [ssh] Failed password for invalid user shuo from 103.38.4.238 port 59376 ssh2
2022-09-19T08:18:27.989Z [wb-mqtt-serial] WARNING: [modbus] failed to read 2 holding(s) @ 16009 of device modbus:5: Serial protocol error: malformed response: invalid crc
2022-09-19T08:18:27.989Z [wb-mqtt-serial] WARNING: [modbus] failed to read 2 holding(s) @ 16009 of device modbus:5: Serial protocol error: malformed response: invalid crc
2022-09-19T08:18:27.252Z [wb-mqtt-serial] WARNING: [modbus] failed to read 5 coil(s) @ 5100 of device modbus:189: Serial protocol error: server device is busy
2022-09-19T08:18:26.080Z [ssh] pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.38.4.238
2022-09-19T08:18:26.077Z [ssh] pam_unix(sshd:auth): check pass; user unknown

То есть контроллер с, как видно, установленным NR доступен из интернета? А каким образом обеспечивается безопасность?

4

Установлен пароль на все веб интерфейсы

5

А доступ к MQTT?

6

Нет

7

Нет - доступа?
Из логов видно что в топики пишет NR.

8

без пароля

его запаролить не получилось.
при внесении mosquitto.conf строчки password_file /etc/mosquitto/mosquitto.pwd - сервис не запускается:

root@wirenboard-AJVPIIOI:~# systemctl restart mosquitto
Job for mosquitto.service failed because the control process exited with error code.
See “systemctl status mosquitto.service” and “journalctl -xe” for details.

systemctl status mosquitto.service

● mosquitto.service - Mosquitto MQTT v3.1/v3.1.1 Broker
Loaded: loaded (/lib/systemd/system/mosquitto.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2022-09-20 13:35:08 UTC; 3s ago
Process: 8846 ExecStartPost=/bin/sh -c echo $MAINPID > /var/run/mosquitto.pid (code=exited, status=0/SUCCESS)
Process: 8863 ExecStart=/usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf (code=exited, status=3)
Main PID: 8863 (code=exited, status=3)
Sep 20 13:35:07 wirenboard-AJVPIIOI systemd[1]: mosquitto.service: Unit entered failed state.
Sep 20 13:35:07 wirenboard-AJVPIIOI systemd[1]: mosquitto.service: Failed with result ‘exit-code’.
Sep 20 13:35:08 wirenboard-AJVPIIOI systemd[1]: mosquitto.service: Service hold-off time over, scheduling restart.
Sep 20 13:35:08 wirenboard-AJVPIIOI systemd[1]: Stopped Mosquitto MQTT v3.1/v3.1.1 Broker.
Sep 20 13:35:08 wirenboard-AJVPIIOI systemd[1]: mosquitto.service: Start request repeated too quickly.
Sep 20 13:35:08 wirenboard-AJVPIIOI systemd[1]: Failed to start Mosquitto MQTT v3.1/v3.1.1 Broker.
Sep 20 13:35:08 wirenboard-AJVPIIOI systemd[1]: mosquitto.service: Unit entered failed state.
Sep 20 13:35:08 wirenboard-AJVPIIOI systemd[1]: mosquitto.service: Failed with result ‘exit-code’.

9

Файл /etc/mosquitto/mosquitto.pwd создан без ошибок? То есть у вас сейчас в интернет выставлены как минимум два порта MQTT?

10

пробовал несколько раз, и с форматом, и без формата, в файле видно логин и ключ к нему. У mqtt два порта? проброшен только один.
уже разбираюсь с openvpn…

11

Здравствуйте! Воспроизводится ли проблема?

12

Здравствуйте. mqtt запаролил. проблема пока не наблюдается.

13

Эта тема была автоматически закрыта через 7 дней после последнего ответа. В ней больше нельзя отвечать.