Announcement

Collapse
No announcement yet.

Flightradar24 page reports "No data" or offline while the feeder is up and running

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    Flightradar24 page reports "No data" or offline while the feeder is up and running

    I'm running fr24feed in a Docker container provided by Thom-x/docker-fr24feed-piaware-dump1090. The container and its services are running just fine but the FR24 data sharing page either reports "Online - No data" or even switches to offline. The restart of FR24 feeder brings the page back to "Online", however still not data.

    This is how it looks like so far:
    fr24_status_page.png

    Some additional information about the running system

    FR24 Feeder status:
    fr24_feeder_status_page.png

    FR24feed configuration:
    Code:
    root@flightradar24:~# cat /etc/fr24feed.ini

bs="no"
fr24key="****************"
host="127.0.0.1:30005"
logmode="1"
logpath="/tmp"
mlat="no"
raw="no"
receiver="beast-tcp"
    FR24feed log (full log attached):
    Code:
    2023-02-10 00:05:45 | 23-02-10 00:06:04.721 [I][receiver_ac_sender.cpp:53] [feed][n]waiting 18 seconds
2023-02-10 00:06:03 | [feed][n]UKLL24@185.218.24.22:8099/UDP
2023-02-10 00:06:03 | 23-02-10 00:06:22.721 [I][receiver_ac_sender.cpp:36] Network thread connecting to 185.218.24.22:8099 for feed UKLL24
2023-02-10 00:06:03 | [feed][n]connecting
2023-02-10 00:06:03 | [feed][n]connected via UDP (fd 23)
2023-02-10 00:06:03 | [feed][n]working
2023-02-10 00:06:33 | [feed][n]ping 1
2023-02-10 00:06:34 | [feed][n]syncing stream result: 1
2023-02-10 00:09:00 | [feed][n]ping 1
2023-02-10 00:09:46 | [feed][n]syncing stream: timeout
2023-02-10 00:10:07 | [feed][n]ping 1
2023-02-10 00:10:37 | [feed][n]disconnected
2023-02-10 00:10:37 | 23-02-10 00:10:56.412 [I][receiver_ac_sender.cpp:53] [feed][n]waiting 20 seconds
2023-02-10 00:10:57 | [feed][n]UKLL24@185.218.24.23:8099/UDP
2023-02-10 00:10:57 | [feed][n]connecting
2023-02-10 00:10:57 | 23-02-10 00:11:16.412 [I][receiver_ac_sender.cpp:36] Network thread connecting to 185.218.24.23:8099 for feed UKLL24
2023-02-10 00:10:57 | [feed][n]connected via UDP (fd 23)
2023-02-10 00:10:57 | [feed][n]working
2023-02-10 00:11:27 | [feed][n]ping 1
2023-02-10 00:11:28 | [feed][n]syncing stream result: 1
2023-02-10 00:11:57 | [feed][n]ping 2
2023-02-10 00:11:58 | [feed][n]syncing stream result: 1
2023-02-10 00:12:27 | [feed][n]ping 3
2023-02-10 00:12:28 | [feed][n]syncing stream result: 1
2023-02-10 00:12:57 | [feed][n]ping 4
2023-02-10 00:12:58 | [feed][n]syncing stream result: 1
2023-02-10 00:13:00 | 23-02-10 00:13:19.530 [I][crxstats_sender.cpp:84] [stats]sent 16 bytes
2023-02-10 00:13:54 | [feed][n]ping 1
2023-02-10 00:13:55 | [feed][n]syncing stream result: 1
2023-02-10 00:14:24 | [feed][n]ping 2
2023-02-10 00:14:25 | [feed][n]syncing stream result: 1
2023-02-10 00:15:07 | [feed][n]ping 1
2023-02-10 00:15:08 | [feed][n]syncing stream result: 1
    I've checked UDP connectivity to FR24 server -- all works!
    Code:
    Connection to 185.218.24.23 8099 port [udp/*] succeeded!
    At the same time FlightAware page is displaying correct and live data (as well as the other platforms):
    fa_status_page.png
    Attached Files
    Last edited by rpavlyuk; 2023-02-09, 22:36.
    Tags: None
  • #2
    Full log file:
    Code:
    2023-02-09 23:33:17 | ______ _ _ _ _ _ _____ ___
2023-02-09 23:33:17 | | ___|| |(_) | | | | | | / __ \ / |
2023-02-09 23:33:17 | | |_ | | _ __ _ | |__ | |_ _ __ __ _ __| | __ _ _ __`' / /' / /| |
2023-02-09 23:33:17 | | _| | || | / _` || '_ \ | __|| '__|/ _` | / _` | / _` || '__| / / / /_| |
2023-02-09 23:33:17 | | | | || || (_| || | | || |_ | | | (_| || (_| || (_| || | ./ /___\___ |
2023-02-09 23:33:17 | \_| |_||_| \__, ||_| |_| \__||_| \__,_| \__,_| \__,_||_| \_____/ |_/
2023-02-09 23:33:17 | __/ |
2023-02-09 23:33:17 | |___/
2023-02-09 23:33:17 | [main][i]FR24 Feeder/Decoder
2023-02-09 23:33:17 | [main][i]Version: 1.0.34-0/generic
2023-02-09 23:33:17 | [main][i]Built on Jan 10 2023 10:09:01 (decoder-v1.0.34-0-7c5301b.git/Linux/static_amd64)
2023-02-09 23:33:17 | [main][i]Running on: debian="11"
2023-02-09 23:33:17 | [main][i]Local IP(s): 172.17.0.2
2023-02-09 23:33:17 | [main][i]Copyright 2012-2023 Flightradar24 AB
2023-02-09 23:33:17 | [main][i]https://www.flightradar24.com
2023-02-09 23:33:17 | [main][i]DNS mode: PING
2023-02-09 23:33:17 | [main][i]Automatic updates are DISABLED
2023-02-09 23:33:17 | 23-02-09 23:33:17.354 [E][:] Local time: 2023-02-09 23:33:17 +0200
2023-02-09 23:33:17 | 23-02-09 23:33:17.354 [E][:] GMT+0 time: 2023-02-09 21:33:17 +0200
2023-02-09 23:33:17 | 23-02-09 23:33:17.354 [E][:] Your machine should be set as GMT+0 time zone!
2023-02-09 23:33:17 | 23-02-09 23:33:17.354 [W][:] Time zone is not set to GMT+0
2023-02-09 23:33:17 | 23-02-09 23:33:17.354 [I][http-server.cpp:270] [httpd]Server started, listening on :::8754
2023-02-09 23:33:17 | [i]PacketSenderConfiguration::fetch_config(): Yoda configuration for this receiver is disabled
2023-02-09 23:33:17 | [d]TLSConnection::ctor(): Enable verify_peer in production code!
2023-02-09 23:33:17 | [main][i]Reader thread started
2023-02-09 23:33:17 | [master][i]Starting processing thread
2023-02-09 23:33:17 | [reader][i]Initializing reader
2023-02-09 23:33:17 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
2023-02-09 23:33:17 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to tcp://127.0.0.1:30005
2023-02-09 23:33:18 | [time][i]Synchronizing time via NTP
2023-02-09 23:32:59 | [time][i]Time synchronized correctly, offset -19.257 seconds
2023-02-09 23:32:59 | [feed][i]Downloading configuration
2023-02-09 23:32:59 | [main][i]Feed Network client started
2023-02-09 23:32:59 | [feed][d]fetching configuration
2023-02-09 23:32:59 | [feed][i]configuring decoder
2023-02-09 23:32:59 | [feed][c]Max range AIR: 350.0nm
2023-02-09 23:32:59 | [feed][c]Max range GND: 100.0nm
2023-02-09 23:32:59 | [feed][i]configuration changed
2023-02-09 23:32:59 | [feed][i]defined 3 servers
2023-02-09 23:32:59 | [feed][c]Timestamps: optional
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [E][:] Local time: 2023-02-09 23:33:18 +0200
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [E][:] GMT+0 time: 2023-02-09 21:33:18 +0200
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [E][:] Your machine should be set as GMT+0 time zone!
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [W][:] Time zone is not set to GMT+0
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [I][receiver_ac_sender.cpp:137] Stopping ReceiverACSender threads for feed
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [D][receiver_ac_sender.cpp:141] Stop called on non-running network thread for feed
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [I][receiver_ac_sender.cpp:96] Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.2 4:8099, feed: UKLL24, send_interval: 5s/1s, max age: 15s, send metadata: true, mode: 1, filtering: true
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [E][:] Local time: 2023-02-09 23:33:18 +0200
2023-02-09 23:32:59 | [feed][n]UKLL24@185.218.24.22:8099/UDP
2023-02-09 23:32:59 | [feed][n]connecting
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [E][:] GMT+0 time: 2023-02-09 21:33:18 +0200
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [E][:] Your machine should be set as GMT+0 time zone!
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [W][:] Time zone is not set to GMT+0
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [I][crxstats.cpp:588] [stats]Stats thread started
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [E][:] Local time: 2023-02-09 23:33:18 +0200
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [E][:] GMT+0 time: 2023-02-09 21:33:18 +0200
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [E][:] Your machine should be set as GMT+0 time zone!
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [W][:] Time zone is not set to GMT+0
2023-02-09 23:32:59 | 23-02-09 23:33:18.783 [I][receiver_ac_sender.cpp:36] Network thread connecting to 185.218.24.22:8099 for feed UKLL24
2023-02-09 23:32:59 | [feed][n]connected via UDP (fd 23)
2023-02-09 23:32:59 | [feed][n]working
2023-02-09 23:33:03 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
2023-02-09 23:33:03 | [reader][i]Connected to the receiver, configuring
2023-02-09 23:33:03 | [reader][i]Configured, processing messages
2023-02-09 23:33:29 | [feed][n]ping 1
2023-02-09 23:33:30 | [feed][n]syncing stream result: 1
2023-02-09 23:33:59 | [feed][n]ping 2
2023-02-09 23:34:00 | [feed][n]syncing stream result: 1
2023-02-09 23:34:29 | [feed][n]ping 3
2023-02-09 23:34:30 | [feed][n]syncing stream result: 1
2023-02-09 23:34:59 | [feed][n]ping 4
2023-02-09 23:35:00 | [feed][n]syncing stream result: 1
2023-02-09 23:35:29 | [feed][n]ping 5
2023-02-09 23:35:30 | [feed][n]syncing stream result: 1
2023-02-09 23:35:59 | [feed][n]ping 6
2023-02-09 23:36:00 | [feed][n]syncing stream result: 1
2023-02-09 23:36:11 | [reader][i]Timestamp source changed from UNKNOWN to SYSTEM-VALIDATED
2023-02-09 23:36:29 | [feed][n]ping 7
2023-02-09 23:36:30 | [feed][n]syncing stream result: 1
2023-02-09 23:37:56 | [feed][n]ping 1
2023-02-09 23:37:57 | [feed][n]syncing stream result: 1
2023-02-09 23:42:59 | 23-02-09 23:43:19.015 [I][crxstats_sender.cpp:84] [stats]sent 16 bytes
2023-02-09 23:43:01 | [feed][n]syncing stream async: 1
2023-02-09 23:43:46 | [feed][n]syncing stream: timeout
2023-02-09 23:45:17 | [feed][n]syncing stream async: 1
2023-02-09 23:46:03 | [feed][n]syncing stream: timeout
2023-02-09 23:47:40 | [feed][n]syncing stream async: 1
2023-02-09 23:48:25 | [feed][n]syncing stream: timeout
2023-02-09 23:48:26 | [feed][n]disconnected
2023-02-09 23:48:26 | 23-02-09 23:48:46.146 [I][receiver_ac_sender.cpp:53] [feed][n]waiting 6 seconds
2023-02-09 23:48:32 | [feed][n]UKLL24@185.218.24.23:8099/UDP
2023-02-09 23:48:32 | [feed][n]connecting
2023-02-09 23:48:32 | 23-02-09 23:48:52.146 [I][receiver_ac_sender.cpp:36] Network thread connecting to 185.218.24.23:8099 for feed UKLL24
2023-02-09 23:48:32 | [feed][n]connected via UDP (fd 23)
2023-02-09 23:48:32 | [feed][n]working
2023-02-09 23:50:03 | [feed][n]syncing stream async: 1
2023-02-09 23:50:04 | [feed][n]syncing stream result: 1
2023-02-09 23:52:09 | [feed][n]syncing stream async: 1
2023-02-09 23:52:55 | [feed][n]syncing stream: timeout
2023-02-09 23:52:59 | 23-02-09 23:53:19.178 [I][crxstats_sender.cpp:84] [stats]sent 16 bytes
2023-02-09 23:54:28 | [feed][n]syncing stream async: 1
2023-02-09 23:55:13 | [feed][n]syncing stream: timeout
2023-02-09 23:55:18 | [time][i]Synchronizing time via NTP
2023-02-09 23:55:18 | [time][i]Time synchronized correctly, offset -19.280 seconds, drift -0.001 seconds/minute
2023-02-09 23:56:50 | [feed][n]syncing stream async: 1
2023-02-09 23:57:36 | [feed][n]syncing stream: timeout
2023-02-09 23:57:36 | [feed][n]disconnected
2023-02-09 23:57:36 | 23-02-09 23:57:55.508 [I][receiver_ac_sender.cpp:53] [feed][n]waiting 10 seconds
2023-02-09 23:57:46 | [feed][n]UKLL24@185.218.24.24:8099/UDP
2023-02-09 23:57:46 | 23-02-09 23:58:05.508 [I][receiver_ac_sender.cpp:36] Network thread connecting to 185.218.24.24:8099 for feed UKLL24
2023-02-09 23:57:46 | [feed][n]connecting
2023-02-09 23:57:46 | [feed][n]connected via UDP (fd 23)
2023-02-09 23:57:46 | [feed][n]working
2023-02-09 23:59:19 | [feed][n]syncing stream async: 1
2023-02-09 23:59:20 | [feed][n]syncing stream result: 1
2023-02-10 00:01:26 | [feed][n]syncing stream async: 1
2023-02-10 00:01:27 | [feed][n]syncing stream result: 1
2023-02-10 00:03:00 | 23-02-10 00:03:19.365 [I][crxstats_sender.cpp:84] [stats]sent 16 bytes
2023-02-10 00:04:10 | [feed][n]syncing stream async: 1
2023-02-10 00:04:56 | [feed][n]syncing stream: timeout
2023-02-10 00:05:15 | [feed][n]ping 1
2023-02-10 00:05:45 | [feed][n]disconnected
2023-02-10 00:05:45 | 23-02-10 00:06:04.721 [I][receiver_ac_sender.cpp:53] [feed][n]waiting 18 seconds
2023-02-10 00:06:03 | [feed][n]UKLL24@185.218.24.22:8099/UDP
2023-02-10 00:06:03 | 23-02-10 00:06:22.721 [I][receiver_ac_sender.cpp:36] Network thread connecting to 185.218.24.22:8099 for feed UKLL24
2023-02-10 00:06:03 | [feed][n]connecting
2023-02-10 00:06:03 | [feed][n]connected via UDP (fd 23)
2023-02-10 00:06:03 | [feed][n]working
2023-02-10 00:06:33 | [feed][n]ping 1
2023-02-10 00:06:34 | [feed][n]syncing stream result: 1
2023-02-10 00:09:00 | [feed][n]ping 1
2023-02-10 00:09:46 | [feed][n]syncing stream: timeout
2023-02-10 00:10:07 | [feed][n]ping 1
2023-02-10 00:10:37 | [feed][n]disconnected
2023-02-10 00:10:37 | 23-02-10 00:10:56.412 [I][receiver_ac_sender.cpp:53] [feed][n]waiting 20 seconds
2023-02-10 00:10:57 | [feed][n]UKLL24@185.218.24.23:8099/UDP
2023-02-10 00:10:57 | [feed][n]connecting
2023-02-10 00:10:57 | 23-02-10 00:11:16.412 [I][receiver_ac_sender.cpp:36] Network thread connecting to 185.218.24.23:8099 for feed UKLL24
2023-02-10 00:10:57 | [feed][n]connected via UDP (fd 23)
2023-02-10 00:10:57 | [feed][n]working

    Comment

    • #3
      All those pings, and connection refused. It's not getting the data it's expecting.

      Beit your feeders configuration or networking thing which we seem to be seeing more and more of with containerising apps and impacting direct connection ability
      Posts not to be taken as official support representation - Just a helpful uploader who tinkers

      Comment

      • #4
        Is there any tool / approach I can use to check the connectivity? Everything was fine with connectivity for almost three years until last 5 days.

        I tried testing UDP connectivity from the same container using
        Code:
        netcat
        and it all worked well:
        fr24_nc_udp.png

        Also, in the log file I'm seeing that something isn't going well but there's no information what exactly:
        Code:
        2023-02-10 10:39:28 | 23-02-10 10:39:47.715 [I][crxstats_sender.cpp:84] [stats]sent 16 bytes
2023-02-10 10:39:42 | [feed][n]syncing stream async: 1
2023-02-10 10:39:43 | [feed][n]syncing stream result: 1
2023-02-10 10:41:44 | [feed][n]syncing stream async: 1
2023-02-10 10:41:45 | [feed][n]syncing stream result: 1
2023-02-10 10:44:21 | [feed][n]syncing stream async: 1
2023-02-10 10:45:07 | [feed][n]syncing stream: timeout
2023-02-10 10:46:43 | [feed][n]syncing stream async: 1
2023-02-10 10:47:28 | [feed][n]syncing stream: timeout
2023-02-10 10:49:00 | [feed][n]syncing stream async: 1
2023-02-10 10:49:29 | 23-02-10 10:49:47.884 [I][crxstats_sender.cpp:84] [stats]sent 16 bytes
2023-02-10 10:49:31 | [time][i]Synchronizing time via NTP
2023-02-10 10:49:31 | [time][e]Failed to synchronize time
2023-02-10 10:49:32 | [reader][i]Timestamp source changed from SYSTEM-VALIDATED to SYSTEM-UNCERTAIN
2023-02-10 10:49:38 | [time][i]Synchronizing time via NTP
2023-02-10 10:49:38 | [time][i]Time synchronized correctly, offset -18.756 seconds, drift -0.000 seconds/minute
2023-02-10 10:49:39 | [reader][i]Timestamp source changed from SYSTEM-UNCERTAIN to SYSTEM-VALIDATED
2023-02-10 10:49:45 | [feed][n]syncing stream: timeout
2023-02-10 10:49:46 | [feed][n]disconnected
2023-02-10 10:49:46 | 23-02-10 10:50:05.609 [I][receiver_ac_sender.cpp:53] [feed][n]waiting 26 seconds
2023-02-10 10:50:12 | 23-02-10 10:50:31.609 [W][receiver_ac_sender.cpp:59] Exited network thread for feed UKLL24
2023-02-10 10:50:12 | [feed][d]fetching configuration
2023-02-10 10:50:12 | [feed][i]decoder config not changed
2023-02-10 10:50:12 | [feed][i]configuration changed
2023-02-10 10:50:12 | [feed][i]defined 3 servers
2023-02-10 10:50:12 | [feed][c]Timestamps: optional
2023-02-10 10:50:12 | 23-02-10 10:50:31.730 [I][receiver_ac_sender.cpp:137] Stopping ReceiverACSender threads for feed UKLL24
2023-02-10 10:50:12 | 23-02-10 10:50:31.730 [I][receiver_ac_sender.cpp:145] Joined network thread for feed UKLL24
2023-02-10 10:50:12 | 23-02-10 10:50:31.730 [I][receiver_ac_sender.cpp:96] Configured ReceiverACSender: 185.218.24.22:8099,185.218.24.23:8099,185.218.24.2 4:8099, feed: UKLL24, send_interval: 5s/1s, max age: 15s, send metadata: true, mode: 1, filtering: t
rue
2023-02-10 10:50:12 | 23-02-10 10:50:31.730 [E][:] Local time: 2023-02-10 10:50:31 +0200
2023-02-10 10:50:12 | [feed][n]UKLL24@185.218.24.22:8099/UDP
2023-02-10 10:50:12 | 23-02-10 10:50:31.730 [E][:] GMT+0 time: 2023-02-10 08:50:31 +0200
2023-02-10 10:50:12 | 23-02-10 10:50:31.730 [E][:] Your machine should be set as GMT+0 time zone!
2023-02-10 10:50:12 | [feed][n]connecting
2023-02-10 10:50:12 | 23-02-10 10:50:31.730 [W][:] Time zone is not set to GMT+0
2023-02-10 10:50:12 | 23-02-10 10:50:31.730 [I][receiver_ac_sender.cpp:36] Network thread connecting to 185.218.24.22:8099 for feed UKLL24
2023-02-10 10:50:13 | [feed][n]connected via UDP (fd 23)
2023-02-10 10:50:13 | [feed][n]working
2023-02-10 10:51:49 | [feed][n]syncing stream async: 1
2023-02-10 10:51:50 | [feed][n]syncing stream result: 1
2023-02-10 10:53:56 | [feed][n]syncing stream async: 1
2023-02-10 10:54:42 | [feed][n]syncing stream: timeout
2023-02-10 10:56:15 | [feed][n]syncing stream async: 1
2023-02-10 10:57:00 | [feed][n]syncing stream: timeout
2023-02-10 10:58:35 | [feed][n]syncing stream async: 1
2023-02-10 10:59:21 | [feed][n]syncing stream: timeout
2023-02-10 10:59:22 | [feed][n]disconnected
2023-02-10 10:59:22 | 23-02-10 10:59:41.291 [I][receiver_ac_sender.cpp:53] [feed][n]waiting 6 seconds
2023-02-10 10:59:26 | [i]PacketSenderConfiguration::on_periodic_refresh: refreshing configuration
2023-02-10 10:59:26 | [i]PacketSenderConfiguration::fetch_config(): Yoda configuration for this receiver is disabled
2023-02-10 10:59:28 | [feed][n]UKLL24@185.218.24.23:8099/UDP
2023-02-10 10:59:28 | [feed][n]connecting
2023-02-10 10:59:28 | 23-02-10 10:59:47.291 [I][receiver_ac_sender.cpp:36] Network thread connecting to 185.218.24.23:8099 for feed UKLL24
2023-02-10 10:59:28 | [feed][n]connected via UDP (fd 23)

        Comment

        • #5
          Its not the outbound..its the internal/feed/decoder connection

          The server is connecting fine. Hence 'online'. 'not receiving data' means, you aren't sending any aircraft to it.

          ​​​​​
          Posts not to be taken as official support representation - Just a helpful uploader who tinkers

          Comment

          • #6
            Originally posted by rpavlyuk View Post
            Full log file:
            Code:
            [main][i]FR24 Feeder/Decoder
[main][i]Version: 1.0.34-0/generic
[main][i]Built on Jan 10 2023 10:09:01 (decoder-v1.0.34-0-7c5301b.git/Linux/static_amd64)
[main][i]Running on: debian="11"
            Originally posted by rpavlyuk View Post
            Everything was fine with connectivity for almost three years until last 5 days.

            You are running fr24feed Ver 1.0.34-0 amd64 on Debian 11.
            When did you upgrade to this latest version?

            Comment

            • #7
              Originally posted by abcd567 View Post
              You are running fr24feed Ver 1.0.34-0 amd64 on Debian 11.
              When did you upgrade to this latest version?
              Good point! I'm running container from https://github.com/Thom-x/docker-fr2...aware-dump1090 and indeed the problems began when I updated to the latest version of the container. That last update is PiAware (and thus dump1090 that comes with it) version bump from v7.2 to v8.2 (https://github.com/Thom-x/docker-fr2...090/issues/111). Most likely, this is what is causing the problem: FR24feed is incompatible with that version of PiAware. I'm trying do downgrade the container version and will see what's going on. However, non of the users of that container have reported any problems as of yet.

              Comment

              • #8
                UPDATE: Downgrade of FR24Feed to 1.0.25-3 made the data to be received again:
                fr24_status_page_dwngrd.png
                Will probably have to file a bug report to container maintainer.

                Comment

                • #9
                  Originally posted by rpavlyuk View Post
                  UPDATE: Downgrade of FR24Feed to 1.0.25-3 made the data to be received again:
                  fr24_status_page_dwngrd.png

                  Will probably have to file a bug report to container maintainer.

                  Why use container? Why not not install directly on Debian 11 amd64?
                  I have installed dump1090, fr24feed, piaware, and Planefinder directly on Debian-11


                  fr24feed-debian-ubuntu-amd64

                  piaware-ubuntu-debian-amd64

                  piaware pre-built packages for debian amd64




                  FR24 on Debian-11 amd64.png



                  FR24-T-CYYZ158.png

                  Last edited by abcd567; 2023-02-11, 01:19.

                  Comment

                  • #10
                    Originally posted by abcd567 View Post
                    Why use container? Why not not install directly on Debian 11 amd64?
                    I have installed dump1090, fr24feed, piaware, and Planefinder directly on Debian-11
                    Because of two reasons:
                    1. My host os is RHEL 9 so I cannot run directly the software on it (Well, I can, but that's not that easy)
                    2. Container was easy plug-n-play solution. Plus, I didn't have to pollute the host OS will unnecessary packages and files.
                    Will see what to do next: help maintainer to fix the container or switch to Debian 11 KVM guest.

                    Comment

                    • #11
                      Yes, direct installation on RHEL is not easy.
                      Using container is very covenient and easy.

                      Three years ago (in 2020) I have successfully installed dump1090-fa manually on RHEL8.1 and Fedors 31

                      How to install dump1090-fa on FEDORA and RED HAT x86_64

                      I have recently written a acript which sutomatically installs (1) dump1090 and (2) FR24 feeder on Fedora, OpenSUSE and CentOS (all these OS are based on RHEL)

                      fr24feed-Fedora-OpenSUSE-CentOS-amd64


                      .
                      Last edited by abcd567; 2023-02-11, 14:49.
                      • Likes 1

                      Comment

                      • #12
                        Thanks for the instructions! I used those to install just FR24feed directly on my RHEL9 host and found out that feeder doesn't work there either.

                        Then I installed FR24feed on a nearby Fedora Linux machine and pointed it to the same container where dump1090-fa is running and where FR24feed didn't work well and... it worked! That's despite both machines have nearly identical settings and are behind the same firewall.

                        Conclusion: Latest version of FR24feed 1.0.34-0 doesn't work well on RHEL/CentOS 9 machines, even being inside Debian container.

                        I'm running a tiny container with just FR24feed in it on that Fedora machine. Thus, let's consider the issue solved. Well, at least for my case
                        • Likes 1

                        Comment

                        • #13
                          I had the same issue. A change to UTC-Timezone solved it in my case.

                          Comment

                          Previous template Next
                          Working...
                          X

                          We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

                          By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

                          I Agree