Announcement

Collapse
No announcement yet.

Receiver is online but not sending any data

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

  • Receiver is online but not sending any data

    Receiver is online but not sending any data (no aircraft in coverage or problem with antenna) - have found out this error today. Used to work just fine.

    I reconfigured the settings and updated the system but no luck so far. I'm using DVT-B USB stick (WINGONEER Digitale USB 2.0 DVB-T SDR+DAB+FM RTL2832U+R820T2).

    Checking the status:
    Code:
    ● fr24feed.service - Flightradar24 Decoder & Feeder
       Loaded: loaded (/etc/systemd/system/fr24feed.service; enabled; vendor preset: enabled)
       Active: active (running) since Sun 2019-01-06 20:03:30 UTC; 2min 40s ago
      Process: 276 ExecStartPre=/usr/lib/fr24/create_missing_directories.sh (code=exited, status=0/SUCCESS)
      Process: 264 ExecStartPre=/usr/lib/fr24/unregister_kernel_modules.sh (code=exited, status=0/SUCCESS)
      Process: 223 ExecStartPre=/usr/lib/fr24/install_dump1090.sh (code=exited, status=0/SUCCESS)
     Main PID: 289 (fr24feed)
       CGroup: /system.slice/fr24feed.service
               └─289 /usr/bin/fr24feed
    
    Jan 06 20:03:28 radar systemd[1]: Starting Flightradar24 Decoder & Feeder...
    Jan 06 20:03:30 radar systemd[1]: Started Flightradar24 Decoder & Feeder.
    Running the sudo fr24feeed:
    Code:
    2019-01-06 20:12:07 | [main][i]FR24 Feeder/Decoder
    2019-01-06 20:12:07 | [main][i]Version: 1.0.23-8/generic
    2019-01-06 20:12:07 | [main][i]Built on Oct 16 2018 08:10:47 (HEAD-2d57e58.git/Linux/static_armel)
    2019-01-06 20:12:07 | [main][i]Running on: raspbian9
    2019-01-06 20:12:07 | [main][i]Local IP(s): 192.168.123.235
    2019-01-06 20:12:07 | [main][i]Copyright 2012-2018 Flightradar24 AB
    2019-01-06 20:12:07 | [main][i]DNS mode: PING
    2019-01-06 20:12:07 | [main][i]Automatic updates are ENABLED
    2019-01-06 20:12:07 | ERROR: rmmod: ERROR: Module dvb_usb_rtl28xxu is not currently loaded
    2019-01-06 20:12:07 | [main][i]Reader thread started
    2019-01-06 20:12:07 | [time][i]Synchronizing time via NTP
    2019-01-06 20:12:07 | [reader][i]Initializing reader
    2019-01-06 20:12:07 | [master][i]Starting processing thread
    2019-01-06 20:12:07 | [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability  --raw)
    2019-01-06 20:12:07 | [[httpd][e]bind function failed, errno: 98
    2019-01-06 20:12:07 | reader][i]Connected to the receiver, configuring
    2019-01-06 20:12:07 | [httpd][d]Master thread terminated
    2019-01-06 20:12:07 | [reader][i]Configured, processing messages
    Sun Jan  6 20:12:07 2019 UTC  dump1090-mutability v1.14 starting up.
    Found 1 device(s):
    0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
    usb_claim_interface error -6
    Error opening the RTLSDR device: Device or resource busy
    2019-01-06 20:12:07 | [reader][i]Connection terminated
    2019-01-06 20:12:07 | [main][i]Terminating child process 1744 with SIGTERM
    Tried to google:
    ERROR: rmmod: ERROR: Module dvb_usb_rtl28xxu is not currently loaded - found sth with blacklisting but did not work
    usb_claim_interface error -6 - didn't anything with -6

  • #2
    Please post the output of

    cat /etc/fr24feed.ini

    Don't post the fr24key though that should remain private.

    If a log path is set please have a look into the log if you know how

    If you want to manually start the feeder for testing you need to stop the service first like this:
    systemctl stop fr24feed
    (otherwise the dongle is already used by the service, it can't be used twice)
    Last edited by wiedehopf; 2019-01-06, 22:06.

    Comment


    • #3
      fr24feed.ini
      Code:
      receiver="dvbt"
      fr24key="myKey"
      path="/usr/lib/fr24/dump1090"
      bs="no"
      raw="no"
      logmode="2"
      logpath="/var/log/fr24feed"
      mlat="no"
      mlat-without-gps="no"
      tail /var/log/fr24feed.log
      Code:
      2018-01-20 11:20:46 | [feed][c]GND: YES
      2018-01-20 11:20:46 | [feed][c]NonADSB: YES
      2018-01-20 11:20:46 | [feed][c]Timestamps: optional
      2018-01-20 11:20:46 | [feed][c]Max range AIR: 350.0nm
      2018-01-20 11:20:46 | [feed][c]Max range GND: 100.0nm
      2018-01-20 11:20:46 | [feed][i]defined 5 servers
      2018-01-20 11:20:46 | [feed][n]LKTB50@83.130.10.85:8099/UDP
      2018-01-20 11:20:46 | [feed][n]connecting
      2018-01-20 11:21:06 | [feed][n]connected via TCP (fd -1)
      2018-01-20 11:21:06 | [feed][n]working

      Comment


      • #4
        I have the same issue. How do we get the Pi to recognise the receiver?

        [main][i]FR24 Feeder/Decoder
        [main][i]Version: 1.0.23-8/generic
        [main][i]Built on Oct 11 2018 18:27:28 (HEAD-3c696a7.git/Linux/static_armel)
        [main][i]Running on: pi24-raspbian9
        [main][i]Local IP(s): 192.168.0.7
        [main][i]Copyright 2012-2018 Flightradar24 AB
        [main][i] fr24 web link
        [main][i]DNS mode: PING
        [main][i]Automatic updates are ENABLED
        ERROR: rmmod: ERROR: Module dvb_usb_rtl28xxu is not currently loaded
        [[main][i]Reader thread started
        [main][i]Socket server started
        [main][i]MLAT data feed started
        [master][i]Starting processing thread
        [reader][i]Initializing reader
        [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw --mlat)
        httpd][e]bind function failed, errno: 98
        [httpd][d]Master thread terminated
        [reader][i]Connected to the receiver, configuring
        [reader][i]Configured, processing messages
        [bs][i]Initializing server
        [bs][i]Starting server on 0.0.0.0:30003
        [mlat][i]Waiting for MLAT configuration
        [bs][e]Could not bind socket to *:30003, errno=98
        Sat Jan 19 02:41:20 2019 UTC dump1090-mutability v1.14 starting up.
        Found 1 device(s):
        0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
        usb_claim_interface error -6
        Error opening the RTLSDR device: Device or resource busy
        [reader][i]Connection terminated
        [main][i]Terminating child process 2447 with SIGTERM
        [time][i]Synchronizing time via NTP
        [reader][i]Connecting to DVBT receiver via (exe:///usr/bin/dump1090-mutability --raw --mlat)
        [reader][i]Connected to the receiver, configuring
        [reader][i]Configured, processing messages

        Comment


        • #5
          Restart for a start. The auto upgrade is enabled and likely didn't shut everything down as it is meant to
          Therefore you are possibly starting 2 copies and RTL set hadn't restarted

          If not it would point to something else the updater had broken

          But we would see a lot more offline if that was the case

          So its likely more isolated to your common set ups and need more individual tests

          Sent from my EML-L09 using Tapatalk
          Posts not to be taken as official support representation - Just a helpful uploader who tinkers

          Comment


          • #6
            Thanks Oblivian. My Raspberry Pi sd card died during the week and I put an image on a new sd card and reactivated everything this morning. Have had an issue with not seeing anything for a while. very frustrating.

            Comment


            • #7
              So can you then fill us all in with the details...

              Config/stick setup settings
              Reboot performed yes/no?

              Remember don't run anything related to 'fr24feed' after rebooting. Only ever look at the web status page or run the correct status command. Anything else will just re-run and break.

              And it is not clear if what you pasted is a log, or re running it which will give that output if you don't stop it first per the command given by wiedehopf

              Sent from my EML-L09 using Tapatalk
              Posts not to be taken as official support representation - Just a helpful uploader who tinkers

              Comment


              • #8
                And I suspect it's the latter. Or you wouldn't see

                [bs][e]Could not bind socket to *:30003, errno=98

                That means already open.

                Sent from my EML-L09 using Tapatalk
                Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                Comment


                • #9
                  Thank again. i may be tech savvy with a lot of things but Linux and the Raspberry Pi are not them.

                  Rapsberry Pi with the FR24 image loaded and activated
                  Tuner - Unsure of the Brand as I purchased it on eBay: USB2.0 Digital DVB-T SDR+DAB+FM HDTV TV Tuner Receiver Stick RTL2832U + R820T
                  Have just rebooted the Pi and logged in via the web portal 192.168.0.7:8754
                  Screen Shot 01-19-19 at 02.25 PM.jpg

                  Antenna is located on the roof, but is just the mag base antenna that came with the tuner.
                  Last edited by PeterWelly; 2019-01-19, 04:26. Reason: adding info

                  Comment


                  • #10
                    Id be surprised if there was 214 users in that immediate area. So someone has maybe reactivated wayyyyy too many times.

                    The image and activation should really only be used once and manual setup every consecutive time after to be sure it uses the same key/id. The default antennas are insensitive to adsb without being trimmed btw. One user has it on a tin roof and only gets out to ~60nm

                    So are you sure there are enough in that range? Reactivating a new unit will need 3-4 or so contacts to go true live if that restriction is still in place.

                    Click the settings page. Enable the log.

                    Restart pi

                    Run the command supplied to view the active log after it's been run for a a few mins.

                    https://forum.flightradar24.com/showthread.php?p=113499

                    Sent from my EML-L09 using Tapatalk
                    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                    Comment


                    • #11
                      Ok, thanks yet again.

                      Have done that and will let it run for a while. I did have previous radar number that was 208. Have only activated twice. I am in the Northern Suburbs of Brisbane so there may be quite a few radars.

                      If I SSH into the Pi with Putty, and run the command tail /var/log/fr24feed.log, I get the error tail: cannot open '/var/log.fr24feed.log' for reading: No such file or directory. Would this be due to it need to run for a while before it creates a log file?

                      Sorry to be a pain.

                      Comment


                      • #12
                        I am 12NM from Brisbane Airport and directly under the flight path, so it shouldn't take long to register some hits hopefully.

                        Comment


                        • #13
                          Typed rather than copy paste?

                          You have log. not log/
                          Posts not to be taken as official support representation - Just a helpful uploader who tinkers

                          Comment


                          • #14
                            Corrected that, still same result.

                            Will leave it running for an hour or so and see if there is a log created.

                            Comment


                            • #15
                              No it won't start after a time - It should be immediate.

                              It logs as soon as it starts up if enabled properly

                              Double check the 'logging' setting saved (you to need to adjust, save, save, reboot) and hasn't got a different path

                              It's under the webpage settings

                              fr24log.JPG

                              But he also didn't have it quite right if it matches above:

                              tail /var/log/fr24feed/fr24feed.log

                              Will show the end

                              cat /var/log/fr24feed/fr24feed.log

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

                              Comment

                              Working...
                              X