| Fixed the issue of page exit during upgrade on local O&M system. |
When using local O&M system to upgrade,there is lower probability of page logout in upgrade progress cannot be seen. Cannot login again until the upgrade is successful. During the upgrade process to versions 2.4.6.002 and above,the upgrade progress will be displayed until restarted after success. |
lower incidence |
If Need to frequently use local O&M system for upgrade,it is recommended to upgrade to version 2.4.6.002 and above.Other upgrade scenarios are not affected. |
| Fixed the issue of multiple time synchronization processes |
Moxa that have deployed version 2.3.0 or 2.3.0.001 will perform multiple time synchronizations at the same time during subsequent use,consuming a certain amount of traffic. |
Moxa that have been deployed with version 2.3.0 or 2.3.0.001 will definitely appear. other hardware is not affected. Offline scenarios are not affected. |
Moxa recommends upgrading,Other hardware is not affected. |
| Fixed the issue of DTUA system service systemd-hwdb disk crash |
The DTUA machine will execute systemd-hwdb update when it starts. When an abnormal interruption (power off) occurs,a dirty file will be generated. If it occurs frequently,the disk will be damaged. |
The probability is low and mainly occurs in scenarios with frequent power outages |
DTUA recommends upgrading,Other hardware is not affected. |
| Fixed the issue where inode damage in the DTUA file system cannot be automatically repaired. |
When the inode is damaged due to a power outage,the DTUA machine cannot forcibly repair the inode,and the system will enter initramfs and cannot login. |
The probability is low and mainly occurs in scenarios with frequent power outages. |
DTUA recommends upgrading,Other hardware is not affected. |
| Fixed an issue where resource packages were abnormal after frequently deleting devices,causing all sub-devices to go offline. |
After frequently deleting sub-devices,the resource package will package and release invalid devices to the device. During the batch online process of sub-devices,invalid devices were not processed,and the cloud directly returned a login failure,causing all sub-devices to fail to go online. |
It will occur when sub-devices are frequently deleted,but the occurrence rate is low. |
It does not affect data collection,but offline can cause misleading. It is recommended to upgrade. The stable environment is not affected. |