Not posting to Emoncms

Cataract2 · October 29, 2019, 12:02am

1

/

1

So around noon today IotaWatt and EmonCMS started to not play nice. Looking at the logs in IotaWatt I see the following.

SD initialized.
10/28/19 23:24:58z Real Time Clock is running. Unix time 1572305098
10/28/19 23:24:58z Reset reason: Software/System restart
10/28/19 23:24:58z 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:3, 1:4, 1:3, 1:4, 1:1[8], 1:2[10], 9:0[10], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 10:2, 10:3
10/28/19 23:24:58z ESP8266 ChipID: 6348181
10/28/19 23:24:58z IoTaWatt 5.0, Firmware version 02_04_02
10/28/19 23:24:58z SPIFFS mounted.
10/29/19 04:24:59 Local time zone: +5:00
10/29/19 04:24:59 device name: IotaWatt
10/29/19 04:24:59 MDNS responder started for hostname IotaWatt
10/29/19 04:24:59 LLMNR responder started for hostname IotaWatt
10/29/19 04:24:59 HTTP server started
10/29/19 04:24:59 timeSync: service started.
10/29/19 04:24:59 statService: started.
10/29/19 04:24:59 Updater: service started. Auto-update class is MINOR
10/29/19 04:24:59 dataLog: service started.
10/29/19 04:25:00 dataLog: Last log entry 10/29/19 04:24:55
10/29/19 04:25:00 WiFi connected. SSID=FBI Surveillance Van Cat1, IP=192.168.1.13, channel=11, RSSI -62db
10/29/19 04:25:00 Updater: Auto-update is current for class MINOR.
10/29/19 04:25:04 EmonService: started. url=192.168.1.21:80/emoncms, node=IotaWatt, interval=5
10/29/19 04:25:05 EmonService: Start posting at 10/28/19 21:53:25
10/29/19 04:25:59 historyLog: service started.
10/29/19 04:25:59 historyLog: Last log entry 10/29/19 04:24:00
10/29/19 04:27:08 EmonService: HTTP response -11, retrying.

The HTTP response is something I’m not familiar with. Not sure how to proceed.

overeasy · October 29, 2019, 4:11am

The response code -11 is a timeout. If this started at about noon your local time, it’s been out-to-lunch for awhile.

I can see that you restarted the IoTaWatt. The good news is that it is still logging and you are not losing anything. When it finally mind-melds with Emoncms, the backlog will be uploaded.

I can also see that you have a local instance of Emoncms. You have probably restarted that as well, but in any event, I would be looking there for a problem.

Without seeing more of the log, I can’t tell if it’s stopped or just slow. You indicated that it stopped posting around noon, but as of the last restart, it had posted through 21:53:25. If you post more of the message log, I will look at it in the morning (12:11am here now).

Cataract2 · October 29, 2019, 8:09am

No problem on the log. Here is the full log.

10/28/19 15:06:04z IoTaWatt 5.0, Firmware version 02_04_02
10/28/19 15:06:04z SPIFFS mounted.
10/28/19 20:06:05 Local time zone: +5:00
10/28/19 20:06:05 device name: IotaWatt
10/28/19 20:06:05 MDNS responder started for hostname IotaWatt
10/28/19 20:06:05 LLMNR responder started for hostname IotaWatt
10/28/19 20:06:05 HTTP server started
10/28/19 20:06:05 timeSync: service started.
10/28/19 20:06:05 statService: started.
10/28/19 20:06:05 Updater: service started. Auto-update class is MINOR
10/28/19 20:06:05 dataLog: service started.
10/28/19 20:06:06 dataLog: Last log entry 10/28/19 20:06:00
10/28/19 20:06:06 WiFi connected. SSID=FBI Surveillance Van Cat1, IP=192.168.1.13, channel=11, RSSI -62db
10/28/19 20:06:06 Updater: Auto-update is current for class MINOR.
10/28/19 20:06:10 EmonService: started. url=192.168.1.21:80/emoncms, node=IotaWatt, interval=5
10/28/19 20:06:11 EmonService: Start posting at 10/28/19 20:06:00

** Restart **

