Ошибки при загрузке

1

Добрый день!
Можете помочь разобраться
Что это за ошибки которые возникают при загрузке WB

28-02-2025 23:05:30.354 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
28-02-2025 23:01:28.902 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
28-02-2025 23:01:28.135 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
28-02-2025 23:01:21.973 [ntp] error resolving pool 3.debian.pool.ntp.org: Name or service not known (-2)
28-02-2025 23:01:20.977 [ntp] error resolving pool 2.debian.pool.ntp.org: Name or service not known (-2)
28-02-2025 23:01:20.178 [NetworkManager] [1740772880.1781] modprobe: ‘/sbin/modprobe --use-blacklist nf_nat_h323’ exited with error 256 (modprobe: FATAL: Module nf_nat_h323 not found in directory /lib/modules/6.8.0-wb124+wb100)
28-02-2025 23:01:20.154 [NetworkManager] [1740772880.1547] modprobe: ‘/sbin/modprobe --use-blacklist nf_nat_pptp’ exited with error 256 (modprobe: FATAL: Module nf_nat_pptp not found in directory /lib/modules/6.8.0-wb124+wb100)
28-02-2025 23:01:20.138 [NetworkManager] [1740772880.1367] modprobe: ‘/sbin/modprobe --use-blacklist nf_nat_tftp’ exited with error 256 (modprobe: FATAL: Module nf_nat_tftp not found in directory /lib/modules/6.8.0-wb124+wb100)
28-02-2025 23:01:20.101 [NetworkManager] [1740772880.1007] modprobe: ‘/sbin/modprobe --use-blacklist nf_nat_sip’ exited with error 256 (modprobe: FATAL: Module nf_nat_sip not found in directory /lib/modules/6.8.0-wb124+wb100)
28-02-2025 23:01:20.072 [NetworkManager] [1740772880.0685] modprobe: ‘/sbin/modprobe --use-blacklist nf_nat_irc’ exited with error 256 (modprobe: FATAL: Module nf_nat_irc not found in directory /lib/modules/6.8.0-wb124+wb100)
28-02-2025 23:01:20.072 [NetworkManager] [1740772880.0685] modprobe: ‘/sbin/modprobe --use-blacklist nf_nat_irc’ exited with error 256 (modprobe: FATAL: Module nf_nat_irc not found in directory /lib/modules/6.8.0-wb124+wb100)
28-02-2025 23:01:20.039 [NetworkManager] [1740772880.0386] modprobe: ‘/sbin/modprobe --use-blacklist nf_nat_ftp’ exited with error 256 (modprobe: FATAL: Module nf_nat_ftp not found in directory /lib/modules/6.8.0-wb124+wb100)
28-02-2025 23:01:19.981 [ntp] error resolving pool 1.debian.pool.ntp.org: Name or service not known (-2)
28-02-2025 23:01:19.704 [wb-mqtt-opcua] ERROR: [main] All groups are disabled, stopping service gracefully
28-02-2025 23:01:19.574 [wb-mqtt-iec104] ERROR: [main] All groups are disabled in config file, stopping service gracefully
28-02-2025 23:01:19.403 [wb-mqtt-mbgate] ERROR: [mbgate] All channels are disabled, stopping service gracefully
28-02-2025 23:01:18.994 [ntp] error resolving pool 0.debian.pool.ntp.org: Name or service not known (-2)
28-02-2025 23:01:18.891 [wpa_supplicant] Using interface wlan0 with hwaddr c8:fe:0f:11:0c:8e and ssid WirenBoard-AJLJGEVR
28-02-2025 23:01:14.790 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
28-02-2025 23:01:14.714 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
28-02-2025 23:01:14.714 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
28-02-2025 23:01:12.665 [bluetooth] sap-server: Operation not permitted (1)
28-02-2025 23:01:12.665 [bluetooth] profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
28-02-2025 23:01:09.235 mdio_bus gpio-1: ethernet-phy has invalid PHY address
28-02-2025 23:01:09.234 mdio_bus gpio-0: ethernet-phy has invalid PHY address
3

