Closed avbentem closed 5 years ago
KrishnaIyer
commented
5 years ago This issue was the focal point of our 1.0.5 fix. I'm closing this since we have enough positive feedback. Please feel free to re-open it if you experience it in the latest stable build.
avbentem
commented
5 years ago This might still be happening in 1.0.5.
But as now the LoRa module is actually working, maybe it's related to #8, and reported there instead: https://github.com/TheThingsProducts/gateway/issues/8#issuecomment-410536382
danielkucera
commented
1 year ago I think this is more related to #71
This is a bug report.
What do you want to do? What do you expect?
I want/expect my gateway to run all day without any human intervention.
What steps did you take? (Give as many details as possible so that we can reproduce it)
Gateway was running just fine...
What went wrong? What is missing?
...until it suddenly rebooted for no apparent reason, and during the boot could not get a configuration but reported
CONF: ERROR REQUEST,CNFG: Downloading gateway configuration failedandCNFG: Communication ERROR. (For this, network problems seem unlikely as it was reporting through MQTT just fine before the reboot? Maybe the remote server was down?)After that it did not properly finish its boot. Like: it never even tried to get the configuration again, nor continued with its existing configuration. So, it was just not operational at all and did not bother to resolve that.
What firmware is running on your gateway?
Loaded from an SD card:
AmazingAckermann, type: 0, version: 1.0.3, commit: 2c56ce09, timestamp: 1521721252 Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298 Build time: Mar 22 2018 12:21:52
Connected through Ziggo ethernet, while XS4ALL WiFi is configured too.
What do the logs show?
All timestamps in UTC (as added by my own monitor).
First, I've no clue why it even restarted, but that happens more often so is likely unrelated to this issue:
A bit later, it successfully gets a network connection:
...but after that the boot process fails:
...and after this there is no mention of
LORA:in the log at all (so also noLORA: GOING ASYNCthat is usually seen, even when the LoRa module actually still fails to receive anything like in #29), nor anything likeMAIN: Gateway bridging.I only got home at 10 PM, so it did not recover itself in 16 hours. Also, after pressing the Mode button it ran into #29, but that seems unrelated. Pressing the Mode button again 45 minutes later finally got the gateway operational again.
Just for reference, the EXPECTED boot for that last part above
## The expected output, as NOT seen due to this very issue ```text CNFG: Load online user config state change to 4 HTTP: Close active socket 0 HTTP: Starting connection HTTPS: Connection Opened: Starting TLS Negotiation HTTP: Wait for TLS Connect HTTP: TLS Connection Opened: Starting Clear Text Communication HTTP: Got 1477 bytes HTTP: Connection Closed HTTP: Close active socket 1 CONF: Parsing response token: HTTP/1.1 200 OK CONF: ROUTER URL: mqtts://bridge.eu.thethings.network:8883 CNFG: Load online user config state change to 6 FREQ: APP_URL_Buffer: https://account.thethingsnetwork.org/api/v2/frequency-plans/EU_863_870 HTTP: Starting connection HTTPS: Connection Opened: Starting TLS Negotiation HTTP: Wait for TLS Connect HTTP: TLS Connection Opened: Starting Clear Text Communication HTTP: Got 1232 bytes HTTP: Connection Closed HTTP: Close active socket 1 CNFG: Load online user config state change to 7 ```Full log
## Full log, all timestamps in UTC (as added by my own monitor) ```text [2018-06-07T04:39:16.060Z] LORA: Accepted packet [2018-06-07T04:39:16.090Z] MQTT: Sending UPLINK OK [2018-06-07T04:39:16.450Z] MQTT: Received DOWNLINK [2018-06-07T04:39:25.346Z] SNTP: State change from 0 to 0 [2018-06-07T04:39:25.350Z] SNTP: State change from 0 to 0 [2018-06-07T04:39:25.352Z] [2018-06-07T04:39:25.353Z] [2018-06-07T04:39:25.354Z] [2018-06-07T04:39:25.356Z] ************************** [2018-06-07T04:39:25.358Z] * The Things Network * [2018-06-07T04:39:25.361Z] * G A T E W A Y * [2018-06-07T04:39:25.363Z] ************************** [2018-06-07T04:39:25.369Z] Firmware name: AmazingAckermann, type: 0, version: 1.0.3, commit: 2c56ce09, timestamp: 1521721252 [2018-06-07T04:39:25.405Z] Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298 [2018-06-07T04:39:25.407Z] Build time: Mar 22 2018 12:21:52 [2018-06-07T04:39:25.408Z] Reboot reason: 0x10 [2018-06-07T04:39:25.419Z] BOOT: (persisted info) 6F 72 72 65 01 10 83 2C E7 16 09 49 92 3A 51 B7 [2018-06-07T04:39:25.420Z] [2018-06-07T04:39:25.421Z] [2018-06-07T04:39:25.422Z] [2018-06-07T04:39:25.423Z] [2018-06-07T04:39:25.424Z] WIFI: Entering state 0 [2018-06-07T04:39:25.448Z] WIFI: Entering SCAN state 0 [2018-06-07T04:39:25.449Z] [2018-06-07T04:39:25.450Z] MAIN: Initialisation complete [2018-06-07T04:39:25.451Z] LORA: Changing state from 0 to 0 [2018-06-07T04:39:25.592Z] [2018-06-07T04:39:25.594Z] MAIN: Leaving state 0 [2018-06-07T04:39:25.597Z] MAIN: Entering state 1 [2018-06-07T04:39:25.604Z] FLASH: Magic bytes found: wifi config present [2018-06-07T04:39:25.610Z] FLASH: Magic bytes found: activation data present [2018-06-07T04:39:25.614Z] FLASH: Magic bytes found: FOTA data present [2018-06-07T04:39:25.617Z] FLASH: Loading Firmware Data [2018-06-07T04:39:25.629Z] CNFG: (Firmware HASH (sha256)) 14 3E 99 52 CC 5B 11 E1 A2 21 8A 04 06 AA 73 1D 1D D8 25 CE FF BD C3 28 34 1E FB 0B B2 AC 9B 56 [2018-06-07T04:39:25.632Z] FLASH: Loading WiFi Data [2018-06-07T04:39:25.636Z] CNFG: WiFi SSID:Any Screenshots or Photos?
Not applicable.
Do you think you can try to fix this yourself and submit a pull request?
No.