RPi stopped comms with FA?

[SDMark]

My RPi dumping to FA, FR24, and ADSBexchange has been chugging along for few weeks with no issues. This morning I got an email from FA saying it hadn’t heard from my Pi in over 12 hours. I checked the Pi, and it seemed happy - dump1090, piaware, and fr24feed services all reported no issues.

I checked tar1090 (local to the Pi), and it showed planes being detected. I checked FR24 and filtered for my site - it showed those same planes were getting through to FR24. I checked Skyaware, and it showed nothing - my stats page saying it had been hours since the feeder checked in.

At a loss for what was up, I rebooted the Pi, and waited - a few minutes later, FA was seeing the site and reporting planes.

So I fixed it (I guess?), but I don’t have any idea why it just decided to stop sending data - or perhaps why FA stopped receiving data (since it appears I was sending data, elsewhere at least). I’ve not encountered this behavior before - has anyone else seen it and/or have thoughts about what might have happened and how to avoid it in the future?

[Devonian]

Perhaps related to this thread?

Not uploading data to Flightaware but ADSB and 24 loading up OK

I noticed the same data loss to Flightaware after disabling ipv6 on my R-Pi. Locally, everything was running fine, but I later got an email from Flightaware that I wasn’t feeding?! Thank goodness for the email otherwise I might have lost my 7 year streak. It’s simple to replicate the ‘problem’ - just add “ipv6.disable=1” to the end of /boot/cmdline.txt and reboot. Good to see Flightaware are on top of it and will have a fix in due course. Nigel.

Nigel

[SDMark]

Hmm. I didn’t manually/intentionally do anything different to reset IPv6, but maybe something auto updated?
I’ll give this a check, thanks!

[nasdisco]

All electronics need a reset or reboot from time to time.