I’m facing a connectivity issue with my RPI 3.
The device has the status Inactive, and I couldn’t find the reason for that.
I followed the instructions in the troubleshooting section, and I can tell that:
the device is correctly connected to ethernet
as much as can see, the network is not restricting or blocking the ports specified in the balena network requirements.
in the dashboard everything seems to be normal with the logs, but the status is inactive and there is no access to the terminal.
there is no recognized repeated pattern of the ACT led.
Are you able to ssh directly to the device locally via balena ssh? The device may be intermittently disconnecting and reconnecting from our VPN, which could cause log delivery without terminal access.
Please let us know if you are able to access the device!
From what I can see from the logs (I’ve installed the Resin OS NetworkManager Debug Logs Collector), it seems that the logs are in correlation with your diagnosis. It loops with Connection reset, restarting [-1] and SIGUSR1[soft,connection-reset] received, process restarting.
do you have local mode enabled for this device? Can you access it via sudo balena local ssh ...? Can you please attach NetworkManager debug logs? I mean, the whole file for example, not just snippets.
Hi @Sara,
First of all I want to confirm that this device is running against balena-cloud and not an open-balena instance. Is that correct?
Can you clarify how that device ended up as Inactive?
Did you do that from the Dashboard’s actions menu or maybe you used a CLI command or CURL request to achieve that?
Inactive Devices get the inactive flag removed automatically once they connect to our backend and get online.
in the dashboard everything seems to be normal with the logs
Heya ! Could you attach the full log from the session, with DEBUG=1 prepended to the command ?
Also - there is a list of questions asked above - could you let us know the answers there as well ? This would help us debug the issue
Thanks !