Добрый день,

Для диагностики проблемы пришлите, пожалуйста, архив с диагностической информацией контроллера. Инструкцию по созданию архива можно найти в документации.

Судя по логам, зафиксированы следующие ошибки:

nl80211: kernel reports: Authentication algorithm number required
bgscan simple: Failed to enable signal strength monitoring
  • “Authentication algorithm number required” — проблема с алгоритмом аутентификации. Возможно, точка доступа требует другой метод шифрования.
  • “Failed to enable signal strength monitoring” — невозможность мониторинга сигнала Wi-Fi.
error resolving pool X.debian.pool.ntp.org: Name or service not known (-2)
  • Ошибка указывает на проблемы с DNS или интернет-соединением, так как не удаётся разрешить домены debian.pool.ntp.org.

Наиболее вероятные причины и рекомендации:

  1. Wi-Fi — Проверьте параметры шифрования сети.
  2. DNS / Интернет — Убедитесь, что контроллер имеет выход в интернет и может резолвить NTP-серверы.
  3. Обновление прошивки — Рекомендую обновиться на актуальную версию прошивки контроллера.
4

Добрый день! Еще раз. Архив приложил.
Отключил Wifi точку доступа , часть ошибок ушла.
Однако если делать все по инструкции один из вариантов получения Сборщик данных для диагностики через UI , но он не работает. Получить архив только получилась через подключение SSH.

приложен диагностический архив, доступен только сотрудникам поддержки
(390,4 КБ)

03-03-2025 21:28:20.085 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
03-03-2025 21:28:19.178 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
03-03-2025 21:28:12.129 [ntp] error resolving pool 3.debian.pool.ntp.org: Name or service not known (-2)
03-03-2025 21:28:11.110 [ntp] error resolving pool 2.debian.pool.ntp.org: Name or service not known (-2)
03-03-2025 21:28:10.113 [ntp] error resolving pool 1.debian.pool.ntp.org: Name or service not known (-2)
03-03-2025 21:28:09.877 [wb-mqtt-opcua] ERROR: [main] All groups are disabled, stopping service gracefully
03-03-2025 21:28:09.809 [wb-mqtt-iec104] ERROR: [main] All groups are disabled in config file, stopping service gracefully
03-03-2025 21:28:09.392 [wb-mqtt-mbgate] ERROR: [mbgate] All channels are disabled, stopping service gracefully
03-03-2025 21:28:09.136 [ntp] error resolving pool 0.debian.pool.ntp.org: Name or service not known (-2)
03-03-2025 21:28:04.958 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
03-03-2025 21:28:04.958 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
03-03-2025 21:28:04.883 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
03-03-2025 21:28:02.763 [bluetooth] sap-server: Operation not permitted (1)
03-03-2025 21:28:02.763 [bluetooth] profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
03-03-2025 21:27:59.284 mdio_bus gpio-1: ethernet-phy has invalid PHY address
03-03-2025 21:27:59.283 mdio_bus gpio-0: ethernet-phy has invalid PHY address

приложен диагностический архив, доступен только сотрудникам поддержки
(390,4 КБ)

6

Сборщик через UI не работает , а просто крутиться уже 7 минут

На изображении показан интерфейс с кнопками для скачивания архивов, конфигурационных файлов и сбора данных для диагностики. (Captioned by AI)
На изображении показан интерфейс с кнопками для скачивания архивов, конфигурационных файлов и сбора данных для диагностики. (Captioned by AI)2882×565 31.9 KB

7

Добрый день,

Попробуйте выполнить обновление командой:

apt update && apt upgrade -y

Часть ошибок должна исчезнуть. Сообщите о результате.

8

Остались следующие ошибки

