Announcement

Collapse
No announcement yet.

Failed to start Flightradar24 Decoder & Feeder.

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

    Failed to start Flightradar24 Decoder & Feeder.

    Code:
    pi@raspberrypi:/var/log/fr24feed $ sudo service fr24feed status
● fr24feed.service - Flightradar24 Decoder & Feeder
Loaded: loaded (/etc/systemd/system/fr24feed.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Sat 2022-03-12 19:22:16 GMT; 3min 43s ago
Process: 1468 ExecStartPre=/usr/lib/fr24/install_dump1090.sh (code=exited, status=0/SUCCESS)
Process: 1473 ExecStartPre=/usr/lib/fr24/unregister_kernel_modules.sh (code=exited, status=0/SUCCESS)
Process: 1477 ExecStartPre=/usr/lib/fr24/create_missing_directories.sh (code=exited, status=0/SUCCESS)
Process: 1480 ExecStart=/usr/bin/fr24feed (code=exited, status=0/SUCCESS)
Main PID: 1480 (code=exited, status=0/SUCCESS)

Mar 12 19:22:16 raspberrypi systemd[1]: fr24feed.service: Service RestartSec=100ms expired, scheduling restart.
Mar 12 19:22:16 raspberrypi systemd[1]: fr24feed.service: Scheduled restart job, restart counter is at 5.
Mar 12 19:22:16 raspberrypi systemd[1]: Stopped Flightradar24 Decoder & Feeder.
Mar 12 19:22:16 raspberrypi systemd[1]: fr24feed.service: Start request repeated too quickly.
Mar 12 19:22:16 raspberrypi systemd[1]: fr24feed.service: Failed with result 'start-limit-hit'.
Mar 12 19:22:16 raspberrypi systemd[1]: Failed to start Flightradar24 Decoder & Feeder.
    Code:
    Mar 12 19:15:58 raspberrypi systemd[1]: fr24gui-init.service: Succeeded.
Mar 12 19:16:10 raspberrypi systemd[1]: fr24feed.service: Control process exited, code=killed, status=15/TERM
Mar 12 19:16:10 raspberrypi systemd[1]: fr24feed.service: Succeeded.
Mar 12 19:16:10 raspberrypi systemd[1]: fr24feed.service: Succeeded.
Mar 12 19:16:10 raspberrypi systemd[1]: fr24feed.service: Service RestartSec=100ms expired, scheduling restart.
Mar 12 19:16:10 raspberrypi systemd[1]: fr24feed.service: Scheduled restart job, restart counter is at 1.
Mar 12 19:16:11 raspberrypi systemd[1]: fr24feed.service: Succeeded.
Mar 12 19:16:11 raspberrypi systemd[1]: fr24feed.service: Service RestartSec=100ms expired, scheduling restart.
Mar 12 19:16:11 raspberrypi systemd[1]: fr24feed.service: Scheduled restart job, restart counter is at 2.
Mar 12 19:16:11 raspberrypi systemd[1]: fr24feed.service: Succeeded.
Mar 12 19:16:11 raspberrypi systemd[1]: fr24feed.service: Service RestartSec=100ms expired, scheduling restart.
Mar 12 19:16:11 raspberrypi systemd[1]: fr24feed.service: Scheduled restart job, restart counter is at 3.
Mar 12 19:16:12 raspberrypi systemd[1]: fr24feed.service: Succeeded.
Mar 12 19:16:12 raspberrypi systemd[1]: fr24feed.service: Service RestartSec=100ms expired, scheduling restart.
Mar 12 19:16:12 raspberrypi systemd[1]: fr24feed.service: Scheduled restart job, restart counter is at 4.
cat: Mar 12 19:16:12 raspberrypi systemd[1]: fr24feed.service: Start request repeated too quickly.
Mar 12 19:16:12 raspberrypi systemd[1]: fr24feed.service: Failed with result 'start-limit-hit'.

    Code:
    pi@raspberrypi:/var/log $ sudo rtl_test -t
Found 1 device(s):
0: Realtek, RTL2832U, SN: 00001000

Using device 0: Generic RTL2832U
Detached kernel driver
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
[R82XX] PLL not locked!
Sampling at 2048000 S/s.
No E4000 tuner found, aborting.
Reattached kernel driver
    Code:
    pi@raspberrypi:/var/log $ cat /etc/fr24feed.ini
receiver="dvbt-mr"
path="/usr/lib/fr24/dump1090"
bs="yes"
raw="yes"
logmode="2"
logpath="/var/log/fr24feed"
mlat="yes"
mlat-without-gps="yes"
    /var/log/fr24feed is empty


    Any ideas?



    Tags: None
  • #2
    In file /etc/fr24feed.ini , change:

    receiver="dvbt-mr"

    To

    receiver="dvbt"

    Save file. Then

    sudo systemctl restart fr24feed

    After few minutes:

    fr24feed-status.

    Comment

    • #3
      I change to mr in last try, with dvbt was the same result.
      Piaware works without problem.

      Comment

      • #4
        What are output of following commands? Their output will confirm which decoder is installed on your RPi.

        apt-cache policy dump1090-mutability

        apt-cache policy dump1090-fa
        Last edited by abcd567; 2022-03-12, 21:05.

        Comment

        • #5
          If piaware is going. The answer is obvious

          You're trying to attach to the USB directly with fr24. PIaware already has it

          It needs to be configured for network data, not direct to usb.
          Posts not to be taken as official support representation - Just a helpful uploader who tinkers

          Comment

          • #6
            Originally posted by Oblivian View Post
            If piaware is going. The answer is obvious

            You're trying to attach to the USB directly with fr24. PIaware already has it

            It needs to be configured for network data, not direct to usb.
            I don't get it, what I should do?

            Comment

            • #7
              We don't know how you set it up, or what guide followed. But if you used the install script after setting up piaware it detects piaware, it configures.

              If you read something that says change it to dvbt to install fr24. or it has been, Then that probably did it.

              Option 2, post 1. Changing to network data source.

              https://forum.flightradar24.com/foru...-a-brief-guide
              Posts not to be taken as official support representation - Just a helpful uploader who tinkers

              Comment

              • #8
                Originally posted by Oblivian View Post
                We don't know how you set it up, or what guide followed. But if you used the install script after setting up piaware it detects piaware, it configures.

                If you read something that says change it to dvbt to install fr24. or it has been, Then that probably did it.

                Option 2, post 1. Changing to network data source.

                https://forum.flightradar24.com/foru...-a-brief-guide
                I upload latest pi24 image. If I upload piaware all works "out of the box", with pi24 I have above problems.

                Comment

                • #9
                  When?.cause new users also blocked

                  Newly created volunteer feeds blocked until further notice - Flightradar24 Forum
                  https://forum.flightradar24.com/forum/radar-forums/flightradar24-feeding-data-to-flightradar24/212121-newly-created-volunteer-feeds-blocked-until-further-notice
                  Hi guys, Im sure some of you saw this mornings carnival involving the AN-225. Of course this was spoofed into the network. We have identified the code involved and we are mitigating it. Unfortunately all new volunteer feeds will be disabled until further notice until we can solve this. I will keep this post updated with


                  But if you have piaware working. Install fr24 and DONT chose dvbt.
                  Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                  Comment

                  • #10
                    Originally posted by sirwiz View Post
                    [

                    Code:
                    pi@raspberrypi:/var/log $ cat /etc/fr24feed.ini
receiver="dvbt-mr"
path="/usr/lib/fr24/dump1090"
bs="yes"
raw="yes"
logmode="2"
logpath="/var/log/fr24feed"
mlat="yes"
mlat-without-gps="yes"

                    (1) In file /etc/fr24feed.ini
                    Replace these two lines:
                    receiver="dvbt-mr"
                    path="/usr/lib/fr24/dump1090"

                    By these two lines:
                    receiver="beast-tcp"
                    host="127.0.0.1:30005"

                    ​​​​​​Save file, then restsrt fr24feed
                    sudo systemctl restart fr24feed


                    (2) You did not post output of following diagnostic commands which will reveal if you have any decoder installed, and which one:

                    apt-cache policy dump1090-mutability

                    apt-cache policy dump1090-fa


                    .

                    Comment

                    • #11
                      Yes I do not post output, because i try many configurations, for now I have piaware with working Flightaware and Radarbox feeds, only FR24 won't start, but like mention Oblivian, I think its due ban new feeds registration https://forum.flightradar24.com/foru...further-notice
                      Last edited by sirwiz; 2022-03-13, 09:25.

                      Comment

                      • #12
                        Sorry, if you dont tell which decoder you have installed, then it is not possible to diagnose the problem and help you.

                        Comment

                        • #13
                          Code:
                          pi@piaware:~ $ apt-cache policy dump1090-mutability
dump1090-mutability:
Installed: (none)
Candidate: 1.15~20180310.4a16df3+dfsg-8
Version table:
1.15~20180310.4a16df3+dfsg-8 500
500 http://flightaware.com/mirror/raspbian/raspbian bullseye/main armhf Packages
pi@piaware:~ $ apt-cache policy dump1090-fa
dump1090-fa:
Installed: 7.2
Candidate: 7.2
Version table:
*** 7.2 500
500 http://flightaware.com/adsb/piaware/files/packages bullseye/piaware armhf Packages
100 /var/lib/dpkg/status
pi@piaware:~ $
                          As I use now piaware I have dump1090-fa.

                          Code:
                          cat /etc/fr24feed.ini
receiver="avr-tcp"
host="127.0.0.1:30002"
bs="yes"
raw="yes"
logmode="2"
logpath="/var/log/fr24feed"
mlat="yes"
mlat-without-gps="yes"
                          Radarbox feed works, Flightaware works, fr24 the same error. But like I wrote above I think that this is reason: https://forum.flightradar24.com/foru...further-notice

                          Comment

                          • #14
                            Thanks for posting details.

                            ​​Your file fr24feed.ini does NOT contain following line:
                            fr24key=xxxxxxxxxxxxxxx

                            If you have not removed it yourself for privacy reasons while posting in forum, then this missing key is the reason for for failure.

                            A further improvement is to change "yes" to "no" in following two lines to avoid conflict of ports between fr24feed and dump1090-fa:

                            bs="yes"
                            raw="yes"


                            .

                            Comment

                            • #15
                              Originally posted by sirwiz View Post
                              As I use now piaware I have dump1090-fa.
                              User generally use word "piaware" for two entirely different things. This creates confusion.

                              (1) Piaware SD card image (consisting of raspberrypios+dump1090-fa+piaware datafeeder). In this case decoder is dump1090-fa

                              (2) Piaware data feeder software (which user himself installs on RaspberryPi OS, or DietPi OS, or Ubuntu for rpi OS). In this csase the decoder is NOT NECESSATILY dump1090-fa. The user is free to install any of available decoders such as dump1090-mutability, readsb, dump1090-fa, modesdeco2 etc etc.

                              .
                              Last edited by abcd567; 2022-03-14, 11:30.
                              • Likes 1

                              Comment

                              Previous 1 2 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