IotaWatt rebooting every 60 odd seconds

Support
1

Morning Folks,

I have two Iotawatts in operation. Both have worked flawlessly for some months until about two weeks ago.
One is now rebooting every 60 seconds or so with the log entry below repeated with each. I see the reason being “Software Watchdog” but what is causing this and how do I fix it?

Thanks, Mike

** Restart **

SD initialized.
10/31/19 12:05:21z Real Time Clock is running. Unix time 1572523521
10/31/19 12:05:21z Reset reason: Software Watchdog
10/31/19 12:05:21z Trace: 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:1[5], 1:2[6], 9:0[6], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 10:13, 1:4, 1:5[14], 14:0, 14:1, 14:2
10/31/19 12:05:21z ESP8266 ChipID: 6910477
10/31/19 12:05:21z IoTaWatt 4.x, Firmware version 02_05_01
10/31/19 12:05:21z SPIFFS mounted.
10/31/19 08:05:22 Local time zone: -5:00
10/31/19 08:05:22 Using Daylight Saving Time (BST) when in effect.
10/31/19 08:05:22 device name: IotaWat2
10/31/19 08:05:22 MDNS responder started for hostname IotaWat2
10/31/19 08:05:22 LLMNR responder started for hostname IotaWat2
10/31/19 08:05:22 HTTP server started
10/31/19 08:05:22 WiFi connected. SSID=XXXXXXXX, IP=192.168.200.170, channel=11, RSSI -59db
10/31/19 08:05:22 timeSync: service started.
10/31/19 08:05:23 statService: started.
10/31/19 08:05:23 Updater: service started. Auto-update class is ALPHA
10/31/19 08:05:23 dataLog: service started.
10/31/19 08:05:23 dataLog: Last log entry 10/31/19 08:05:15
10/31/19 08:05:24 Updater: Auto-update is current for class ALPHA.
10/31/19 08:05:27 EmonService: started. url:80=emoncms.org, node=IotaWat2, interval=10, encrypted
10/31/19 08:05:28 EmonService: Start posting at 10/31/19 08:05:20
10/31/19 08:06:23 historyLog: service started.
10/31/19 08:06:23 historyLog: first entry 09/16/19 08:43:00

** Restart **

SD initialized.
10/31/19 12:06:27z Real Time Clock is running. Unix time 1572523587
10/31/19 12:06:27z Reset reason: Software Watchdog
10/31/19 12:06:27z Trace: 10:14, 10:14, 10:15, 10:16, 10:16[1], 10:16[1], 10:16[1], 10:16[2], 10:17, 10:22, 10:23, 10:17, 1:4, 1:1[8], 1:2[9], 9:0[9], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 1:4, 1:5[14], 14:0, 14:1, 14:2
10/31/19 12:06:27z ESP8266 ChipID: 6910477
10/31/19 12:06:27z IoTaWatt 4.x, Firmware version 02_05_01
10/31/19 12:06:27z SPIFFS mounted.
10/31/19 08:06:28 Local time zone: -5:00
10/31/19 08:06:28 Using Daylight Saving Time (BST) when in effect.
10/31/19 08:06:28 device name: IotaWat2
10/31/19 08:06:28 MDNS responder started for hostname IotaWat2
10/31/19 08:06:28 LLMNR responder started for hostname IotaWat2
10/31/19 08:06:28 HTTP server started
10/31/19 08:06:28 WiFi connected. SSID=XXXXXXXX, IP=192.168.200.170, channel=11, RSSI -60db
10/31/19 08:06:29 timeSync: service started.
10/31/19 08:06:29 statService: started.
10/31/19 08:06:29 Updater: service started. Auto-update class is ALPHA
10/31/19 08:06:29 dataLog: service started.
10/31/19 08:06:29 dataLog: Last log entry 10/31/19 08:06:20
10/31/19 08:06:30 Updater: Auto-update is current for class ALPHA.
10/31/19 08:06:33 EmonService: started. url:80=emoncms.org, node=IotaWat2, interval=10, encrypted
10/31/19 08:06:34 EmonService: Start posting at 10/31/19 08:06:30

2

Mike,
There is a problem with one of the logs. Could you post the datalogs section of your status display please?
image

3

OK,

Current Log from: 9/16/2019 8:42:10 AM to: 10/31/2019 11:00:00 AM
History Log from: to:

4

Not exactly sure what is going on here but it’s trying to either create or extent the history log. It’s possible the current log is damaged, but lets first try to delete the history log and see if it gets rebuilt. If it that doesn’t do it, we will need to delete both logs.

I will post the command to do that in a PM because I don’t want people trying this at home.