Welcome to Radarspotting. Please login or sign up.

May 25, 2026, 05:45:07 PM

Login with username, password and session length

New Members

New Members

You should get an activation email when you join.  If not, please use the Contact option.

Fr24 feed stopped

Started by Triple7, October 05, 2024, 08:33:56 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Triple7

I hope this is the right place to post.

My FR24 feed from my RPi seems to have stopped. My feed to FA, via MSM2 to BaseStation and direct to PlanePlotter are all working as normal.

When I set this up originally, I used the following command from the FR24 web site:

wget -qO- https://fr24.com/install.sh | sudo bash -s
It has been working perfectly for many years, so I am at a loss to know what's happened. I have tried a reboot of the RPi but that didn't make any difference. Is there a stop/start/restart command I can give to get it going again?

Linux is definitely not my specialist subject, so if anyone can provide simple guidelines on what I could try, it would be much appreciated.

Thanks in advance.

Tim
SBS-1eR, FA ProStick + 1090 filter

Anmer

Hi Tim

What does your FR24 account Status show?

Business -> My Data Sharing -> Show Statistics

When was the last data feed?

Is your FA feed from the RPi or via BaseStation?

If you type the RPi IP address into a browser you should see the FR24 Decoder Status.  Do you?
Here to Help.

Triple7

Hi Mike,

A couple of screen grabs attached with suitable redactions.

I think the last feed was Thursday, but I don't know and I have not received an email telling my feed is off-line.
I actually spotted it yesterday as my account has dropped back to "basic".

My FA feed is from the Pi using Dump1090-fa. BaseStation uses the feed via MSM2 - also on the Pi.

Tim
SBS-1eR, FA ProStick + 1090 filter

Anmer

Thanks Tim

Have you tried a reinstall of the FR24 feed?

SSH into the RPi and run this command (same as before):

wget -qO- https://fr24.com/install.sh | sudo bash -s
Here to Help.

Triple7

That was actually the first thing I did, but I have done it again and rebooted the Pi and now I get the attached screen grab!

If I go to settings, I see my sharing key (correct) and receiver AVR(TCP) hit save but when I go back to the feeder page it's as per the attached.

Tim
SBS-1eR, FA ProStick + 1090 filter

Anmer

Try changing Receiver to:

ModeS Beast (TCP)
Here to Help.

Triple7

No change I'm afraid and I did click save and restart.
SBS-1eR, FA ProStick + 1090 filter

Anmer

Thanks Tim.  I assume you redacted the sharing key?

If you have a spare SD card, try installing just the FR24 feed and swap the card in the RPi.  Or try FR24 Support for help?
Here to Help.

Triple7

Yes, Mike correct on the key.

OK, I'll have a look at finding another card. I will also contact FR24 support.

Thanks for your help.

Tim,
SBS-1eR, FA ProStick + 1090 filter

wiedehopf

Some reports of the service not starting on boot.

Try this:

sudo systemctl enable --now fr24feed

Triple7

Thanks for the suggestion, unfortunately that didn't resolve the issue.

Tim
SBS-1eR, FA ProStick + 1090 filter

Anmer

#11
Ask FR24 Support if there's a log command you can run that will identify the status of the FR24 feed ont he SD card.  I'm sure they can help.

Edit

I've contacted FR24 and been asked to run this command:

journalctl -u fr24feed
Can you do this please Tim and paste the results (or at least the last 20-30 lines)?
Here to Help.

Triple7

More than 30 lines but hopefyully this will mean something:

