Update to 02_06_02 failed - Resolved

[speedy]

I wondered why my system had not updated to 02_06_02 so had a look at the logs …

Ultra right wing Govts. hate the internet

5/06/21 20:17:19 Updater: Download failed HTTPcode -11
5/06/21 21:17:25 Updater: Update from 02_05_12 to 02_06_02
5/06/21 21:17:25 Updater: download 02_06_02
5/06/21 21:17:31 Updater: Download failed HTTPcode -11
5/06/21 22:17:37 Updater: Update from 02_05_12 to 02_06_02
5/06/21 22:17:37 Updater: download 02_06_02
5/06/21 22:17:43 Updater: Download failed HTTPcode -11
5/06/21 23:17:49 Updater: Update from 02_05_12 to 02_06_02
5/06/21 23:17:49 Updater: download 02_06_02
5/06/21 23:17:55 Updater: Download failed HTTPcode -11
5/07/21 00:18:01 Updater: Update from 02_05_12 to 02_06_02
5/07/21 00:18:01 Updater: download 02_06_02
5/07/21 00:18:07 Updater: Download failed HTTPcode -11
5/07/21 01:18:13 Updater: Update from 02_05_12 to 02_06_02
5/07/21 01:18:13 Updater: download 02_06_02
5/07/21 01:18:19 Updater: Download failed HTTPcode -11
5/07/21 02:18:25 Updater: Update from 02_05_12 to 02_06_02
5/07/21 02:18:25 Updater: download 02_06_02
5/07/21 02:18:31 Updater: Download failed HTTPcode -11
5/07/21 03:18:37 Updater: Update from 02_05_12 to 02_06_02
5/07/21 03:18:37 Updater: download 02_06_02
5/07/21 03:18:43 Updater: Download failed HTTPcode -11
5/07/21 04:18:49 Updater: Update from 02_05_12 to 02_06_02
5/07/21 04:18:49 Updater: download 02_06_02
5/07/21 04:18:55 Updater: Download failed HTTPcode -11
5/07/21 05:19:01 Updater: Update from 02_05_12 to 02_06_02
5/07/21 05:19:01 Updater: download 02_06_02
5/07/21 05:19:07 Updater: Download failed HTTPcode -11
5/07/21 06:19:13 Updater: Update from 02_05_12 to 02_06_02
5/07/21 06:19:13 Updater: download 02_06_02
5/07/21 06:19:19 Updater: Download failed HTTPcode -11
5/07/21 07:19:25 Updater: Update from 02_05_12 to 02_06_02
5/07/21 07:19:25 Updater: download 02_06_02
5/07/21 07:19:31 Updater: Download failed HTTPcode -11
5/07/21 08:19:37 Updater: Update from 02_05_12 to 02_06_02
5/07/21 08:19:37 Updater: download 02_06_02
5/07/21 08:19:43 Updater: Download failed HTTPcode -11
5/07/21 09:19:49 Updater: Update from 02_05_12 to 02_06_02
5/07/21 09:19:49 Updater: download 02_06_02
5/07/21 09:19:56 Updater: Download failed HTTPcode -11
5/07/21 10:20:02 Updater: Update from 02_05_12 to 02_06_02
5/07/21 10:20:02 Updater: download 02_06_02
5/07/21 10:20:08 Updater: Download failed HTTPcode -11
5/07/21 11:20:15 Updater: Update from 02_05_12 to 02_06_02
5/07/21 11:20:15 Updater: download 02_06_02
5/07/21 11:20:21 Updater: Download failed HTTPcode -11
5/07/21 12:20:27 Updater: Update from 02_05_12 to 02_06_02
5/07/21 12:20:27 Updater: download 02_06_02
5/07/21 12:20:33 Updater: Download failed HTTPcode -11
5/07/21 13:20:39 Updater: Update from 02_05_12 to 02_06_02
5/07/21 13:20:39 Updater: download 02_06_02
5/07/21 13:20:46 Updater: Download failed HTTPcode -11
5/07/21 14:20:52 Updater: Update from 02_05_12 to 02_06_02
5/07/21 14:20:52 Updater: download 02_06_02
5/07/21 14:20:58 Updater: Download failed HTTPcode -11
5/07/21 15:21:04 Updater: Update from 02_05_12 to 02_06_02
5/07/21 15:21:04 Updater: download 02_06_02
5/07/21 15:21:11 Updater: Download failed HTTPcode -11
5/07/21 16:21:17 Updater: Update from 02_05_12 to 02_06_02
5/07/21 16:21:17 Updater: download 02_06_02
5/07/21 16:21:23 Updater: Download failed HTTPcode -11

[speedy]

So did the old manual update with the files off github
Restart and … broken.
Page now just displays the HTML code
Looks like I’ll have to pull the card and put 02_05_12 back on

[speedy]

Reverted back to 02_05_12 but when I load the local IP or iotawatt.local all I get is the index page code.
Same when trying to access on a different computer.
Any ideas???