SD initialized.
10/28/19 15:07:01z Real Time Clock is running. Unix time 1572275221
10/28/19 15:07:01z Reset reason: Exception
10/28/19 15:07:01z Trace: 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1
10/28/19 15:07:01z ESP8266 ChipID: 6348181
10/28/19 15:07:01z IoTaWatt 5.0, Firmware version 02_04_02
10/28/19 15:07:01z SPIFFS mounted.
10/28/19 20:07:02 Local time zone: +5:00
10/28/19 20:07:02 device name: IotaWatt
10/28/19 20:07:02 MDNS responder started for hostname IotaWatt
10/28/19 20:07:02 LLMNR responder started for hostname IotaWatt
10/28/19 20:07:02 HTTP server started
10/28/19 20:07:02 timeSync: service started.
10/28/19 20:07:02 statService: started.
10/28/19 20:07:02 Updater: service started. Auto-update class is MINOR
10/28/19 20:07:02 dataLog: service started.
10/28/19 20:07:03 dataLog: Last log entry 10/28/19 20:06:55
10/28/19 20:07:03 WiFi connected. SSID=FBI Surveillance Van Cat1, IP=192.168.1.13, channel=11, RSSI -62db
10/28/19 20:07:03 Updater: Auto-update is current for class MINOR.
10/28/19 20:07:07 EmonService: started. url=192.168.1.21:80/emoncms, node=IotaWatt, interval=5
10/28/19 20:07:08 EmonService: Start posting at 10/28/19 20:06:55
10/28/19 20:08:02 historyLog: service started.
10/28/19 20:08:02 historyLog: Last log entry 10/28/19 20:06:00

** Restart **

SD initialized.
10/28/19 15:12:53z Real Time Clock is running. Unix time 1572275573
10/28/19 15:12:53z Reset reason: Software/System restart
10/28/19 15:12:53z Trace: 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1
10/28/19 15:12:53z ESP8266 ChipID: 6348181
10/28/19 15:12:53z IoTaWatt 5.0, Firmware version 02_04_02
10/28/19 15:12:53z SPIFFS mounted.
10/28/19 20:12:54 Local time zone: +5:00
10/28/19 20:12:54 device name: IotaWatt
10/28/19 20:12:54 MDNS responder started for hostname IotaWatt
10/28/19 20:12:54 LLMNR responder started for hostname IotaWatt
10/28/19 20:12:54 HTTP server started
10/28/19 20:12:54 timeSync: service started.
10/28/19 20:12:54 statService: started.
10/28/19 20:12:54 Updater: service started. Auto-update class is MINOR
10/28/19 20:12:55 WiFi connected. SSID=FBI Surveillance Van Cat1, IP=192.168.1.13, channel=11, RSSI -61db
10/28/19 20:12:55 dataLog: service started.
10/28/19 20:12:55 dataLog: Last log entry 10/28/19 20:12:50
10/28/19 20:12:56 Updater: Auto-update is current for class MINOR.
10/28/19 20:12:59 EmonService: started. url=192.168.1.21:80/emoncms, node=IotaWatt, interval=5
10/28/19 20:13:00 EmonService: Start posting at 10/28/19 20:12:50
10/28/19 20:13:54 historyLog: service started.
10/28/19 20:13:54 historyLog: Last log entry 10/28/19 20:12:00
10/28/19 21:52:52 EmonService: HTTP response -11, retrying.

** Restart **

