Announcement

Collapse
No announcement yet.

How to set up a feeder using 64-bit Ubuntu Linux on Intel platform

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

  • Thanks very much to OP and the other contributors to this very helpful post. I'm very comfortable with Windows, not so much with Linux.
    I got a Nooelec RTL-SDR v5.
    I bought on Amazon a Mini Windows10Pro Celeron-based machine (N4020) with 4GB DDR4 and a 128gb ssd. I spent some time trying to set up a feed from Windows, but decided would be easier to do linux - Kind of had that in mind when I bought the pc, so before doing anything, I backed it up, and shrunk the Windows partition to make room for Ubuntu install -
    Now, the machine is dual boot Windows/Ubuntu

    I pretty much followed all the steps in first post - and with a little fiddling, got it to work/sort of. Only until I connected to Internet. Turns out, the issue is the default driver for the Nooelec, which requires a slightly different blacklist file to prevent default driver. By the time I figured that out, I had other issues with things I had tried that weren't problem, so I started over - reinstalled ubuntu, and went through all the steps again - and got everything to work.

    For anyone using Nooelec, they have a Install manual for ubuntu, and the key is to get: blacklist dvb_usb_rtl128xxu in a .conf file in /etc/modprobe.d (their documentation puts it in file blacklist-dvb.conf,)

    This setup is drawing under 5 watts of power (headless) and I installed xrdp pkg so can use Windows rdp client.

    (I also discovered my high-E glass attenuates signal a lot, but if I put antenna outside on window huge difference. I've got in coming through open window and going to try a RG6 flat jumper cable I found on Amazon so I can close window and keep antenna outside... )



    Last edited by RichH1; 2023-08-16, 23:21.

    Comment


    • RichH1
      Congratulations.
      Glad to know you succeeded in installing Ubuntu AND Flightradar24 feeder on Celeron-based machine (N4020) with 4GB DDR4 and a 128gb ssd.

      Can you please give some more details?

      (1) Which version of Ubuntu (Ubuntu20 / Ubuntu22 / Ubuntu 23) ?
      (2) Which decoder (dump1090-mutability / dump1090-fa / readsb ?
      (3) Did you also install other feeders like Flightaware, Planefinder, Radarbox24, Adsbexchange etc?


      .

      Comment


      • Originally posted by abcd567 View Post
        RichH1
        Congratulations.
        ...
        (1) Which version of Ubuntu (Ubuntu20 / Ubuntu22 / Ubuntu 23) ?
        (2) Which decoder (dump1090-mutability / dump1090-fa / readsb ?
        (3) Did you also install other feeders like Flightaware, Planefinder, Radarbox24, Adsbexchange etc?


        .
        I used the current ubuntuLTS downloaded just a few days ago - 22.04.3 LTS - (and chose option to install as little as possible, I forget what the setup calls it; also installed not connected to Internet, and without the SDR in USB. I did allow proprietary 3rd-party hw drivers.)

        I'm using dump1090-mutability - basically, the only thing I needed to change in the instructions from the original post in this thread was the name needed for blacklisting the default driver for the radio receiver (in my case Nooelec)

        After everything was working for FR24 feed, I did install another feeder that you mention above and it installed/worked basically as per their instructions for ubuntu&dump1090.

        On my first ubuntu install, it took me a while to realize the issue I was facing was the wrong driver for the stick. In the process of figuring that out, I tried a lot of different things, including the FA version of 1090 feeder (which would have worked I think), and I had things working with the 1090FA, but I made some kind of mistake (installed lighttpd webserver) and got to the point lost proper internet routing (even Firefox) - and decided to just start over wiping out the ubuntu partition - and it didn't take long to reinstall everything.

        I find the responsiveness of the xDesktop & the browser, and remote desktop surprisingly fast for the 2019-release Celeron box and way better deal for me compared to current pricing of the Pi's. Came with dual video, dual band wifi, gigabit ethernet, bluetooth 5.0.. (I guess I'm too used to WinDoze) and it's drawing under 5 watts while feeding, using 5ghz wifi, powering the Nooelec which is very warm. Is the power draw similar to what a Pi4 setup would be? (And, 1 more thing - I think after everything is done, should delete the pi .img, .img.gz ? I think these 2 files are around 3.5gb. Apologies if this has already been mentioned, I noob here.)

        edit to add - before I mess things up again, since everything is working - I purchased a Timetec 512gb M.2SSD ($20usd!) to replace the 128gb that came with the box - and I intend to keep that 128gb just as it is for a while as a backup. I installed Gparted & Clonezilla/Live USB and did a disk-to-disk clone to the larger drive (using a Eluteng M.2-USB3). It surprised me how little time that took, almost thought it couldn't have done the clone - but after putting the 512gb in, both Windows & Ubuntu boot just fine and I'm feeding....
        Last edited by RichH1; 2023-08-17, 06:31.

        Comment


        • Hi All,

          Noob here, trying to get this working. I'm attempting to use Ubuntu-22.04 running under https://github.com/microsoft/WSL on a computer running Windows 10, also using https://github.com/dorssel/usbipd-win for USB sharing. I'm using a Rafael Micro R820T2, which was used with FR24 when they supported Windows.

          I followed the steps in the first post as exactly as possible. I only experienced one definite error, which was the following:

          Code:
          *****@*****:/home# cp ./fr24/etc/logrotate.d/fr24feed /etc/logrotate.d/fr24feed
          cp: cannot stat './fr24/etc/logrotate.d/fr24feed': No such file or directory
          The directory ./fr24/etc/logrotate.d/fr24feed does not exist in the img. I looked around and didn't see it anywhere else. Has anyone experienced this problem? If so, what is the work-around?

          Code:
          *****@*****:/home$ sudo systemctl status fr24feed.service
          ● fr24feed.service - Flightradar24 Decoder & Feeder
               Loaded: loaded (/etc/systemd/system/fr24feed.service; enabled; vendor preset: enabled)
               Active: activating (start-pre) since Sat 2024-01-20 22:12:20 PST; 1min 0s ago
              Process: 10096 ExecStartPre=/usr/lib/fr24/unregister_kernel_modules.sh (code=exited, status=0/SUCCESS)
              Process: 10100 ExecStartPre=/usr/lib/fr24/create_missing_directories.sh (code=exited, status=1/FAILURE)
          Cntrl PID: 10103 (fr24feed)
                Tasks: 11 (limit: 8887)
               Memory: 10.6M
               CGroup: /system.slice/fr24feed.service
                       ├─10103 /usr/bin/fr24feed --validate-config --config-file=/etc/fr24feed.ini
                       └─10119 /usr/bin/dump1090-mutability --gain -10 --write-json /run/dump1090-mutability/ --lat 49.2541 --lon>
          
          Jan 20 22:12:21 kaveri fr24feed[10119]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
          Jan 20 22:12:21 kaveri fr24feed[10119]: Allocating 4 zero-copy buffers
          Jan 20 22:12:22 kaveri fr24feed[10103]: [reader][w]Setting new UTC offset: 0!
          Jan 20 22:12:24 kaveri fr24feed[10103]: [time][i]Time synchronized correctly, offset -14.0609 seconds
          Jan 20 22:12:24 kaveri fr24feed[10103]: [main][i]Feed Network client started
          Jan 20 22:12:24 kaveri fr24feed[10103]: [main][i]RAW data server started
          Jan 20 22:12:24 kaveri fr24feed[10103]: [feed][i]Downloading configuration
          Jan 20 22:12:24 kaveri fr24feed[10103]: [raw][i]Initializing server
          Jan 20 22:12:24 kaveri fr24feed[10103]: [raw][i]Starting server on 0.0.0.0:30002
          Jan 20 22:12:25 kaveri fr24feed[10103]: [feed][i]Failed on start, Sleeping 120 seconds​


          The script which exited with failure is trying to create four directories. All four were created, so no idea why error status was returned.

          Code:
          *****@*****:/var/log$ sudo systemctl status nginx.service
          ● nginx.service - A high performance web server and a reverse proxy server
          Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
          Active: active (running) since Sat 2024-01-20 14:30:40 PST; 7h ago
          Docs: man:nginx(8)
          Main PID: 739 (nginx)
          Tasks: 5 (limit: 8887)
          Memory: 4.7M
          CGroup: /system.slice/nginx.service
          ├─739 "nginx: master process /usr/sbin/nginx -g daemon on; master_process on;"
          ├─740 "nginx: worker process" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ">
          ├─741 "nginx: worker process" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ">
          ├─742 "nginx: worker process" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ">
          └─743 "nginx: worker process" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" "" ">
          
          Jan 20 14:30:40 kaveri systemd[1]: Starting A high performance web server and a reverse proxy server...
          Jan 20 14:30:40 kaveri systemd[1]: Started A high performance web server and a reverse proxy server.​
          If anyone has suggestions to get this working, I would greatly appreciate it.

          Comment


          • Latest and Easier Method:



            fr24feed-debian-ubuntu-amd64-i386



            .
            Last edited by abcd567; 2024-01-21, 13:37.

            Comment


            • Originally posted by abcd567 View Post
              Latest and Easier Method:

              fr24feed-debian-ubuntu-amd64-i386
              Thank you for your reply!

              I deleted the distro and created a new one.

              I'm following the procedure in README.md.

              The default /etc/fr24feed.ini contains the following:

              Code:
              bs=yes
              raw=yes
              mlat="yes"
              mlat-without-gps="yes"
              Is there any documentation​ about the content?

              Code:
              receiver="avr-tcp"
              host="127.0.0.1:30002"
              fr24key=""
              
              bs="no"
              raw="no"
              logmode="1"
              logpath="REDACTED"
              mlat="yes"
              mlat-without-gps="yes"
              I had to redact the log path because it was causing an error with vbulletin.

              My receiver is an 820T2 & SDR. Is "avr-tcp"​ the correct type?

              Is it preferable to enable mlat?

              Thank you.

              Comment


              • I made some progress, but having a few problems.

                dump1090 is working and I can see aircraft, so that's a start.

                However, fr24feed is notworking.

                Here is the output from sudo systemctl status fr24feed:

                Code:
                ● fr24feed.service - Flightradar24 Decoder & Feeder
                Loaded: loaded (/etc/systemd/system/fr24feed.service; disabled; vendor preset: enabled)
                Active: active (running) since Sun 2024-01-21 16:17:23 PST; 3s ago
                Process: 2592 ExecStartPre=/usr/lib/fr24/install_dump1090.sh (code=exited, status=0/SUCCESS)
                Process: 2596 ExecStartPre=/usr/lib/fr24/unregister_kernel_modules.sh (code=exited, status=0/SUCCESS)
                Process: 2600 ExecStartPre=/usr/lib/fr24/create_missing_directories.sh (code=exited, status=1/FAILURE)
                Process: 2603 ExecStartPre=/usr/bin/fr24feed --validate-config --config-file=/etc/fr24feed.ini (code=exited, status>
                Main PID: 2604 (fr24feed)
                Tasks: 14 (limit: 8887)
                Memory: 10.5M
                CGroup: /system.slice/fr24feed.service
                └─2604 /usr/bin/fr24feed
                
                Jan 21 16:17:23 kaveri fr24feed[2604]: [reader][i]Connecting to AVR-TCP receiver via (avr-tcp://127.0.0.1:30002)
                Jan 21 16:17:23 kaveri fr24feed[2604]: [reader][i]Connected to the receiver, configuring
                Jan 21 16:17:23 kaveri fr24feed[2604]: [reader][i]Configured, processing messages
                Jan 21 16:17:23 kaveri fr24feed[2604]: [time][i]Synchronizing time via NTP
                Jan 21 16:17:24 kaveri fr24feed[2604]: [time][i]Time synchronized correctly, offset -4.767 seconds
                Jan 21 16:17:24 kaveri fr24feed[2604]: [main][i]Feed Network client started
                Jan 21 16:17:24 kaveri fr24feed[2604]: [feed][i]Downloading configuration
                Jan 21 16:17:24 kaveri fr24feed[2604]: [feed][d]Fetching configuration
                Jan 21 16:17:24 kaveri fr24feed[2604]: [feed][e]Result: failure, message: Not found, check your key!
                Jan 21 16:17:24 kaveri fr24feed[2604]: [feed][i]Failed on start, Sleeping 30 seconds
                ​I have a sharing key, which I got from sudo fr24feed --signup.

                Since I'm getting the above error, I tried the signup wizard again. Here is the result:

                Code:
                Verifying sharing key...[W] Fall back to HTTP for error: SSL connect error
                Got no response or empty response from the server :(
                Does a port need to be opened up? I did start with a clean distro, but it's the same distro that I used before.

                I have another question about dump1090 regarding some messages in the log file.

                Code:
                Sun Jan 21 10:32:06 2024 PST EB_SOURCE EB_VERSION starting up.
                Using sample converter: UC8, integer/table path
                Found 1 device(s):
                0: unable to read device details
                usb_open error -3
                Please fix the device permissions, e.g. by installing the udev rules file rtl-sdr.rules
                Error opening the RTLSDR device: Permission denied
                Sun Jan 21 10:33:26 2024 PST EB_SOURCE EB_VERSION starting up.
                Using sample converter: UC8, integer/table path
                Found 1 device(s):
                0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
                Found Rafael Micro R820T tuner
                Max available gain is: 49.60 dB
                Setting gain to: 49.60 dB
                Gain reported by device: 49.60 dB
                Allocating 15 zero-copy buffers


                ​Is the error at the beginning of the log caused by the wrong device type? If so, what device type should I use for the R820T2?

                Thank you for the help.

                Comment


                • Originally posted by bimmerdriver View Post
                  Thank you for your reply!

                  I deleted the distro and created a new one.

                  I'm following the procedure in README.md.

                  The default /etc/fr24feed.ini contains the following:

                  Code:
                  bs=yes
                  raw=yes
                  mlat="yes"
                  mlat-without-gps="yes"
                  Is there any documentation​ about the content?

                  Code:
                  receiver="avr-tcp"
                  host="127.0.0.1:30002"
                  fr24key=""
                  
                  bs="no"
                  raw="no"
                  logmode="1"
                  logpath="REDACTED"
                  mlat="yes"
                  mlat-without-gps="yes"
                  I had to redact the log path because it was causing an error with vbulletin.

                  My receiver is an 820T2 & SDR. Is "avr-tcp"​ the correct type?

                  Is it preferable to enable mlat?


                  Thanks for pointing out. That paragraph about default config was many years old, and I forgot to update it.

                  I have now updated it as follows:


                  (1) CONFIGURATION OF FR24FEED
                  The configuration file can be edited by following command;

                  sudo nano /etc/fr24feed.ini

                  Shown below are contents of file /etc/fr24feed.ini, when following 2 conditions are met:

                  (1) A decoder like dump1090-mutability or dump1090-fa is installed and running on the Computer.

                  (2) during --signup OR --reconfigure, you have said yes to following question:

                  Would you like to use autoconfig (*yes*/no)

                  receiver="avr-tcp"
                  host="127.0.0.1:30002"
                  fr24key="xxxxxxxxxxx"
                  logmode="1"

                  bs="no"
                  raw="no"
                  mlat="yes"
                  mlat-without-gps="yes"
                  Last edited by abcd567; 2024-01-22, 05:27.

                  Comment


                  • I tried rebooting the computer to see if it would help to resolve the problem with fr24feed. Unfortunately, it made no difference. I also found that dump1090 didn't automatically restart, so I had to give it a kick by running sudo dpkg-reconfigure dump1090-mutability.

                    Here is the log from fr24feed:

                    Code:
                    *****@kaveri:/home/*****$ sudo systemctl status fr24feed
                    ● fr24feed.service - Flightradar24 Decoder & Feeder
                    Loaded: loaded (/etc/systemd/system/fr24feed.service; disabled; vendor preset: enabled)
                    Active: active (running) since Mon 2024-01-22 13:26:35 PST; 2s ago
                    Process: 1206 ExecStartPre=/usr/lib/fr24/install_dump1090.sh (code=exited, status=0/SUCCESS)
                    Process: 1210 ExecStartPre=/usr/lib/fr24/unregister_kernel_modules.sh (code=exited, status=0/SUCCESS)
                    Process: 1214 ExecStartPre=/usr/lib/fr24/create_missing_directories.sh (code=exited, status=1/FAILURE)
                    Process: 1217 ExecStartPre=/usr/bin/fr24feed --validate-config --config-file=/etc/fr24feed.ini (code=exited, status>
                    Main PID: 1218 (fr24feed)
                    Tasks: 14 (limit: 8887)
                    Memory: 10.5M
                    CGroup: /system.slice/fr24feed.service
                    └─1218 /usr/bin/fr24feed
                    
                    Jan 22 13:26:35 kaveri fr24feed[1218]: [reader][i]Connected to the receiver, configuring
                    Jan 22 13:26:35 kaveri fr24feed[1218]: [reader][i]Configured, processing messages
                    Jan 22 13:26:35 kaveri fr24feed[1218]: [time][i]Synchronizing time via NTP
                    Jan 22 13:26:35 kaveri fr24feed[1218]: [time][i]Time synchronized correctly, offset -7.534 seconds
                    Jan 22 13:26:35 kaveri fr24feed[1218]: [feed][i]Downloading configuration
                    Jan 22 13:26:35 kaveri fr24feed[1218]: [main][i]Feed Network client started
                    Jan 22 13:26:35 kaveri fr24feed[1218]: [feed][d]Fetching configuration
                    Jan 22 13:26:36 kaveri fr24feed[1218]: [feed][e]Result: failure, message: Not found, check your key!
                    Jan 22 13:26:36 kaveri fr24feed[1218]: [feed][i]Failed on start, Sleeping 30 seconds
                    Jan 22 13:26:36 kaveri fr24feed[1218]: [reader][i]Timestamp source changed from UNKNOWN to SYSTEM-VALIDATED
                    ...
                    Jan 22 13:44:40 kaveri fr24feed[1218]: [feed][e]Result: failure, message: Not found, check your key!
                    Jan 22 13:44:40 kaveri fr24feed[1218]: [feed][i]Failed on start, Sleeping 270 seconds
                    Jan 22 13:46:36 kaveri fr24feed[1218]: [time][i]Synchronizing time via NTP
                    Jan 22 13:46:36 kaveri fr24feed[1218]: [time][e]Failed to synchronize time
                    Jan 22 13:46:36 kaveri fr24feed[1218]: [reader][i]Timestamp source changed from SYSTEM-VALIDATED to SYSTEM-UNCERTAIN
                    Jan 22 13:46:42 kaveri fr24feed[1218]: [time][i]Synchronizing time via NTP
                    Jan 22 13:46:43 kaveri fr24feed[1218]: [time][e]Time synchronized, offset -0.242 seconds, drift +0.363 seconds/minute
                    Jan 22 13:49:11 kaveri fr24feed[1218]: [feed][d]Fetching configuration
                    Jan 22 13:49:11 kaveri fr24feed[1218]: [feed][e]Result: failure, message: Not found, check your key!
                    Jan 22 13:49:11 kaveri fr24feed[1218]: [feed][i]Failed on start, Sleeping 300 seconds​
                    I'm getting the same problem as I reported previously when I run sudo fr24feed --signup.

                    Code:
                    Verifying sharing key...[W] Fall back to HTTP for error: SSL connect error
                    Got no response or empty response from the server :(


                    This is strange, because it initially worked and I got a sharing key.

                    More info:

                    Code:
                    ​*****@kaveri:/var/log$ fr24feed-status
                    * FR24 Feeder/Decoder Process: running
                    * FR24 Stats Timestamp: 2024-01-22 21:20:06
                    * FR24 Link: unknown
                    * Receiver: connected (102 MSGS/0 SYNC)
                    * FR24 MLAT: not running
                    DUMP1090 is tracking flights, using http://127.0.0.1/dump1090/gmap.html.

                    lightpd is showing a placeholder page http://127.0.0.1/.​ Is that normal?

                    Comment


                    • Check your file /etc/fr24feed.ini

                      Code:
                      sudo nano /etc/fr24feed.ini
                      Does it have a line starting with fr24key?
                      If yes, check if its value is correct. You can find the key from your Flightradar24 Stats page. You have to Login to your account on that page

                      The world’s most popular flight tracker. Track planes in real-time on our flight tracker map and get up-to-date flight status & airport information.


                      Cotents of file /etc/fr24feed.ini
                      Code:
                      receiver="avr-tcp"
                      host="127.0.0.1:30002"
                      fr24key="xxxxxxxxxxx"
                      logmode="1"
                      
                      bs="no"
                      raw="no"
                      mlat="yes"
                      mlat-without-gps="yes"
                      ​

                      Comment


                      • Originally posted by abcd567 View Post
                        Check your file /etc/fr24feed.ini

                        Code:
                        sudo nano /etc/fr24feed.ini
                        Does it have a line starting with fr24key?
                        If yes, check if its value is correct. You can find the key from your Flightradar24 Stats page. You have to Login to your account on that page

                        The world’s most popular flight tracker. Track planes in real-time on our flight tracker map and get up-to-date flight status & airport information.


                        Cotents of file /etc/fr24feed.ini
                        Code:
                        receiver="avr-tcp"
                        host="127.0.0.1:30002"
                        fr24key="xxxxxxxxxxx"
                        logmode="1"
                        
                        bs="no"
                        raw="no"
                        mlat="yes"
                        mlat-without-gps="yes"
                        ​
                        Thank you for your reply. I was previously using the fr24feed.ini file that I pasted above. I deleted the entire file contents and pasted in the contents from your post with my fr24key. As I said previously, I was able to use the script to get a key and I also received an email containing it. I copied and pasted the key from the email into the file. I then stopped and restarted the service.

                        Here is the result:

                        Code:
                        *****@kaveri:/home/*****$ sudo systemctl status fr24feed.service
                        ● fr24feed.service - Flightradar24 Decoder & Feeder
                        Loaded: loaded (/etc/systemd/system/fr24feed.service; disabled; vendor preset: enabled)
                        Active: active (running) since Mon 2024-01-22 17:11:54 PST; 2s ago
                        Process: 2835 ExecStartPre=/usr/lib/fr24/install_dump1090.sh (code=exited, status=0/SUCCESS)
                        Process: 2839 ExecStartPre=/usr/lib/fr24/unregister_kernel_modules.sh (code=exited, status=0/SUCCESS)
                        Process: 2843 ExecStartPre=/usr/lib/fr24/create_missing_directories.sh (code=exited, status=1/FAILURE)
                        Process: 2846 ExecStartPre=/usr/bin/fr24feed --validate-config --config-file=/etc/fr24feed.ini (code=exited, status>
                        Main PID: 2847 (fr24feed)
                        Tasks: 15 (limit: 8887)
                        Memory: 12.5M
                        CGroup: /system.slice/fr24feed.service
                        └─2847 /usr/bin/fr24feed
                        
                        Jan 22 17:11:54 kaveri fr24feed[2847]: [mlat][i]Waiting for MLAT configuration
                        Jan 22 17:11:54 kaveri fr24feed[2847]: [reader][i]Connected to the receiver, configuring
                        Jan 22 17:11:54 kaveri fr24feed[2847]: [reader][i]Configured, processing messages
                        Jan 22 17:11:55 kaveri fr24feed[2847]: [time][i]Synchronizing time via NTP
                        Jan 22 17:11:56 kaveri fr24feed[2847]: [time][i]Time synchronized correctly, offset -5.937 seconds
                        Jan 22 17:11:56 kaveri fr24feed[2847]: [main][i]Feed Network client started
                        Jan 22 17:11:56 kaveri fr24feed[2847]: [feed][i]Downloading configuration
                        Jan 22 17:11:56 kaveri fr24feed[2847]: [feed][d]Fetching configuration
                        Jan 22 17:11:56 kaveri fr24feed[2847]: [feed][e]Result: failure, message: Not found, check your key!
                        Jan 22 17:11:56 kaveri fr24feed[2847]: [feed][i]Failed on start, Sleeping 30 seconds


                        dump1090 is running and I can see aircraft on the map.

                        Code:
                        *****@kaveri:/etc/default$ sudo systemctl status dump1090-mutability
                        ● dump1090-mutability.service - LSB: dump1090 daemon (mutability variant)
                        Loaded: loaded (/etc/init.d/dump1090-mutability; generated)
                        Active: active (running) since Mon 2024-01-22 16:30:18 PST; 51min ago
                        Docs: man:systemd-sysv-generator(8)
                        Process: 2403 ExecStart=/etc/init.d/dump1090-mutability start (code=exited, status=0/SUCCESS)
                        Tasks: 3 (limit: 8887)
                        Memory: 5.6M
                        CGroup: /system.slice/dump1090-mutability.service
                        └─2413 /usr/bin/dump1090-mutability --net --ppm 0 --fix --lat 49.2541 --lon -122.8080 --max-range 100 --ne>
                        
                        Jan 22 16:30:17 kaveri systemd[1]: Starting LSB: dump1090 daemon (mutability variant)...
                        Jan 22 16:30:18 kaveri systemd[1]: Started LSB: dump1090 daemon (mutability variant).
                        Let me know if I should post any other information.

                        Thanks again.​

                        Comment


                        • I tried to signup again, without using the key that I got before. It failed with the same error. I think whatever is causing this is preventing fr24feed from contacting feed.flightradar24.com. I can ping, nslookup and traceroute feed.flightradar24.com, but for some reason, the software isn't able to verify the key. I wish it provided a more descriptive error message.

                          UPDATE: It occurred to me that when I signed up, I was following the procedure in the first post. That is the only thing I can think of that changed from when the signup was working to now with it not working.
                          Last edited by bimmerdriver; 2024-01-23, 17:08.

                          Comment


                          • I forgot to update this thread. I was finally able to get it working by completely uninstalling all of the software and reinstalling it. It's currently working with dump1090-mutability and fr24feed. I will create a separate thread explaining how to set up a feeder using Windows Subsystem for Linux.

                            Comment

                            Working...
                            X