[overeasy]

The original problem was fairly harmless with the download timing out every hour on the retry. There was a simple solution to that. I’m guessing you are in Australia?

I can’t tell you how to fix it because I don’t know what you did. Can you tell me how you did “the old manual update”? How you tried to revert? What the led state is?

[speedy]

manual update = download the release files (02_06_02) off github and copy to root of SD. (all except config file)

When that didn’t work ( page loads as html code )
copied the old 02-05-12 files back to root of SD card.
power cycled the unit, still just get the html code page

yes, in Aus

[overeasy]

From a browser, can you run:

http://IoTaWatt.local/IoTaWatt/iotamsgs.txt?textpos=-10000

What is the state of the led?

[speedy]

Okay, read the old article and realised my mistake! OOOOPS !!.

MINOR auto-update in Australia stuck in restart cycle - resolving

Manually updated on 18/6/20 after being unable to access the web interface for a few days. After killing the WAN connection I was able to set update class to “NONE”, however the Graph+ interface was broken (e.g., appearance similar to unloaded CSS on a web page). During the udpate period, “power” for three inputs appears to have been recorded as normal, however the kWh accrual for this period has broken (registering about 30% of typical consumption). I’m guessing this is due to being “down fo…

(putting those files into the root is needed when creating a NEW SD card.)

Found the .BIN file @ https://iotawatt.com/firmware/bin/02_06_02.bin and downloaded

(Had to hack the URL to get this file as I could not find it on the iotawatt.com site by just by looking around. The old article referenced firmware/bin/02-05-09, so I just changed the end of then URL to 02-06-02 )

Copied to “download” folder and then ran the update command http://iotawatt.local/update?release=02_06_02

All good !

SD initialized.
5/07/21 11:30:56z Real Time Clock is running. Unix time 1620387056
5/07/21 11:30:56z Power failure detected.
5/07/21 11:30:56z Reset reason: External System
5/07/21 11:30:56z ESP8266 ChipID: 6145634
5/07/21 11:30:56z IoTaWatt 5.0, Firmware version 02_05_12
5/07/21 11:30:56z SPIFFS mounted.
5/07/21 19:31:02 Local time zone: +8:00
5/07/21 19:31:02 device name: IotaWatt
5/07/21 19:31:05 HTTP server started
5/07/21 19:31:05 WiFi connected. SSID=SpeedyDave, IP=192.168.1.106, channel=4, RSSI -71db
5/07/21 19:31:05 MDNS responder started for hostname IotaWatt
5/07/21 19:31:05 LLMNR responder started for hostname IotaWatt
5/07/21 19:31:05 timeSync: service started.
5/07/21 19:31:05 statService: started.
5/07/21 19:31:05 Updater: service started. Auto-update class is NONE
5/07/21 19:31:05 dataLog: service started.
5/07/21 19:31:10 dataLog: Last log entry 05/07/21 19:21:00
5/07/21 19:31:10 historyLog: service started.
5/07/21 19:31:11 historyLog: Last log entry 05/07/21 19:21:00
5/07/21 19:31:15 PVoutput: started
5/07/21 19:31:15 PVoutput: System Speedy Dave’s, interval 5, donator mode
5/07/21 19:31:16 PVoutput: Start status beginning 05/07/21 19:20:00
5/07/21 19:33:48 Updater: signature verified
5/07/21 19:33:56 Updater: firmware upgraded to version 02_06_02
5/07/21 19:33:56 Updater: Firmware updated, restarting.

** Restart **

SD initialized.
5/07/21 11:34:05z Real Time Clock is running. Unix time 1620387245
5/07/21 11:34:05z Reset reason: Software/System restart
5/07/21 11:34:05z Trace: 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:3, 1:4, 1:3, 1:4, 1:3, 1:4, 1:1[2], 1:2[3], 9:0[3], 9:0, 9:1, 8:4, 8:6, 8:8, 8:9, 9:3, 9:5, 9:9, 1:2, 1:3
5/07/21 11:34:05z ESP8266 ChipID: 6145634
5/07/21 11:34:05z IoTaWatt 5.0, Firmware version 02_06_02
5/07/21 11:34:05z Updater: Installing update files for version 02_06_02
5/07/21 11:34:05z Updater: Installing GRAPH.JS
5/07/21 11:34:06z Updater: Installing GRAPH2.HTM
5/07/21 11:34:06z Updater: Installing GRAPH2.JS
5/07/21 11:34:06z Updater: Installing INDEX.HTM
5/07/21 11:34:07z Updater: Installing TABLES.TXT
5/07/21 11:34:07z Updater: Installing CNFSTYLE.CSS
5/07/21 11:34:07z Updater: Installing EDIT.HTM
5/07/21 11:34:08z Updater: Installing GRAPH.HTM
5/07/21 11:34:08z Updater: Installation complete.
5/07/21 11:34:08z SPIFFS mounted.
5/07/21 19:34:08 Local time zone: +8:00
5/07/21 19:34:08 device name: IotaWatt
5/07/21 19:34:08 HTTP server started
5/07/21 19:34:08 timeSync: service started.
5/07/21 19:34:08 statService: started.
5/07/21 19:34:08 dataLog: service started.
5/07/21 19:34:11 dataLog: Last log entry 05/07/21 19:33:35
5/07/21 19:34:13 historyLog: service started.
5/07/21 19:34:13 historyLog: Last log entry 05/07/21 19:33:00
5/07/21 19:34:13 WiFi connected. SSID=SpeedyDave, IP=192.168.1.106, channel=4, RSSI -65db
5/07/21 19:34:13 MDNS responder started for hostname IotaWatt
5/07/21 19:34:13 LLMNR responder started for hostname IotaWatt
5/07/21 19:34:13 Updater: service started. Auto-update class is NONE
5/07/21 19:34:18 PVoutput: started
5/07/21 19:34:18 PVoutput: System Speedy Dave’s, interval 5, donator mode
5/07/21 19:34:19 PVoutput: Start status beginning 05/07/21 19:25:00
5/07/21 19:38:53 Updater: Auto-update class changed to MINOR
5/07/21 19:38:55 Updater: Auto-update is current for class MINOR.