Oct 07 06:01:03 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:02:18 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:03:33 raspberrypi fr24feed[490]: [time][e]Failed to synchronize time
Oct 07 06:03:33 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:05:39 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:06:40 raspberrypi fr24feed[490]: PacketSenderConfiguration::on_periodic_refresh: refreshing configuration
Oct 07 06:06:50 raspberrypi fr24feed[490]: [e]PacketSenderConfiguration::fetch_config(): Unable to fetch configuration for yoda receiver
Oct 07 06:06:54 raspberrypi fr24feed[490]: [time]Synchronizing time via NTP
Oct 07 06:06:54 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:07:29 raspberrypi fr24feed[490]: [feed][d]Fetching configuration
Oct 07 06:08:09 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:08:29 raspberrypi fr24feed[490]: [feed][e] Timeout was reached
Oct 07 06:08:29 raspberrypi fr24feed[490]: [feed][e]Could not retrieve configuration from Flightradar24!
Oct 07 06:08:29 raspberrypi fr24feed[490]: [feed][e]Request failed, code=0
Oct 07 06:08:29 raspberrypi fr24feed[490]: [feed]Failed on start, Sleeping 600 seconds
Oct 07 06:09:24 raspberrypi fr24feed[490]: [time][e]Failed to synchronize time
Oct 07 06:09:24 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:10:14 raspberrypi fr24feed[490]: [reader][w]Global timeout exceeded, 0 msgs, 5644164 resyncs, reconnecting
Oct 07 06:10:14 raspberrypi fr24feed[490]: [reader]Connection terminated
Oct 07 06:10:19 raspberrypi fr24feed[490]: [reader]Connecting to unknown receiver via (tcp://127.0.0.1:30002)
Oct 07 06:10:19 raspberrypi fr24feed[490]: [reader]Connected to the receiver, configuring
Oct 07 06:10:19 raspberrypi fr24feed[490]: [reader]Configured, processing messages
Oct 07 06:11:29 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:12:44 raspberrypi fr24feed[490]: [time]Synchronizing time via NTP
Oct 07 06:12:44 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:13:59 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:15:14 raspberrypi fr24feed[490]: [time][e]Failed to synchronize time
Oct 07 06:15:14 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:17:19 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:18:30 raspberrypi fr24feed[490]: [feed][d]Fetching configuration
Oct 07 06:18:34 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:18:34 raspberrypi fr24feed[490]: [time]Synchronizing time via NTP
Oct 07 06:19:30 raspberrypi fr24feed[490]: [feed][e] Timeout was reached
Oct 07 06:19:30 raspberrypi fr24feed[490]: [feed][e]Could not retrieve configuration from Flightradar24!
Oct 07 06:19:30 raspberrypi fr24feed[490]: [feed][e]Request failed, code=0
Oct 07 06:19:30 raspberrypi fr24feed[490]: [feed]Failed on start, Sleeping 600 seconds
Oct 07 06:19:49 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:20:19 raspberrypi fr24feed[490]: [reader][w]Global timeout exceeded, 0 msgs, 5953363 resyncs, reconnecting
Oct 07 06:20:19 raspberrypi fr24feed[490]: [reader]Connection terminated
Oct 07 06:20:24 raspberrypi fr24feed[490]: [reader]Connecting to unknown receiver via (tcp://127.0.0.1:30002)
Oct 07 06:20:24 raspberrypi fr24feed[490]: [reader]Connected to the receiver, configuring
Oct 07 06:20:24 raspberrypi fr24feed[490]: [reader]Configured, processing messages
Oct 07 06:21:04 raspberrypi fr24feed[490]: [time][e]Failed to synchronize time
Oct 07 06:21:04 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:23:09 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:24:24 raspberrypi fr24feed[490]: [time]Synchronizing time via NTP
Oct 07 06:24:24 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:25:39 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:26:55 raspberrypi fr24feed[490]: [time][e]Failed to synchronize time
Oct 07 06:26:55 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:29:00 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:29:30 raspberrypi fr24feed[490]: [feed][d]Fetching configuration
Oct 07 06:30:15 raspberrypi fr24feed[490]: [time]Synchronizing time via NTP
Oct 07 06:30:15 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:30:24 raspberrypi fr24feed[490]: [reader][w]Global timeout exceeded, 0 msgs, 5429777 resyncs, reconnecting
Oct 07 06:30:24 raspberrypi fr24feed[490]: [reader]Connection terminated
Oct 07 06:30:29 raspberrypi fr24feed[490]: [reader]Connecting to unknown receiver via (tcp://127.0.0.1:30002)
Oct 07 06:30:29 raspberrypi fr24feed[490]: [reader]Connected to the receiver, configuring
Oct 07 06:30:29 raspberrypi fr24feed[490]: [reader]Configured, processing messages
Oct 07 06:30:30 raspberrypi fr24feed[490]: [feed][e] Timeout was reached
Oct 07 06:30:30 raspberrypi fr24feed[490]: [feed][e]Could not retrieve configuration from Flightradar24!
Oct 07 06:30:30 raspberrypi fr24feed[490]: [feed][e]Request failed, code=0
Oct 07 06:30:30 raspberrypi fr24feed[490]: [feed]Failed on start, Sleeping 600 seconds
Oct 07 06:31:30 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:32:45 raspberrypi fr24feed[490]: [time][e]Failed to synchronize time
Oct 07 06:32:45 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:34:50 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:36:05 raspberrypi fr24feed[490]: [time]Synchronizing time via NTP
Oct 07 06:36:05 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:37:20 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:38:35 raspberrypi fr24feed[490]: [time][e]Failed to synchronize time
Oct 07 06:38:35 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:40:29 raspberrypi fr24feed[490]: [reader][w]Global timeout exceeded, 0 msgs, 5278011 resyncs, reconnecting
Oct 07 06:40:29 raspberrypi fr24feed[490]: [reader]Connection terminated
Oct 07 06:40:31 raspberrypi fr24feed[490]: [feed][d]Fetching configuration
Oct 07 06:40:34 raspberrypi fr24feed[490]: [reader]Connecting to unknown receiver via (tcp://127.0.0.1:30002)
Oct 07 06:40:34 raspberrypi fr24feed[490]: [reader]Connected to the receiver, configuring
Oct 07 06:40:34 raspberrypi fr24feed[490]: [reader]Configured, processing messages
Oct 07 06:40:40 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:41:31 raspberrypi fr24feed[490]: [feed][e] Timeout was reached
Oct 07 06:41:31 raspberrypi fr24feed[490]: [feed][e]Could not retrieve configuration from Flightradar24!
Oct 07 06:41:31 raspberrypi fr24feed[490]: [feed][e]Request failed, code=0
Oct 07 06:41:31 raspberrypi fr24feed[490]: [feed]Failed on start, Sleeping 600 seconds
Oct 07 06:41:55 raspberrypi fr24feed[490]: [time]Synchronizing time via NTP
Oct 07 06:41:55 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:43:10 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
Oct 07 06:44:25 raspberrypi fr24feed[490]: [time][e]Failed to synchronize time
Oct 07 06:44:25 raspberrypi fr24feed[490]: [W] ares_static_callback - 4 timeouts reported (status 12)
lines 4949-4971/4971 (END)
SBS-1eR, FA ProStick + 1090 filter

Anmer

Thanks Tim, hopefully FR24 will diagnose that.
Here to Help.

Anmer

FR24 response:

QuoteLooks like DNS is not working, can't resolve hostnames - (ares_static_callback) this is a timeout error from the DNS library.

Maybe a router reboot?
Here to Help.