I am looking for a way to better diagnosis why I have a fin that keeps going offline in the middle of the night.
I know it isn’t connected to the wifi network because I checked the router and tried to ssh indirectly.
I have it here in my office so I can restart it and connect to it directly, but I need to figure out why this is happening between my current version of the code and not in the last version.
Some things I added:
I unmanaged eth0 in the network manager to avoid it continuously scanning for an ip. This is only an issue because of my custom power delivery here.
'nmcli device set ' + adapter + ' managed no'
The relevant section of the docker file:
FROM balenalib/raspberrypi3-debian-python:3.6.8-buster-build RUN apt-get update && apt-get install -y \ network-manager=1.14.* \ tcpdump=4.9.* \ openssh-client=1:7.* \ iw=5.0.* \ net-tools=1.60* \ wireless-tools=30* \ sshpass=1.06* \ procps \ && rm -rf /var/lib/apt/lists/* && systemctl mask NetworkManager.service &&\ apt-get clean ENV DBUS_SYSTEM_BUS_ADDRESS=unix:path=/host/run/dbus/system_bus_socket
The device is primarily connected via wifi normally so I don’t see why this was an issue and I did this during the start of my container which then ran for serval hours before there was a problem.
My application itself is fairly simple. It uses tcpdump to monitor 3 network interfaces that I rename with a udev rule, and un-monitor in the same way.
The only new thing I added was more multithreading.
I am looking at what I am doing with the network manager because I know that is most likely the root cause of any issues, but is there anything else I can look at.
Also is there any way to connect to it via a serial connection, maybe over USB? I think I saw that mentioned somewhere, but I can’t find anything on it.