First things first, happy new year! Hopefully 2021 will be a much better year.
Next up, over the weekend I had a RPI4 with BalenaOS v2.65.0+rev1 (dev), supervisor v12.2.11 that “crashed”. The RPI4 is not in local mode and downloads and runs the releases from the openBalena server. One of the containers ping’s our server, and about 01:00 it went offline and didn’t ping anymore. I logged in via our VPN at the office and tried to SSH into it, but it timed out.
Today, I came back at the office and tried to find out what was wrong. First thing I noticed is that the Ethernet port of the RPI4 had both lights on, but they were solid on. No flickering as always.
The Node.js application that’s supposed to run on the RPI4, also creates (via the NetworkManager’s DBUS API) an access point via wlan0. But that access point was gone. I hoped that I could SSH via the Access Point to gather some logs.
Raspberry Pi 4 (2GB RAM)
BalenaOS 2.65.0+rev1 (development image)
32GB SanDisk Max Endurance SD-card
openBalena server v3.1.1
Running 3 containers (redis, custom Node.js application, custom Golang application with serial communication, so
enable_uart=1 is added to the config.txt via environment variables)
Another RPI4, which is being tested by our client, also has the same specs as above, but that’s a production image. This is running for 14 days now without a crash. It runs the same containers and I don’t see CPU spikes, high CPU temperatures or a memory leak there.
I’m happy to share additional information. I had to restart the RPI4 because it was ‘dead’. After a hard reset (cut power), it booted fine and is running again. I hope someone can do anything with this information.
Thanks in advance!