Announcement

Collapse
No announcement yet.

fr24feed issues

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • fr24feed issues

    Hello,
    My setup worked flawlessly for a few weeks until I noticed the data was not following. I attempted a reboot a few times, and everything returned to normal. Before restarting, I checked the status and grabbed the log from the most recent event. Please assist me with this.

    Code:
    pi@piaware:/etc $ sudo fr24feed-status
    FR24 Feeder/Decoder Process: running.
    FR24 Stats Timestamp: 2023-02-05 14:17:09.
    FR24 Link: failure ... failed!
    Receiver: down ... failed!
    FR24 MLAT: ok [UDP].
    FR24 MLAT AC seen: 0.

    ######################

    Code:
    2023-02-05 10:03:32 | [mlat][i]Pinging the server
    2023-02-05 10:03:32 | [mlat][i]Stats 54915755/333
    2023-02-05 10:03:34 | [feed][i]sent 3,19 AC
    2023-02-05 10:03:34 | 23-02-05 10:03:34.670 [D][:] sent 3 of 22 aircraft, 19 ignored, 0 outdated
    2023-02-05 10:03:40 | [reader][i]Connection terminated
    2023-02-05 10:03:45 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2023-02-05 10:03:45 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to tcp://localhost:30005
    2023-02-05 10:03:50 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2023-02-05 10:03:50 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to tcp://localhost:30005
    2023-02-05 10:03:52 | [mlat][i]Pinging the server
    2023-02-05 10:03:52 | [mlat][i]Stats 54915894/139
    2023-02-05 10:03:55 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2023-02-05 10:03:55 | [reader][e]Could not connect to tcp://localhost:30005
    2023-02-05 10:04:00 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2023-02-05 10:04:00 | [reader][e]Could not connect to tcp://localhost:30005
    2023-02-05 10:04:04 | [feed][n]ping 1
    2023-02-05 10:04:05 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2023-02-05 10:04:05 | [reader][e]Could not connect to tcp://localhost:30005
    2023-02-05 10:04:05 | [feed][n]syncing stream result: 1
    2023-02-05 10:04:08 | [get_local_ips][e]getifaddrs failed (Too many open files)
    2023-02-05 10:04:10 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2023-02-05 10:04:10 | [reader][e]Could not connect to tcp://localhost:30005
    2023-02-05 10:04:12 | [mlat][i]Pinging the server
    2023-02-05 10:04:12 | [mlat][i]Stats 54915894/0
    2023-02-05 10:04:15 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2023-02-05 10:04:15 | [reader][e]Could not connect to tcp://localhost:30005
    2023-02-05 10:04:20 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)

    ##########################
    Code:
    2023-02-05 13:56:11 | [mlat][i]Stats 54991983/0
    2023-02-05 13:56:14 | [mlat][i]No ADS-B time reference available (0/0)
    2023-02-05 13:56:15 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2023-02-05 13:56:15 | [reader][e]Could not connect to tcp://localhost:30005
    2023-02-05 13:56:20 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2023-02-05 13:56:20 | [reader][e]Could not connect to tcp://localhost:30005
    2023-02-05 13:56:24 | [mlat][i]No ADS-B time reference available (0/0)
    2023-02-05 13:56:25 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2023-02-05 13:56:25 | [reader][e]Could not connect to tcp://localhost:30005
    2023-02-05 13:56:30 | [reader][i]Connecting to DVBT-TCP-BEAST-RAW receiver via (tcp://localhost:30005)
    2023-02-05 13:56:30 | [reader][e]Could not connect to tcp://localhost:30005
    2023-02-05 13:56:31 | [mlat][i]Pinging the server
    2023-02-05 13:56:31 | [mlat][i]Stats 54991983/0

    Thank you for your help!
    Mario

    Last edited by marnow; 2023-02-05, 19:27.

  • #2
    After reading numerous posts about similar problems, I changed the fr24feed from "avr-tcp" to "beast-tcp." We will see if this helps.

    Comment


    • #3
      The change did not help....

      2023-02-06 21:52:20 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
      2023-02-06 21:52:20 | BeastBase::connectTcp(): Unable go create socket, error: Too many open files[reader][e]Could not connect to tcp://127.0.0.1:30005
      2023-02-06 21:52:22 | [time][i]Synchronizing time via NTP
      2023-02-06 21:52:22 | [time][e]Failed to synchronize time
      2023-02-06 21:52:25 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
      2023-02-06 21:52:25 | BeastBase::connectTcp(): Unable go create socket, error: Too many open files[reader][e]Could not connect to tcp://127.0.0.1:30005
      2023-02-06 21:52:30 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
      2023-02-06 21:52:30 | BeastBase::connectTcp(): Unable go create socket, error: Too many open files[reader][e]Could not connect to tcp://127.0.0.1:30005
      2023-02-06 21:52:35 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
      2023-02-06 21:52:35 | BeastBase::connectTcp(): Unable go create socket, error: Too many open files[reader][e]Could not connect to tcp://127.0.0.1:30005
      2023-02-06 21:52:40 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
      2023-02-06 21:52:40 | BeastBase::connectTcp(): Unable go create socket, error: Too many open files[reader][e]Could not connect to tcp://127.0.0.1:30005

      Comment


      • #4
        You have some networking issues to sort out First

        Socket errors and connection refused.

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

        Comment


        • #5
          No network issues; I am able to feed to flighaware and adbsexchange without a problem...only issue is with fr24.

          BeastBase::connectTcp(): Unable go create socket, error: Too many open files[reader][e]Could not connect to tcp://127.0.0.1:30005
          2023-02-06 21:52:30 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)

          Comment


          • #6
            So,. your feeder, can't currently connect to, or establish an open network port.

            Network.. issue. (And earlier status suggests is also not connecting to fr24 remotely)

            How many copies of the feeder are now running? Presumably you did the update and then restarted/flushed it.

            And also confirmed a functional feeder and the open ports on it are available

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

            Comment


            • #7
              ps aux | grep fr24feed

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

              Comment


              • #8
                Originally posted by Oblivian View Post
                ps aux | grep fr24feed

                ​​
                pi@piaware:~ $ ps aux | grep fr24feed
                fr24 8250 2.2 1.7 153904 16412 ? Ssl Feb06 23:03 /usr/bin/fr24feed

                One copy only.

                Comment


                • #9
                  2023-02-07 16:31:03 | [reader][i]Connecting to unknown receiver via (tcp://127.0.0.1:30005)
                  2023-02-07 16:31:03 | BeastBase::connectTcp(): Unable go connect, error: Connection refused[reader][e]Could not connect to tcp://127.0.0.1:30005

                  I observe these errors intermittently in the logs, after which the connection is established and the data flows. I agree that this is a networking issue, but since the issue is internal, between the receiver/dump and the feeder, I'm unsure what I can do to resolve it.

                  Comment


                  • #10
                    It looks like a bug introduced somewhere between 1.0.25 and 1.0.34. Whenever the TCP connection to the receiver is lost, fr24feed opens a new one, however it doesn't release the file descriptor associated with the socket related to the previous connection. lsof -c fr24feed shows plenty of these:

                    Code:
                    fr24feed 3057226 szpajder   26u     sock                0,7      0t0 76547965 protocol: TCP
                    fr24feed 3057226 szpajder   27u     sock                0,7      0t0 76547972 protocol: TCP
                    fr24feed 3057226 szpajder   28u     sock                0,7      0t0 76547975 protocol: TCP
                    fr24feed 3057226 szpajder   29u     sock                0,7      0t0 76547978 protocol: TCP
                    fr24feed 3057226 szpajder   30u     sock                0,7      0t0 76547981 protocol: TCP
                    fr24feed 3057226 szpajder   31u     sock                0,7      0t0 76554232 protocol: TCP
                    fr24feed 3057226 szpajder   32u     sock                0,7      0t0 76558251 protocol: TCP
                    fr24feed 3057226 szpajder   33u     sock                0,7      0t0 76558256 protocol: TCP
                    fr24feed 3057226 szpajder   34u     sock                0,7      0t0 76558273 protocol: TCP
                    fr24feed 3057226 szpajder   35u     sock                0,7      0t0 76558277 protocol: TCP
                    fr24feed 3057226 szpajder   36u     sock                0,7      0t0 76559362 protocol: TCP
                    fr24feed 3057226 szpajder   37u     sock                0,7      0t0 76559365 protocol: TCP
                    fr24feed 3057226 szpajder   38u     sock                0,7      0t0 76559369 protocol: TCP
                    fr24feed 3057226 szpajder   39u     sock                0,7      0t0 76559373 protocol: TCP
                    fr24feed 3057226 szpajder   40u     sock                0,7      0t0 76559376 protocol: TCP
                    fr24feed 3057226 szpajder   41u     sock                0,7      0t0 76559380 protocol: TCP
                    fr24feed 3057226 szpajder   42u     sock                0,7      0t0 76559383 protocol: TCP
                    fr24feed 3057226 szpajder   43u     sock                0,7      0t0 76559387 protocol: TCP
                    fr24feed 3057226 szpajder   44u     sock                0,7      0t0 76559404 protocol: TCP
                    fr24feed 3057226 szpajder   45u     sock                0,7      0t0 76559407 protocol: TCP
                    fr24feed 3057226 szpajder   46u     sock                0,7      0t0 76559410 protocol: TCP
                    fr24feed 3057226 szpajder   47u     sock                0,7      0t0 76559413 protocol: TCP
                    fr24feed 3057226 szpajder   48u     sock                0,7      0t0 76559417 protocol: TCP
                    fr24feed 3057226 szpajder   49u     sock                0,7      0t0 76559421 protocol: TCP
                    fr24feed 3057226 szpajder   50u     sock                0,7      0t0 76559424 protocol: TCP
                    fr24feed 3057226 szpajder   51u     sock                0,7      0t0 76559429 protocol: TCP
                    fr24feed 3057226 szpajder   52u     sock                0,7      0t0 76559436 protocol: TCP
                    Eventually the process runs out of file descriptors and is unable to open any new ones (hence the "Too many open files" error message). It won't reconnect to the receiver until it's restarted.

                    Comment


                    • #11
                      Originally posted by szpajder View Post
                      It looks like a bug introduced somewhere between 1.0.25 and 1.0.34. Whenever the TCP connection to the receiver is lost, fr24feed opens a new one, however it doesn't release the file descriptor associated with the socket related to the previous connection. lsof -c fr24feed shows plenty of these:

                      Code:
                      fr24feed 3057226 szpajder 26u sock 0,7 0t0 76547965 protocol: TCP
                      fr24feed 3057226 szpajder 27u sock 0,7 0t0 76547972 protocol: TCP
                      fr24feed 3057226 szpajder 28u sock 0,7 0t0 76547975 protocol: TCP
                      fr24feed 3057226 szpajder 29u sock 0,7 0t0 76547978 protocol: TCP
                      fr24feed 3057226 szpajder 30u sock 0,7 0t0 76547981 protocol: TCP
                      fr24feed 3057226 szpajder 31u sock 0,7 0t0 76554232 protocol: TCP
                      fr24feed 3057226 szpajder 32u sock 0,7 0t0 76558251 protocol: TCP
                      fr24feed 3057226 szpajder 33u sock 0,7 0t0 76558256 protocol: TCP
                      fr24feed 3057226 szpajder 34u sock 0,7 0t0 76558273 protocol: TCP
                      fr24feed 3057226 szpajder 35u sock 0,7 0t0 76558277 protocol: TCP
                      fr24feed 3057226 szpajder 36u sock 0,7 0t0 76559362 protocol: TCP
                      fr24feed 3057226 szpajder 37u sock 0,7 0t0 76559365 protocol: TCP
                      fr24feed 3057226 szpajder 38u sock 0,7 0t0 76559369 protocol: TCP
                      fr24feed 3057226 szpajder 39u sock 0,7 0t0 76559373 protocol: TCP
                      fr24feed 3057226 szpajder 40u sock 0,7 0t0 76559376 protocol: TCP
                      fr24feed 3057226 szpajder 41u sock 0,7 0t0 76559380 protocol: TCP
                      fr24feed 3057226 szpajder 42u sock 0,7 0t0 76559383 protocol: TCP
                      fr24feed 3057226 szpajder 43u sock 0,7 0t0 76559387 protocol: TCP
                      fr24feed 3057226 szpajder 44u sock 0,7 0t0 76559404 protocol: TCP
                      fr24feed 3057226 szpajder 45u sock 0,7 0t0 76559407 protocol: TCP
                      fr24feed 3057226 szpajder 46u sock 0,7 0t0 76559410 protocol: TCP
                      fr24feed 3057226 szpajder 47u sock 0,7 0t0 76559413 protocol: TCP
                      fr24feed 3057226 szpajder 48u sock 0,7 0t0 76559417 protocol: TCP
                      fr24feed 3057226 szpajder 49u sock 0,7 0t0 76559421 protocol: TCP
                      fr24feed 3057226 szpajder 50u sock 0,7 0t0 76559424 protocol: TCP
                      fr24feed 3057226 szpajder 51u sock 0,7 0t0 76559429 protocol: TCP
                      fr24feed 3057226 szpajder 52u sock 0,7 0t0 76559436 protocol: TCP
                      Eventually the process runs out of file descriptors and is unable to open any new ones (hence the "Too many open files" error message). It won't reconnect to the receiver until it's restarted.
                      It appears to be this way, so I ended up with a cron job that restarts the feeder every 24 hours....not the best solution, but it works for now.

                      Comment

                      Working...
                      X