SD initialized.
10/28/19 22:55:23z Real Time Clock is running. Unix time 1572303323
10/28/19 22:55:23z Reset reason: Exception
10/28/19 22:55:23z Trace: 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1
10/28/19 22:55:23z ESP8266 ChipID: 6348181
10/28/19 22:55:23z IoTaWatt 5.0, Firmware version 02_04_02
10/28/19 22:55:23z SPIFFS mounted.
10/29/19 03:55:24 Local time zone: +5:00
10/29/19 03:55:24 device name: IotaWatt
10/29/19 03:55:24 MDNS responder started for hostname IotaWatt
10/29/19 03:55:24 LLMNR responder started for hostname IotaWatt
10/29/19 03:55:24 HTTP server started
10/29/19 03:55:24 timeSync: service started.
10/29/19 03:55:24 statService: started.
10/29/19 03:55:24 Updater: service started. Auto-update class is MINOR
10/29/19 03:55:24 dataLog: service started.
10/29/19 03:55:25 dataLog: Last log entry 10/29/19 03:55:20
10/29/19 03:55:25 WiFi connected. SSID=FBI Surveillance Van Cat1, IP=192.168.1.13, channel=11, RSSI -63db
10/29/19 03:55:25 Updater: Auto-update is current for class MINOR.
10/29/19 03:55:29 EmonService: started. url=192.168.1.21:80/emoncms, node=IotaWatt, interval=5
10/29/19 03:55:30 EmonService: Start posting at 10/28/19 21:52:10
10/29/19 03:56:24 historyLog: service started.
10/29/19 03:56:24 historyLog: Last log entry 10/29/19 03:55:00
10/29/19 03:57:29 EmonService: HTTP response -11, retrying.
10/29/19 04:24:56 Restart command received.

** Restart **

SD initialized.
10/28/19 23:24:58z Real Time Clock is running. Unix time 1572305098
10/28/19 23:24:58z Reset reason: Software/System restart
10/28/19 23:24:58z 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:3, 1:4, 1:3, 1:4, 1:1[8], 1:2[10], 9:0[10], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3, 10:2, 10:3
10/28/19 23:24:58z ESP8266 ChipID: 6348181
10/28/19 23:24:58z IoTaWatt 5.0, Firmware version 02_04_02
10/28/19 23:24:58z SPIFFS mounted.
10/29/19 04:24:59 Local time zone: +5:00
10/29/19 04:24:59 device name: IotaWatt
10/29/19 04:24:59 MDNS responder started for hostname IotaWatt
10/29/19 04:24:59 LLMNR responder started for hostname IotaWatt
10/29/19 04:24:59 HTTP server started
10/29/19 04:24:59 timeSync: service started.
10/29/19 04:24:59 statService: started.
10/29/19 04:24:59 Updater: service started. Auto-update class is MINOR
10/29/19 04:24:59 dataLog: service started.
10/29/19 04:25:00 dataLog: Last log entry 10/29/19 04:24:55
10/29/19 04:25:00 WiFi connected. SSID=FBI Surveillance Van Cat1, IP=192.168.1.13, channel=11, RSSI -62db
10/29/19 04:25:00 Updater: Auto-update is current for class MINOR.
10/29/19 04:25:04 EmonService: started. url=192.168.1.21:80/emoncms, node=IotaWatt, interval=5
10/29/19 04:25:05 EmonService: Start posting at 10/28/19 21:53:25
10/29/19 04:25:59 historyLog: service started.
10/29/19 04:25:59 historyLog: Last log entry 10/29/19 04:24:00
10/29/19 04:27:08 EmonService: HTTP response -11, retrying.

** Restart **

SD initialized.
10/28/19 23:44:07z Real Time Clock is running. Unix time 1572306247
10/28/19 23:44:07z Reset reason: Exception
10/28/19 23:44:07z Trace: 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1
10/28/19 23:44:07z ESP8266 ChipID: 6348181
10/28/19 23:44:07z IoTaWatt 5.0, Firmware version 02_04_02
10/28/19 23:44:07z SPIFFS mounted.
10/29/19 04:44:08 Local time zone: +5:00
10/29/19 04:44:08 device name: IotaWatt
10/29/19 04:44:08 MDNS responder started for hostname IotaWatt
10/29/19 04:44:08 LLMNR responder started for hostname IotaWatt
10/29/19 04:44:08 HTTP server started
10/29/19 04:44:08 timeSync: service started.
10/29/19 04:44:08 statService: started.
10/29/19 04:44:08 Updater: service started. Auto-update class is MINOR
10/29/19 04:44:08 dataLog: service started.
10/29/19 04:44:09 dataLog: Last log entry 10/29/19 04:44:05
10/29/19 04:44:09 WiFi connected. SSID=FBI Surveillance Van Cat1, IP=192.168.1.13, channel=11, RSSI -62db
10/29/19 04:44:09 Updater: Auto-update is current for class MINOR.
10/29/19 04:44:35 EmonService: started. url=192.168.1.21:80/emoncms, node=IotaWatt, interval=5
10/29/19 04:44:37 EmonService: Start posting at 10/28/19 21:54:40

