You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With an update to version 19.0 we get a ton of err32 flags in the data and corresponding (s. below) entries in the openmuc.log
Action was scheduled for UNIX time 1636990999200. But current time is already 1636991000302. Will calculate new action time because the action has timed out. Has the system clock jumped?
The server is not under any load at all during these loggings. The meters are pulled every 200ms via modbus driver, which worked fine under 18.1. Downgrading to 18.1. solved the issue.
Any ideas?
The text was updated successfully, but these errors were encountered:
With an update to version 19.0 we get a ton of err32 flags in the data and corresponding (s. below) entries in the openmuc.log
Action was scheduled for UNIX time 1636990999200. But current time is already 1636991000302. Will calculate new action time because the action has timed out. Has the system clock jumped?The server is not under any load at all during these loggings. The meters are pulled every 200ms via modbus driver, which worked fine under 18.1. Downgrading to 18.1. solved the issue.
Any ideas?
The text was updated successfully, but these errors were encountered: