Добрый день! Вчера получили контроллер WirenBoard 6 hw: 6.9.1U/1G s/n: A7GZNFZ4.
Сразу решили его потестировать, у нас уже был WB 6.7, софт пишем на MasterScada, поэтому уже было что залить.
Для начала поставили в контроллер исполнительную систему MasterScada и залили софт.
Контроллер сразу не отдавал данные на верх по modbus tcp поэтому полезли в WebUI и сразу заметили странности:
- В Rules удалось зайти всего один раз
- System-> Configs сначала долго думает и потом не показывает с ошибкой Cannot load WebUI config.: MQTT RPC request timed out MqttTimeoutError
- Нет демо дашбордов
- Раздел Devices урезан
Обновляли последними прошивками от 0909 и 1209(сегодня попробовал) через USB с различными флешками и web.
При установке версии 2204 вообще контроллер не загружается и пишет ошибку MMC памяти.
На последних прошивках стабильно часть сервисов не может стартануть, такое чувство что память в read only встала.
Попробовал на journal, на остальных сервисах похожие ошибки по недоступности файлов или директорий:
root@wirenboard-A7GZNFZ4:~# systemctl list-units --type=service
UNIT LOAD ACTIVE SUB DESCRIPTION
avahi-daemon.service loaded active running Avahi mDNS/DNS-SD Stack
bluetooth.service loaded active running Bluetooth service
cgmanager.service loaded active running Cgroup management daemon
cron.service loaded active running Regular background progra
dbus.service loaded active running D-Bus System Message Bus
dnsmasq.service loaded active running dnsmasq - A lightweight D
getty@tty1.service loaded active running Getty on tty1
hostapd.service loaded active running LSB: Advanced IEEE 802.11
ifup@eth0.service loaded active exited ifup for eth0
ifup@eth1.service loaded active exited ifup for eth1
ifup@wlan0.service loaded active exited ifup for wlan0
kmod-static-nodes.service loaded active exited Create list of required s
knxd.service loaded active running KNX Daemon
mosquitto.service loaded active running Mosquitto MQTT v3.1/v3.1.
netplug.service loaded active running LSB: Brings up/down netwo
networking.service loaded active exited Raise network interfaces
nginx.service loaded active running A high performance web se
ntp.service loaded active running LSB: Start NTP daemon
rsyslog.service loaded active running System Logging Service
serial-getty@ttymxc0.service loaded active running Serial Getty on ttymxc0
ssh.service loaded active running OpenBSD Secure Shell serv
systemd-fsck-root.service loaded active exited File System Check on Root
systemd-fsck@dev-mmcblk0p6.service loaded active exited File System Check on
● systemd-journald.service loaded failed failed Journal Service
systemd-logind.service loaded active running Login Service
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 F
systemd-sysctl.service loaded active exited Apply Kernel Variables
● systemd-tmpfiles-clean.service loaded failed failed Cleanup of Temporary Dire
● systemd-tmpfiles-setup-dev.service loaded failed failed Create Static Device
● systemd-tmpfiles-setup.service loaded failed failed Create Volatile Files and
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manage
systemd-update-utmp.service loaded active exited Update UTMP about System
systemd-user-sessions.service loaded active exited Permit User Sessions
user@0.service loaded active running User Manager for UID 0
watchdog.service loaded active running watchdog daemon
wb-configs-early.service loaded active exited prepare mounts and symlin
wb-configs.service loaded active running watch config files
wb-diag-collect.service loaded active running one-click diagnostic data
wb-gsm-rtc-restore.service loaded active exited Restore local date from W
wb-hwconf-manager.service loaded active exited Initialize Wiren Board De
wb-init.service loaded active exited Initialize Wiren Board on
wb-knxd-config.service loaded active exited KNXD Configurator for Wir
wb-mqtt-adc.service loaded active running MQTT Driver for ADC
● wb-mqtt-confed.service loaded failed failed Wiren Board configuration
wb-mqtt-db.service loaded active running Wiren Board database logg
wb-mqtt-gpio.service loaded active running MQTT Driver for GPIO-cont
wb-mqtt-knx.service loaded active running Wiren Board MQTT KNX brid
wb-mqtt-logs.service loaded active running Wiren Board journald to M
wb-mqtt-mbgate.service loaded active running Wiren Board MQTT to Modbu
wb-mqtt-metrics.service loaded active running metrics sender.
wb-mqtt-opcua.service loaded active running Wiren Board MQTT to OPC U
wb-mqtt-w1.service loaded active running Kernel 1-Wire MQTT driver
wb-prepare.service loaded active exited initialize filesystems at
wb-repart.service loaded active exited prepare partitions at fir
● wb-rules.service loaded failed failed MQTT Rule engine for Wire
wb-watch-update.service loaded active running Wiren Board firmware upda
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.
59 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use ‘systemctl list-unit-files’.
root@wirenboard-A7GZNFZ4:~# systemctl start systemd-journald.service
[ 2672.404910] systemd[1]: Listening on Journal Socket (/dev/log).
[ 2672.417348] systemd[1]: Listening on Journal Socket.
[ 2672.433407] systemd[1]: Starting Journal Service…
[ 2672.489005] systemd-journald[11223]: Failed to open runtime journal: No such file or directory
[ 2672.501138] systemd[1]: systemd-journald.service: Main process exited, code=exited, status=1/FAILURE
[ 2672.525320] systemd[1]: Failed to start Journal Service.
[ 2672.541643] systemd[1]: systemd-journald.service: Unit entered failed state.
[ 2672.549444] systemd[1]: systemd-journald.service: Failed with result ‘exit-code’.
[ 2672.598151] systemd[1]: systemd-journald.service: Service has no hold-off time, scheduling restart.
Job for systemd-journald.service failed because the control process exited with error code.
See “systemctl status systemd-journald.service” and “journalctl [ 2672.623344] systemd[1]: Stopped Journal Service.
-xe” for details.
[ 2672.635547] systemd[1]: Starting Journal Service…
root@wirenboard-A7GZNFZ4:~# [ 2672.690206] systemd-journald[11225]: Failed to open runtime journal: No such file or directory
[ 2672.812140] systemd-journald[11227]: Failed to open runtime journal: No such file or directory
[ 2672.932938] systemd-journald[11229]: Failed to open runtime journal: No such file or directory
[ 2673.052553] systemd-journald[11231]: Failed to open runtime journal: No such file or directory