** Restart **

SD initialized.
10/28/19 23:44:44z Real Time Clock is running. Unix time 1572306284
10/28/19 23:44:44z Reset reason: Exception
10/28/19 23:44:44z Trace: 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1, 15:0, 15:1, 15:1
10/28/19 23:44:44z ESP8266 ChipID: 6348181
10/28/19 23:44:44z IoTaWatt 5.0, Firmware version 02_04_02
10/28/19 23:44:44z SPIFFS mounted.
10/29/19 04:44:45 Local time zone: +5:00
10/29/19 04:44:45 device name: IotaWatt
10/29/19 04:44:45 MDNS responder started for hostname IotaWatt
10/29/19 04:44:45 LLMNR responder started for hostname IotaWatt
10/29/19 04:44:45 HTTP server started
10/29/19 04:44:45 timeSync: service started.
10/29/19 04:44:45 statService: started.
10/29/19 04:44:45 Updater: service started. Auto-update class is MINOR
10/29/19 04:44:45 dataLog: service started.
10/29/19 04:44:46 dataLog: Last log entry 10/29/19 04:44:40
10/29/19 04:44:46 WiFi connected. SSID=FBI Surveillance Van Cat1, IP=192.168.1.13, channel=11, RSSI -60db
10/29/19 04:44:46 Updater: Auto-update is current for class MINOR.
10/29/19 04:44:50 EmonService: started. url=192.168.1.21:80/emoncms, node=IotaWatt, interval=5
10/29/19 04:44:51 EmonService: Start posting at 10/28/19 21:55:55
10/29/19 04:45:45 historyLog: service started.
10/29/19 04:45:45 historyLog: Last log entry 10/29/19 04:44:00
10/29/19 04:46:50 EmonService: HTTP response -11, retrying.

overeasy · October 29, 2019, 12:03pm

I don’t have a definitive answer, but it looks as if Emoncms accepts one input post with about 15 frames (75 seconds) worthof data, then never responds OK. IoTaWatt times out waiting then retries again and again.

That would be my diagnosis, except that the IoTaWatt is also taking exceptions periodically in a seemingly unrelated utility. So I need to look at that more and try to figure that out. I’m not a big believer in coincidence. My sense is that they are related, but it could be caused by the retry, I just don’t know know, the trace isn’t deep enough to tell how it got there.

Nevertheless, i still think it’s an Emoncms issue. Has anything changed?

Cataract2 · October 29, 2019, 12:44pm

Not as of this morning before I left for work. I did notice on my tablet that continuously monitors EmonCMS there was an error that seems to be popping up on the app display.

Cataract2 · October 29, 2019, 12:49pm

Just thought I should check would you happen to know of any updates to EmonCMS that changed the URL that we used to report to?

overeasy · October 29, 2019, 12:51pm

You might try floating that on the OEM forum. It looks like you did get Brian Orpin’s attention. You might try it as a new thread.

I can understand the response you got to the original thread as they have no idea how to read an IoTaWatt log. I can’t make sense of an Emoncms log. But this is an Emoncms message. Even if unrelated, someone should be able to tell you what it means.

Cataract2 · October 29, 2019, 12:53pm

I saw that he replied and I provided additional information. I also should note that I have 2 OpenEVSE chargers that are tied into EmonCMS and they are reporting no issues sending information to it and the inputs are updating. So this definitely appears to be between IotaWatt and EmonCMS.

overeasy · October 29, 2019, 1:17pm

Are the corresponding feeds updating?

Cataract2 · October 29, 2019, 1:38pm

Yes. The timers in the input field on EmonCMS we’re showing a reset in every 30 seconds update for both OpenEVSE.

I was doing some digging and came across an old Post from 2018 where you had someone send their browser to an address with the API key and post the response from that. I didn’t know if I did that if it would give more information?

overeasy · October 29, 2019, 2:32pm

I understand the input so are being updated. Do those inputs have a process list to log to feed and if so, are you also seeing updates to those feeds on the feeds page?

overeasy · October 29, 2019, 2:39pm

It may come to that, but it should not be done casually. If you post an input with a current time, IoTaWatt will skip ahead and you will not get the history upload. You will need to time stamp it to avoid that problem.

