My feeder is a recent addition and the first one I have assembled, UID QLvS_Der7bJk. It is built from a Pi 4, Nooelec Flycatcher, Nooelec SAWBird+, and self built antennas with wired ethernet. I had been running the antennas initially in the basement for about the first week, moved the 1090 to the first floor for about a week, and then both into the attic during Jan. 11th. Overnight, my feeder experienced a complete halts of all CPU activity that required hard power of and on reset to get going again. I had tried a "save and restart" via the http://local_ip_addr/config/ link, but it was not enough to restore feed status. There were 2 short halts before I went to sleep and the feeder stopped overnight while I was asleep for 3 hours and again required a hard power reset.
Since that reset, I have made sure to close all local feeder web server pages and to not tax the Pi. I think the issue has to do with keeping multiple instances of the http://local_ip_addr/tar1090/ page open on multiple devices in my house. Overall CPU utilization less than 10%. Keeping the local page serving traffic to the Pi at minimums seems to allow the feeder to keep running.
What I am seeing now are odd dropouts of ADS-B 1090 Tracks and ADS-B CPU Utilization at about 20 minute intervals. I spoke too soon, while I have been writing this, the feeder completely halted again. With the power off reset, the feeder seems to have lost 9 hours of Performance Graph data.
I have a lot of screen capture and some log data captured. What would be most useful for me to post for diagnosing this trouble?
Thank you!