RPi4b Buster upgrade to 1-0-37-0 broke feed

[bumpy_up_here]

Hi,

I did a general (not fr24feed) update today using
sudo apt update
sudo apt upgrade

This 'upgraded' my fr24feed from 1-0-34-0 to 1-0-37-0

My feed then failed and no amount of restarts would fix it, so I downgraded back to 1-0-34-0 and it's feeding fine again.

Discuss......

Edit - have just noticed that my other pi feeder (at a different location) is running and feeding OK using -037 - this is a RPi3b+, so now am confused as to why one is fine with the latest version and the other is not. Both are running Buster and are regularly updated. The only major difference I can see is the one that fails has both Wired and Wireless interfaces configured, whereas the RPi3 only has Wired setup.

Streety.

[mby]

Same here, error msgs are:

2023-02-28 18:27:46 | [mlat][i]Pinging the server
2023-02-28 18:27:46 | [mlat][i]Stats 988733/252
2023-02-28 18:27:50 | [feed][i]sent 1,12 AC
2023-02-28 18:27:50 | 23-02-28 18:27:50.511 [D][:] sent 1 of 13 aircraft, 12 ignored, 0 outdated
2023-02-28 18:27:55 | [feed][i]sent 1,12 AC
2023-02-28 18:27:55 | 23-02-28 18:27:55.807 [D][:] sent 1 of 13 aircraft, 12 ignored, 0 outdated
2023-02-28 18:28:00 | [reader][i]Connection terminated
2023-02-28 18:28:05 | [reader][i]Connecting to unknown receiver via (tcp://localhost:30005)
2023-02-28 18:28:05 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to tcp://localhost:30005
2023-02-28 18:28:06 | [mlat][i]Pinging the server
2023-02-28 18:28:06 | [mlat][i]Stats 988939/206
2023-02-28 18:28:10 | [reader][i]Connecting to unknown receiver via (tcp://localhost:30005)
2023-02-28 18:28:10 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to tcp://localhost:30005
2023-02-28 18:28:15 | [reader][i]Connecting to unknown receiver via (tcp://localhost:30005)
2023-02-28 18:28:15 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to tcp://localhost:30005

[IZ8292SWL]

I updated to 1.0.37-0 this morning and it went offline.
I had to restart the whole raspberry server. Is that normal? I lost 1 month of online service

[bumpy_up_here]

And to make matters worse, after my successful downgrade yesterday, I received an email just now stating my feed had been offline...guess what....it had updated by itself to -037 again.

I will do some research, but does anyone know off the top of their head, how to stop it updating automatically, please?

MTIA
Streety

After (more) research, /etc/cron.d/fr24feed_updater needs editing (as root) to insert a # at the start of the file so it won't run - at least that's what I'm hoping.

In my case, there is a cron entry at 08:49 every morning to run the updater script - now it won't run, I hope.

[Oblivian]

Usual radio silence warning of update release and to test for problem's without any post update tips before shoving it to everyone

Unsurprising.

You can see why I prefer to do mine manually on my schedule after everyone else has found the kinks

[elljay]

You can see why I prefer to do mine manually on my schedule after everyone else has found the kinks

Me too! Especially since the Changelog says nothing since 1.0.34-0 !!

[Zeven]

Mine is running normally with 1.0.37.0 but the range has dropped about 20NM since the update. Wonder why

[fribse]

I got it fixed by pulling a new image, and using the auto update to .37, and entering they key again.

[luisrzf]

Hi,

I've not found the way to downgrade from 1.0.37 to 1.0.34.
Could you please tell me how to do it?

[wiedehopf]

Install readsb and then run the section on feeding fr24: https://github.com/wiedehopf/adsb-wi...ADS-B-receiver

That will go to 1.0.34 and disable all auto updates.