Cataract2 · October 29, 2019, 6:11pm

Sorry, I missed the reply above the last one. Yes the data in those fields is being updated.

Cataract2 · October 29, 2019, 8:16pm

Ok, back home and taking a good look at both the IotaWatt and EmonCMS logs. The OpenEVSE chargers are posting information so those seem to be working.

Cataract2 · October 29, 2019, 8:38pm

Brian had me install tshark on the EmonCMS and I posted the results. Not sure if maybe they might be useful to you as well in this. I can see both OpenEVSE postings, and then one that is posting every 10 seconds which follows with my IotaWatt settings, yet it has nothing.

Cataract2 · October 29, 2019, 8:59pm

This might also be of use for you. I got into the EmonCMS through ssh to look at the log. Also changed the logging to info. Looking at the log and based on what you said. I can see values that the IotaWatt should be sending over to the EmonCMS, so it appears it’s seeing the information, but according to what you said it’s not acknowledging receipt.

2019-10-29 20:50:02.004|INFO|feed_model.php|insert_data() feedid=23 updatetime=1572281845 feedtime=1572281845 value=19.28 arg=
2019-10-29 20:50:01.937|INFO|feed_model.php|insert_data() feedid=30 updatetime=1572281845 feedtime=1572281845 value=0.77 arg=
2019-10-29 20:50:01.966|INFO|feed_model.php|insert_data() feedid=31 updatetime=1572281845 feedtime=1572281845 value=5.62 arg=
2019-10-29 20:50:02.004|INFO|feed_model.php|insert_data() feedid=23 updatetime=1572281845 feedtime=1572281845 value=19.28 arg=
2019-10-29 20:50:01.966|INFO|feed_model.php|insert_data() feedid=31 updatetime=1572281845 feedtime=1572281845 value=5.62 arg=
2019-10-29 20:50:02.004|INFO|feed_model.php|insert_data() feedid=23 updatetime=1572281845 feedtime=1572281845 value=19.28 arg=
2019-10-29 20:50:01.966|INFO|feed_model.php|insert_data() feedid=31 updatetime=1572281845 feedtime=1572281845 value=5.62 arg=
2019-10-29 20:50:01.901|INFO|feed_model.php|insert_data() feedid=22 updatetime=1572281845 feedtime=1572281845 value=829.58 arg=
2019-10-29 20:50:01.937|INFO|feed_model.php|insert_data() feedid=30 updatetime=1572281845 feedtime=1572281845 value=0.77 arg=
2019-10-29 20:50:01.966|INFO|feed_model.php|insert_data() feedid=31 updatetime=1572281845 feedtime=1572281845 value=5.62 arg=
2019-10-29 20:50:01.848|INFO|feed_model.php|insert_data() feedid=63 updatetime=1572281845 feedtime=1572281845 value=241.8 arg=
2019-10-29 20:50:01.883|INFO|feed_model.php|insert_data() feedid=62 updatetime=1572281880 feedtime=1572281880 value=233.86800362363 arg=join
2019-10-29 20:50:01.901|INFO|feed_model.php|insert_data() feedid=22 updatetime=1572281845 feedtime=1572281845 value=829.58 arg=
2019-10-29 20:50:01.901|INFO|feed_model.php|insert_data() feedid=22 updatetime=1572281845 feedtime=1572281845 value=829.58 arg=
2019-10-29 20:50:01.901|INFO|feed_model.php|insert_data() feedid=22 updatetime=1572281845 feedtime=1572281845 value=829.58 arg=
2019-10-29 20:50:01.797|INFO|feed_model.php|insert_data() feedid=29 updatetime=1572281845 feedtime=1572281845 value=120.9 arg=
2019-10-29 20:50:01.848|INFO|feed_model.php|insert_data() feedid=63 updatetime=1572281845 feedtime=1572281845 value=241.8 arg=
2019-10-29 20:50:01.797|INFO|feed_model.php|insert_data() feedid=29 updatetime=1572281845 feedtime=1572281845 value=120.9 arg=
2019-10-29 20:50:01.797|INFO|feed_model.php|insert_data() feedid=29 updatetime=1572281845 feedtime=1572281845 value=120.9 arg=
2019-10-29 20:50:01.756|INFO|feed_model.php|insert_data() feedid=61 updatetime=1572281880 feedtime=1572281880 value=1627.4049431641 arg=join
2019-10-29 20:50:01.797|INFO|feed_model.php|insert_data() feedid=29 updatetime=1572281845 feedtime=1572281845 value=120.9 arg=
2019-10-29 20:50:01.797|INFO|feed_model.php|insert_data() feedid=29 updatetime=1572281845 feedtime=1572281845 value=120.9 arg=
2019-10-29 20:50:01.848|INFO|feed_model.php|insert_data() feedid=63 updatetime=1572281845 feedtime=1572281845 value=241.8 arg=
2019-10-29 20:50:01.848|INFO|feed_model.php|insert_data() feedid=63 updatetime=1572281845 feedtime=1572281845 value=241.8 arg=
2019-10-29 20:50:01.797|INFO|feed_model.php|insert_data() feedid=29 updatetime=1572281845 feedtime=1572281845 value=120.9 arg=

