Announcement

Collapse
No announcement yet.

Unable to connect to receiver?

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

  • Unable to connect to receiver?

    I recently renewed my FR24 "server". Both, old and new, are Linux based (Lubuntu). I installed latest fr24feed and I'm using the same DVB-T receiver from my previous configuration. I was reading FAQ and troubleshooting info and I think the problem is that fr24feed cannot connect to my DVB-T receiver. Any ideas how to proceed?

    I have checked that no dump1090 or fr24feed processes are running before starting fr24feed.


    Here are my info, fr24feed.ini:
    Code:
    receiver="dvbt"
    fr24key="xxxxxxxxxxxxxxxxx"
    path="/usr/lib/fr24/dump1090"
    bs="no"
    raw="yes"
    logmode="2"
    mlat="no"
    mlat-without-gps="no"

    fr24feed status:
    Code:
    fr24feed.service - LSB: Flightradar24 Decoder & Feeder
       Loaded: loaded (/etc/init.d/fr24feed; bad; vendor preset: enabled)
       Active: active (running) since to 2016-07-07 10:38:39 EEST; 51s ago
         Docs: man:systemd-sysv-generator(8)
      Process: 18846 ExecStart=/etc/init.d/fr24feed start (code=exited, status=0/SUCCESS)
       CGroup: /system.slice/fr24feed.service
               +-18873 /usr/bin/fr24feed -- --monitor-file=/dev/shm/fr24feed.txt --write-pid=/var/run/fr24feed.pid --quiet --log
    
    jul 07 10:38:39 TheTower systemd[1]: Starting LSB: Flightradar24 Decoder & Feeder...
    jul 07 10:38:39 TheTower fr24feed[18846]:  * Starting FR24 feeder fr24feed
    jul 07 10:38:39 TheTower fr24feed[18846]:    ...done.
    jul 07 10:38:39 TheTower systemd[1]: Started LSB: Flightradar24 Decoder & Feeder.
    fr24feed.log:
    Code:
    2016-07-07 10:38:39 | [main][i]FR24 Feeder/Decoder
    2016-07-07 10:38:39 | [main][i]Version: 1.0.18-5/generic
    2016-07-07 10:38:39 | [main][i]Built on Mar  2 2016 20:06:10 (devel-d11ca48.git/Linux/i686)
    2016-07-07 10:38:39 | [main][i]Copyright 2012-2016 Flightradar24 AB
    2016-07-07 10:38:39 | [main][i]<link_removed>
    2016-07-07 10:38:39 | [main][i]DNS mode: LIBC
    2016-07-07 10:38:39 | [main][i]Automatic updates are DISABLED
    2016-07-07 10:38:39 | ERROR
    2016-07-07 10:38:39 | [httpd][i]Server started, listening on 0.0.0.0:8754
    2016-07-07 10:38:39 | [main][i]Reader thread started
    2016-07-07 10:38:39 | [time][i]Synchronizing time via NTP
    2016-07-07 10:38:39 | [reader][i]Initializing reader
    2016-07-07 10:38:46 | [time][i]Time synchronized correctly, offset +0.0010 seconds
    2016-07-07 10:38:46 | [main][i]Feed Network client started
    2016-07-07 10:38:46 | [main][i]RAW data server started
    2016-07-07 10:38:46 | [raw][i]Initializing server
    2016-07-07 10:38:46 | [raw][i]Starting server on 0.0.0.0:30002
    2016-07-07 10:38:46 | [feed][i]Downloading configuration
    2016-07-07 10:38:47 | [feed][c]Interval: 5s
    2016-07-07 10:38:47 | [feed][c]Latitude: 60.4700
    2016-07-07 10:38:47 | [feed][c]Longitude: 26.9200
    2016-07-07 10:38:47 | [feed][c]GND: YES
    2016-07-07 10:38:47 | [feed][c]NonADSB: YES
    2016-07-07 10:38:47 | [feed][c]Timestamps: optional
    2016-07-07 10:38:47 | [feed][c]Max range AIR: 350.0nm
    2016-07-07 10:38:47 | [feed][c]Max range GND: 100.0nm
    2016-07-07 10:38:47 | [feed][i]defined 5 servers
    2016-07-07 10:38:47 | [feed][n]EFUT2@83.140.21.112:28099/UDP
    2016-07-07 10:38:47 | [feed][n]connecting
    2016-07-07 10:38:47 | [stats][i]Stats thread started
    2016-07-07 10:38:47 | [feed][n]connected via UDP (fd 10)
    2016-07-07 10:38:47 | [feed][n]working
    2016-07-07 10:38:50 | [reader][i]Connecting to Beast receiver via (exe:///usr/lib/fr24/dump1090  --raw)
    2016-07-07 10:38:50 | [reader][i]Connected to the receiver, configuring
    2016-07-07 10:38:50 | [reader][i]Configured, processing messages
    2016-07-07 10:38:50 | [reader][i]Connection terminated
    2016-07-07 10:38:50 | [main][i]Terminating child process 18908 with SIGETERM
    2016-07-07 10:38:56 | [reader][i]Connecting to Beast receiver via (exe:///usr/lib/fr24/dump1090  --raw)
    2016-07-07 10:38:56 | [reader][i]Connected to the receiver, configuring
    2016-07-07 10:38:56 | [reader][i]Configured, processing messages
    2016-07-07 10:38:56 | [reader][i]Connection terminated
    ...
    There is "ERROR" in one row. What fails? Any ideas what to test, change configuration, test DVB-T stick?

  • #2
    First error is normal.

    You didn't install dump1090 separate?

    You can configure using the webpage in that state, turn off the output feeds and configure as AVRTCP on 30002 instead to try
    Posts not to be taken as official support representation - Just a helpful uploader who tinkers

    Comment


    • #3
      No, I shouldn't have dump1090 installed separately, fr24feed is using it from "/usr/lib/fr24/dump1090". Changing mode to AVRTCP won't work either, it's not getting data from localhost:30002.

      Code:
      2016-07-07 15:15:07 | [reader][i]Connecting to Beast receiver via (avr-tcp://localhost:30002)
      2016-07-07 15:15:07 | [reader][e]Could not connect to avr-tcp://localhost:30002
      I just tested with my old conputer and it seems to be working with same .ini file.

      Comment


      • #4
        OK, now I think I know whats going on. I tried to shut down fr24feed and check dumb1090 output with result:
        Code:
        Found 1 device(s):
        0: Realtek, RTL2838UHIDIR, SN: 00000001 (currently selected)
        
        Kernel driver is active, or device is claimed by second instance of librtlsdr.
        In the first case, please either detach or blacklist the kernel module
        (dvb_usb_rtl28xxu), or enable automatic detaching at compile time.
        
        usb_claim_interface error -6
        Error opening the RTLSDR device: Device or resource busy
        So... does this mean that some kernel modile is using my device and fr24feed is unable to access it? I'm a bit noob with Linux... so how can I "detach or blacklist" that module?

        Comment


        • #5
          OK, I will now answer myself if someone else is having same problem.

          I tried to remove module with: sudo rmmod dvb_usb_rtl28xxu. That resulted in error that module is in use. When I unplugged DVB-T receiver, I was able to unload module. But when I plugged it in again, it loaded the module and same problem again.

          So, I found almost similar problem with Google and that suggested that moduel has to be blacklisted. I created file /etc/modprobe.d/no-rtl.conf with following:
          Code:
          blacklist dvb_usb_rtl28xxu
          After that, I checked the log file and everything seems to be in order.

          Comment


          • #6
            The fix for that is also in my guide thread but so rare these days to have suggested

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

            Comment


            • #7
              Oh... so there is. I somehow missed that. Thanks

              Comment

              Working...
              X