Device Config Update every log interval

This page details the process to troubleshooting when there is a device that is reporting a "Device Config Update" every log interval (e.g. every 5 minutes if the sources run at frequency of 300).

The "Device Config Update" notification usually indicates some change has been made to the configuration of the device, whether it is a new certificate, an additional source added, an old source removed, etc. If this notification is being sent periodically, this usually means there is some error in the device configuration. Below are three areas to check when troubleshooting this issue.

  • Check whether 2 or more scenarios are writing to the same source. This can usually be spotted in Analysis. Otherwise it might show up in e.g. /opt/ardexa/logs/solar/inverter-xy, and you will see duplicate logs (e.g. 2022-11-07.csv and 2022-11-07.csv.1). If this is the case, track down the two run scenarios that are logging to that source and remove the erroneous one.

  • Check agent errors table to see if there is a problem (e.g. EXPECT_ERROR). Make sure that if there is an EXPECT_ERROR that it coincides with the time at which you noticed the issue beginning, because it could be that the EXPECT_ERROR occurs regularly and is not the root cause.

  • Check /opt/ardexa/logs for any unusual logs. It could be that some process is changing what variable is being sent, or what units the variable should be.

Last updated