04-03-2025 22:53:51.036 [ntp] unable to create socket on wlan1 (6) for fe80::18f:ee5a:9ee2:d008%5#123
04-03-2025 22:53:51.035 [ntp] bind(24) AF_INET6 fe80::18f:ee5a:9ee2:d008%5#123 flags 0x11 failed: Cannot assign requested address
04-03-2025 22:53:49.036 [ntp] unable to create socket on wlan1 (5) for fe80::18f:ee5a:9ee2:d008%5#123
04-03-2025 22:53:49.036 [ntp] bind(24) AF_INET6 fe80::18f:ee5a:9ee2:d008%5#123 flags 0x11 failed: Cannot assign requested address
04-03-2025 22:53:47.436 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
04-03-2025 22:53:46.226 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
04-03-2025 22:53:46.037 [ntp] error resolving pool 3.debian.pool.ntp.org: Name or service not known (-2)
04-03-2025 22:53:45.035 [ntp] error resolving pool 2.debian.pool.ntp.org: Name or service not known (-2)
04-03-2025 22:53:44.035 [ntp] error resolving pool 1.debian.pool.ntp.org: Name or service not known (-2)
04-03-2025 22:53:43.645 [wb-mqtt-opcua] ERROR: [main] All groups are disabled, stopping service gracefully
04-03-2025 22:53:43.645 [wb-mqtt-opcua] ERROR: [main] All groups are disabled, stopping service gracefully
04-03-2025 22:53:43.492 [wb-mqtt-iec104] ERROR: [main] All groups are disabled in config file, stopping service gracefully
04-03-2025 22:53:43.322 [wb-mqtt-mbgate] ERROR: [mbgate] All channels are disabled, stopping service gracefully
04-03-2025 22:53:43.103 [ntp] error resolving pool 0.debian.pool.ntp.org: Name or service not known (-2)
04-03-2025 22:53:38.843 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
04-03-2025 22:53:38.773 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
04-03-2025 22:53:36.703 [bluetooth] sap-server: Operation not permitted (1)
04-03-2025 22:53:36.702 [bluetooth] profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
04-03-2025 22:53:33.156 mdio_bus gpio-1: ethernet-phy has invalid PHY address
04-03-2025 22:53:33.155 mdio_bus gpio-0: ethernet-phy has invalid PHY address
04-03-2025 22:53:33.155 mdio_bus gpio-0: ethernet-phy has invalid PHY address

На изображении показан экран командной строки с выводом информации о системе и процессе обновления пакетов в операционной системе Linux, основанной на Debian. (Captioned by AI)
На изображении показан экран командной строки с выводом информации о системе и процессе обновления пакетов в операционной системе Linux, основанной на Debian. (Captioned by AI)2410×1408 210 KB

приложен диагностический архив, доступен только сотрудникам поддержки
(404,9 КБ)

10

Добрый день!

Оставшиеся ошибки, насколько я вижу, не критичны, так как возникают только при запуске системы, и это нормально.

Из рекомендуемых проверок советую обратить внимание на следующую ошибку:
error resolving pool 1.debian.pool.ntp.org: Name or service not known (-2)

Проверьте, стабильно ли работает интернет и служба DNS.

Есть ли какие-то признаки сбоев в работе контроллера? Или ошибки появляются только в начале загрузки?

11

Добрый день,
Удалось ли решить вопрос?

12

Интернет работает стабильно и без проблем.
А ошибки частота не проверял. К сожалению в последние пару будних дней болел и было не до проверки. На выходных посмотрю.

13

Добрый день, ожидаю обратной связи.

14

Вот перечень всех ошибок . Устройство работало без выключения 22 часа

09-03-2025 12:14:13.542 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
09-03-2025 12:14:12.759 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
09-03-2025 08:02:08.801 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
09-03-2025 08:02:07.943 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
09-03-2025 01:44:31.346 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
09-03-2025 01:44:30.498 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
08-03-2025 17:00:28.178 [wb-rules] ERROR: [wbgo_mqtt] MQTT token wait timeout: *mqtt.PublishToken (&{{{{0 0} 0 0 {{} 0} {{} 0}} 0x400055a8a0 } 210})
08-03-2025 17:00:18.177 [wb-rules] ERROR: [wbgo_mqtt] MQTT token wait timeout: *mqtt.PublishToken (&{{{{0 0} 0 0 {{} 0} {{} 0}} 0x40004f6c00 } 209})
08-03-2025 17:00:08.176 [wb-rules] ERROR: [wbgo_mqtt] MQTT token wait timeout: *mqtt.PublishToken (&{{{{0 0} 0 0 {{} 0} {{} 0}} 0x40004f6ba0 } 208})
08-03-2025 16:59:58.173 [wb-rules] ERROR: [wbgo_mqtt] MQTT token wait timeout: *mqtt.PublishToken (&{{{{0 0} 0 0 {{} 0} {{} 0}} 0x40001e85a0 } 207})
08-03-2025 16:59:58.173 [wb-rules] ERROR: [wbgo_mqtt] MQTT token wait timeout: *mqtt.PublishToken (&{{{{0 0} 0 0 {{} 0} {{} 0}} 0x40001e85a0 } 207})
08-03-2025 16:59:48.882 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
08-03-2025 16:59:47.678 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
08-03-2025 16:59:47.430 [ntp] error resolving pool 3.debian.pool.ntp.org: Name or service not known (-2)
08-03-2025 16:59:46.432 [ntp] error resolving pool 2.debian.pool.ntp.org: Name or service not known (-2)
08-03-2025 16:59:45.428 [ntp] error resolving pool 1.debian.pool.ntp.org: Name or service not known (-2)
08-03-2025 16:59:45.089 [wb-mqtt-iec104] ERROR: [main] All groups are disabled in config file, stopping service gracefully
08-03-2025 16:59:45.074 [wb-mqtt-opcua] ERROR: [main] All groups are disabled, stopping service gracefully
08-03-2025 16:59:44.797 [wb-mqtt-mbgate] ERROR: [mbgate] All channels are disabled, stopping service gracefully
08-03-2025 16:59:44.705 [wb-mqtt-iec104] ERROR: [mqtt] loop_stop error: MOSQ_ERR_INVAL
08-03-2025 16:59:44.705 [wb-mqtt-iec104] ERROR: [mqtt] loop_stop error: MOSQ_ERR_INVAL
08-03-2025 16:59:44.705 [wb-mqtt-iec104] ERROR: [mqtt] disconnect error: MOSQ_ERR_NO_CONN
08-03-2025 16:59:44.456 [ntp] error resolving pool 0.debian.pool.ntp.org: Name or service not known (-2)
08-03-2025 16:59:40.267 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
08-03-2025 16:59:40.201 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
08-03-2025 16:59:38.081 [bluetooth] sap-server: Operation not permitted (1)
08-03-2025 16:59:38.081 [bluetooth] profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
08-03-2025 16:59:34.277 mdio_bus gpio-1: ethernet-phy has invalid PHY address
08-03-2025 16:59:34.276 mdio_bus gpio-0: ethernet-phy has invalid PHY address

15

Добрый день!
Прошу прислать новый архив с диагностической информацией контроллера. Создание архива описано в документации.

16

Скидываю новый архив.
Интернет работает без проблем. Лог ошибок также прилагаю.

приложен диагностический архив, доступен только сотрудникам поддержки
(420,2 КБ)
log_20250309T121413.log (3,2 КБ)

18

Также хочется отметить , что указанные способы получения диагностического архива не работают. Архив можно получить только через терминал, а вот через User Interface эта штука не работает.

19

Прилагаю самый новый отчет.
Устройство работало 5 дней без выключения.
Ошибки новые появляются каждый день.

