I have some devices running at a customer site with borons and papertrail to see log messages. I often see blocks like this:
What do these errors mean?
Until now, I just ignored them. But today I had a device on my test bench showing a problem similar to something the customer reported and I assume a connection:
The Boron was blinking cyan, which means internet, but no particle cloud. Waiting a long time (~15min), this did not change. After a reboot, the connection could be established normally. The error message was again [system] ERROR: Failed to load session data from persistent storage.
But additional to the connection problem, the main loop was not working anymore. It should send some data over uart in intervalls, this stopped. I use SYSTEM_THREAD(ENABLED);, so the main loop should run even with connection problems. I do not use any particle cloud functions or publish.
I am using a third party sim, I had no problems with this provider on Electrons. This is our first Boron project.
Can anyone help me with these error messages? Thank you in advance!
ERROR: Failed to load session data from persistent storage.
That is not really an error. I'm not sure why it's set at error level, actually. There are many reasons a Gen 3 device won't be able to retrieve its session information from persistent storage, and if that happens it will just renegotiate.
ERROR: Failed to determine server address
Now that actually is an error. It means that the device can't determine the cloud server address. Either there's a DNS problem, or there's a problem with the server address setting.
You could try a particle key server in DFU mode (blinking yellow) to reset it.
Or you can get Boron cloud debug log which will show in much greater detail what actually is failing:
Thank you for the hints. I think there should be no problem with the server address as the connection is always established after a boot from power off and the errors only come after the device is running for some minutes.
At the moment I am not sure about the relation of my application to the problem, although I am not using any Particle cloud features, it’s just there for OTA updates. I will investigate this, use your clouddebug tool and come back with more information about the problem.
Occasionally I get this issue with the b-som continually blinking green. Usually it will either fix itself after about 10 minutes or full power off. Any suggestion on preventing this issue?
0000006044 [system] INFO: Cloud socket connected
0000006044 [comm.protocol.handshake] INFO: Establish secure connection
0000006046 [comm.dtls] INFO: session has 0 uses
0000006054 [comm.dtls] INFO: (CMPL,RENEG,NO_SESS,ERR) restoreStatus=0
0000006054 [comm.dtls] INFO: out_ctr 0,1,0,0,0,0,0,18, next_coap_id=d
0000006054 [comm.dtls] INFO: restored session from persisted session data. next_msg_id=13
0000006055 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 2
0000006310 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 4
0000006310 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 3
0000006310 [comm.protocol.handshake] INFO: Sending HELLO message
0000080888 [comm.coap] ERROR: CoAP message timeout; ID: 14
0000080888 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 0
0000080888 [comm.dtls] INFO: session cmd (CLS,DIS,MOV,LOD,SAV): 4
0000080889 [comm.protocol.handshake] ERROR: Could not send HELLO message: 10
0000088190 [system.cm] ERROR: No addrinfo for e00fce68faa0dac1315478e5.v5.udp-mesh.particle.io#5684
0000088191 [system] WARN: Internet test failed: -230 network
0000088191 [system] WARN: Cloud handshake failed, code=-160
0000088441 [system] INFO: Cloud: disconnecting
0000088441 [system] INFO: Cloud: disconnected
0000088441 [system] INFO: Cloud: connecting
0000088445 [system] WARN: Failed to load session data from persistent storage
0000096190 [system] ERROR: Failed to determine server address
0000096191 [system] WARN: Cloud socket connection failed: -230
0000104190 [system.cm] ERROR: No addrinfo for **********************.v5.udp-mesh.particle.io#5684
0000104191 [system] WARN: Internet test failed: -230 network
0000104191 [system] WARN: Handling cloud error: 2
0000104191 [system] INFO: Cloud: connecting
0000104195 [system] WARN: Failed to load session data from persistent storage
0000112190 [system] ERROR: Failed to determine server address
0000112191 [system] WARN: Cloud socket connection failed: -230
0000120190 [system.cm] ERROR: No addrinfo for **********************.v5.udp-mesh.particle.io#5684
0000120191 [system] WARN: Internet test failed: -230 network
0000120191 [system] WARN: Handling cloud error: 2
0000120191 [system] INFO: Cloud: connecting
0000120195 [system] WARN: Failed to load session data from persistent storage
0000128190 [system] ERROR: Failed to determine server address
0000128191 [system] WARN: Cloud socket connection failed: -230
0000136190 [system.cm] ERROR: No addrinfo for **********************.v5.udp-mesh.particle.io#5684
0000136191 [system] WARN: Internet test failed: -230 network
0000136191 [system] WARN: Handling cloud error: 2
0000136191 [system] INFO: Cloud: connecting
0000136195 [system] WARN: Failed to load session data from persistent storage
0000088445 [system] WARN: Failed to load session data from persistent storage
This is not really an error, it will happen frequently including on cold boot.
0000096190 [system] ERROR: Failed to determine server address
This is not normal. It means the DNS request to look up the cloud address failed. This could happen if there was poor cellular connectivity. If something happened and the modem was in a bad state somehow, resetting the network interface would probably resolve it. It could also be a cellular network data issue, which would likely resolve itself.
