Board Becomes Unresponsive to Remote Connections After a Time

[uninvitedguest]

Hey all.

 

Running the Dec 9th build of Armbian 22.11.2 Debian Bullseye CLI, and I've been running in to issues with consistently remotely connecting to the board. While ssh and other direct connections (IP:Port for services like Nextcloud, etc) work for a bit after a recent reboot, after some unknown amount of uptime I'm unable to connect to the board through any new remote connections. Attempting an SSH session provides me the error

ssh: connect to host 192.168.50.5 port 22: No route to host

 

When connected via the serial console, I am able to verify that the board has internet access while it is refusing these remote connections on the local network.

 

When I restart the board it starts accepting remote connections again.

 

Not sure what to do to troubleshoot this or if anyone else is dealing with the issue.

[Myron]

Please provide diagnostic logs with ...

armbianmonitor -u

... and post the link here.  It'll may help others determine what the issue is.

[uninvitedguest]

Okay, at one point I was able to run armbianmonitor -u, but I wasn't able to post due to the daily post limit here. Now, when I attempt to run it I receive the following:

 

rock-5b:user:# armbianmonitor -u
System diagnosis information will now be uploaded to https://paste.armbian.com/
https://paste.armbian.com/
https://paste.armbian.com/
https://paste.armbian.com/
https://paste.armbian.com/
https://paste.armbian.com/
https://paste.armbian.com/
Please post the URL in the forum where you've been asked for.

 

Luckily, the link was in my browser history. Here's the output: https://paste.armbian.com/alayababaf

[uninvitedguest]

As a fun new quirk, after having my board offline for a number of days, I've booted it up and the device mac address has changed - resulting in the DHCP server on my router assigning it a random IP address, even though armbian-config had been set to static as well.

[achachiez]

@uninvitedguest  I am experiencing this one of the three boards I have. From what I have seen, a system crash caused this, but I can't tell what caused it. @Myron, here is a link to my debug info https://paste.armbian.com/iqivalulam

[jrstarke]

Strangely I saw something similar with my Rock 5B when I was running it as a k3s control-plane node. Dropping it back to just a normal node, the problem appears to have gone away. Unsure what the difference is. Once I get another control-plane node running, I'll add it back in, and get a monitor log.