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
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?
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
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
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
Try changing Receiver to:
ModeS Beast (TCP)
No change I'm afraid and I did click save and restart.
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?
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,
Some reports of the service not starting on boot.
Try this:
sudo systemctl enable --now fr24feed
Thanks for the suggestion, unfortunately that didn't resolve the issue.
Tim
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)?
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)
Thanks Tim, hopefully FR24 will diagnose that.
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?
Tried that - no change. FA feed is working perfectly though.
Do you have any AV apps that may be blocking the FR24 feed?
Have you contacted FR24 Support? Piotr says an SSH connection might identify the issue more precisely.
I don't have any 3rd party AV stuff installed on the Pi. The setup has been working for ages and seems to have stopped on Thursday last week - it just sits in my loft minding its own business.
Yes, I have contacted FR24 support, I received an automated email but nothing further.
I can SSH into the Pi wihtout any problems - what am I looking for?
Thanks,
Tim
Quote from: Triple7 on October 07, 2024, 12:09:35 PMI can SSH into the Pi wihtout any problems - what am I looking for?
I think Piotr was suggesting FR24 need to SSH and take a look.
Do you have a ref number from FR24 Support? For the automatic acknowledgement?
Yes; 639659
Tim
This is Piotr's suggestion regarding remote SSH to the RPi:
QuoteIf he can forward a port and provide credentials then yes,, we can log in and take a look.
I can forward a port but I don't know what credentials are required or where to send them. Would it be possible to set up a remote session, I can then log into the Pi and give access that way?
I haven't heard anything more in connection with the open ticket.
The credentials will be your RPi login/password.
You'll need to discuss the remote session options with FR24 Support. I'm not sure what SLA is in place for responding to support requests.
To close this thread out. After a couple of dozen emails back and forth to FR24 support, we finally sorted out the issue.
Studying this file:
sudo nano /etc/dhcpcd.conf
It seems that the entry - static domain_name_servers=192.168.1.254 was incorrect as my router has an IP of 192.168.1.1. Also, it was suggested to add in Google's public dns server. So that line was amended to:
static domain_name_servers=192.168.1.1 8.8.8.8
After a reboot and a bit of a wait, things have been restored.
It should be noted that my FA feed was unaffected by the apparent incorrect setting.
I have a vague recollection that I might have changed that setting when I swapped a router over for a couple of days in June and that replacement router did have the IP address of 192.168.1.254 so I may have amended the file on the Pi and then subsequently forgot to swap it back when I reinstalled the original router.
Still, it seems to be behaving now.
Tim
Thanks for the update Tim. Glad to hear all is well again.
And FR24 Support helped sort it out for you.