[overeasy]

This update problem is mostly unique to Australia. My suspicion is that the ISP is causing the timeouts. The release file should be served quickly out of the global Cloudflare cache, Australia has three servers, but apparently something else is deliberately delaying packets.

[speedy]

“something else is deliberately delaying packets.”
That would be Herr Duttolini, the Tuberfuhrer.
Not sure if the world is aware of what is going on (politically) down under, but it is some pretty dystopian totalitarian BS by a religious cult (Pentecostal) absorbed prime minister who believes in the “rapture” which is why we are damn near last in the world for vaccinations against covid etc.

Anyway;
Are the .BIN files accessible on Git or is there an easy way of finding them on your web site ?

[overeasy]

@speedy

Are the .BIN files accessible on Git or is there an easy way of finding them on your web site ?

They are at https://iotawatt.com/firmware/bin/02_06_02.bin

That is a release blob that contains the 8266 firmware as well as the SD files for the release. It is also signed to insure authenticity. You can get all of those files including the 8266 binary on github for any release, but they are individual and would require using ESPTOOL.py to flash the ESP8266. This is easier and secure.

[speedy]

https://iotawatt.com/firmware/bin/02_06_02.binre

Gets a 404 not found response ? or is the “re” on the end of the URL a typo ?

[overeasy]

Typo. Just fixed it. Try again.

[speedy]

Cool and a really big thanks for your dedication to your project Bob. It really is very very good !

[speedy]

@overeasy

My suspicion is that the ISP is causing the timeouts.

This really $h1ts me.
What do I need to ask / tell my ISP to get this sorted ?
Do they need a DNS entry in their lookup file or something ?

What URL is timing out ?

[overeasy]

Calm down. I don’t have any proof that the ISP is doing anything to willfully cause this problem. All I have is that it only happens in Australia. The URL is the one you just used, except that the IoTaWatt will use http rather than https. It’s possible whatever proxy is handling it may be sending a redirect to enforce https. What would be needed to figure it out is a wire-shark trace when it happens. I can’t do that. I thought about using my VPN to simulate a presence there, but for all the complexity it still wouldn’t be definitive with the VPN in the loop.

So teeing off on the ISP would be an exercise in futility. If someone wants to wireshark the IoTaWatt during updte, I’d be interested in the results.

[speedy]

@overeasy

Calm down. I don’t have any proof that the ISP is doing anything

Sorry, but you misinterpret me Bob.

No where did I ever lay blame on the ISP. It is our fascist govt that I have issue with and their draconian laws being forced onto all areas, communications are just one.

I simply asked if there was some technically relevant words that (i don’t know ) I could say to my ISP to fix the issue.
I optimistically hope that it is in no way a deliberate ISP intervention, just merely a config oversight.

I must say though, I does seem VERY odd that it is a unique Aussie issue, and one that looks to be across different ISP’s.

[LosinIt]

@speedy

It is our fascist govt that I have issue with and their draconian laws being forced onto all areas, communications are just one.

While I sympathize with your plight I don’t think this venue is a good place to vent.

[speedy]

Thanks for your input Los.
As the two items being discussed (update and failure) are inextricably linked, I feel that it is totally relevant to at least highlight the issue here.

If we are forced to only discuss specific issues within their specific “silo’s” (echo chamber) then the majority of people will be unaware that a related issue even exists.

Whilst I absolutely recognise that this is not a “political” forum (hence my restraint) there is absolutely no doubt that the ongoing internet “issues” that we have in Australia are 100% politically created, and as such, when discussing THIS particular issue, the “political” angle should absolutely be looked at.

Hope that clears it up for you.