Cataract2 · October 30, 2019, 12:44am

I also have the back and forth from IotaWatt and EmonCMS now. According to Brian the EmonCMS is sending back an ok.

194 60.238194461 192.168.1.13 → 192.168.1.21 TCP 1514 POST HTTP://192.168.1.21/emoncms/input/bulk HTTP/1.1 [TCP segment of a reassembled PDU]
195 60.238477453 192.168.1.21 → 192.168.1.13 TCP 54 80 → 49267 [ACK] Seq=1 Ack=1461 Win=32120 Len=0
196 60.261928811 192.168.1.13 → 192.168.1.21 HTTP 1363 POST HTTP://192.168.1.21/emoncms/input/bulk HTTP/1.1 (application/x-www-form-urlencoded)
197 60.262048808 192.168.1.21 → 192.168.1.13 TCP 54 80 → 49267 [ACK] Seq=1 Ack=2770 Win=35040 Len=0
199 62.929419779 192.168.1.13 → 192.168.1.21 TCP 60 49267 → 80 [FIN, ACK] Seq=2770 Ack=1 Win=5840 Len=0
200 62.978935424 192.168.1.21 → 192.168.1.13 TCP 54 80 → 49267 [ACK] Seq=1 Ack=2771 Win=35040 Len=0
201 64.265328209 192.168.1.21 → 192.168.1.13 HTTP 205 HTTP/1.1 200 OK (text/plain)
202 64.265989190 192.168.1.21 → 192.168.1.13 TCP 54 80 → 49267 [FIN, ACK] Seq=152 Ack=2771 Win=35040 Len=0
203 64.273891974 192.168.1.13 → 192.168.1.21 TCP 60 49267 → 80 [RST, ACK] Seq=2771 Ack=152 Win=5840 Len=0
204 64.274224965 192.168.1.13 → 192.168.1.21 TCP 60 49267 → 80 [RST, ACK] Seq=2771 Ack=153 Win=5840 Len=0

overeasy · October 30, 2019, 1:31am

I’m not familiar with this shark format. Do you have the header that explains the columns? Reason I ask is that I’m wondering if the second column is time in seconds. If that’s the case, and I’m out on a limb here with that conjecture, but the OK response would be after four seconds. That would be consistent with the timeout being reported as the post times out after 2 seconds.

overeasy · October 30, 2019, 1:43am

I ran an update on EmonCMS yesterday but it reported no update but then I did see a post recently about there being some sort of update within the last few days so maybe there was one and it grabbed it. was there a recent update that had a change to the address Iotawatt should be reporting to now?

What is the timing of this with respect to the problem onset?

Cataract2 · October 30, 2019, 8:53am

Around 12:50PM EST on Oct 28 was the start of the drop off. EmonCMS reports 40 hours since last update. The update check I ran on EmonCMS happened a few hours earlier, but it reported no updates.

Double checking the tshark as Brian says what he initially thought was a report of acknowledgement was not and that nothing it coming in from IotaWatt.

Not posting to Emoncms

Iotawatt Fails to post to EmonCMS

Iotawatt Fails to post to EmonCMS

1

1