13-03-2025 18:14:46.650 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
13-03-2025 18:14:45.749 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
12-03-2025 12:03:49.912 [ntp] unable to create socket on wlan1 (22) for fe80::18f:ee5a:9ee2:d008%5#123
12-03-2025 12:03:49.911 [ntp] bind(23) AF_INET6 fe80::18f:ee5a:9ee2:d008%5#123 flags 0x11 failed: Cannot assign requested address
12-03-2025 12:03:48.723 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
12-03-2025 12:03:47.843 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
12-03-2025 07:21:28.466 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
12-03-2025 07:21:27.666 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
11-03-2025 19:49:28.527 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
11-03-2025 19:49:27.681 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
11-03-2025 19:49:27.681 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
11-03-2025 16:40:41.124 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
11-03-2025 16:40:40.309 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
11-03-2025 12:29:27.179 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
11-03-2025 12:29:25.449 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
10-03-2025 11:18:20.781 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
10-03-2025 11:18:19.972 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
09-03-2025 12:14:13.542 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
09-03-2025 12:14:12.759 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
09-03-2025 08:02:08.801 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
09-03-2025 08:02:08.801 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
09-03-2025 08:02:07.943 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
09-03-2025 01:44:31.346 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
09-03-2025 01:44:30.498 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
08-03-2025 17:00:28.178 [wb-rules] ERROR: [wbgo_mqtt] MQTT token wait timeout: *mqtt.PublishToken (&{{{{0 0} 0 0 {{} 0} {{} 0}} 0x400055a8a0 } 210})
08-03-2025 17:00:18.177 [wb-rules] ERROR: [wbgo_mqtt] MQTT token wait timeout: *mqtt.PublishToken (&{{{{0 0} 0 0 {{} 0} {{} 0}} 0x40004f6c00 } 209})
08-03-2025 17:00:08.176 [wb-rules] ERROR: [wbgo_mqtt] MQTT token wait timeout: *mqtt.PublishToken (&{{{{0 0} 0 0 {{} 0} {{} 0}} 0x40004f6ba0 } 208})
08-03-2025 16:59:58.173 [wb-rules] ERROR: [wbgo_mqtt] MQTT token wait timeout: *mqtt.PublishToken (&{{{{0 0} 0 0 {{} 0} {{} 0}} 0x40001e85a0 } 207})
08-03-2025 16:59:48.882 [wpa_supplicant] bgscan simple: Failed to enable signal strength monitoring
08-03-2025 16:59:47.678 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
08-03-2025 16:59:47.678 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
08-03-2025 16:59:47.430 [ntp] error resolving pool 3.debian.pool.ntp.org: Name or service not known (-2)
08-03-2025 16:59:46.432 [ntp] error resolving pool 2.debian.pool.ntp.org: Name or service not known (-2)
08-03-2025 16:59:45.428 [ntp] error resolving pool 1.debian.pool.ntp.org: Name or service not known (-2)
08-03-2025 16:59:45.089 [wb-mqtt-iec104] ERROR: [main] All groups are disabled in config file, stopping service gracefully
08-03-2025 16:59:45.074 [wb-mqtt-opcua] ERROR: [main] All groups are disabled, stopping service gracefully
08-03-2025 16:59:44.797 [wb-mqtt-mbgate] ERROR: [mbgate] All channels are disabled, stopping service gracefully
08-03-2025 16:59:44.705 [wb-mqtt-iec104] ERROR: [mqtt] loop_stop error: MOSQ_ERR_INVAL
08-03-2025 16:59:44.705 [wb-mqtt-iec104] ERROR: [mqtt] disconnect error: MOSQ_ERR_NO_CONN
08-03-2025 16:59:44.456 [ntp] error resolving pool 0.debian.pool.ntp.org: Name or service not known (-2)
08-03-2025 16:59:44.456 [ntp] error resolving pool 0.debian.pool.ntp.org: Name or service not known (-2)
08-03-2025 16:59:40.267 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
08-03-2025 16:59:40.201 [wpa_supplicant] nl80211: kernel reports: Authentication algorithm number required
08-03-2025 16:59:38.081 [bluetooth] sap-server: Operation not permitted (1)
08-03-2025 16:59:38.081 [bluetooth] profiles/sap/server.c:sap_server_register() Sap driver initialization failed.
08-03-2025 16:59:34.277 mdio_bus gpio-1: ethernet-phy has invalid PHY address
08-03-2025 16:59:34.276 mdio_bus gpio-0: ethernet-phy has invalid PHY address
[diag_AJLJGEVR_2025-03-13-22.16.20.zip attachment](upload://xAh9Aqj4PWBVOcjD5vod61JRiRL.zip) (453,9 КБ)
21

Добрый день!

Благодарю за предоставленный лог, проанализируем его с коллегами.