No announcement yet.

usb_claim_interface_error -6

  • Filter
  • Time
  • Show
Clear All
new posts

  • usb_claim_interface_error -6


    I got FR24 installed on a fresh Debian x86 now by just downloading that package:
    And install by dpkg -i fr24feed_1.0.18-5_i386.deb

    But now I get that error, can you please help me why?
    I have that USB receiver:
    Is that one ok?

    root@FR24:~# fr24feed --status
    2019-10-15 16:50:45 | [main][i]FR24 Feeder/Decoder
    2019-10-15 16:50:45 | [main][i]Version: 1.0.18-5/generic
    2019-10-15 16:50:45 | [main][i]Built on Mar  2 2016 20:06:10 (devel-d11ca48.git/Linux/i686)
    2019-10-15 16:50:45 | [main][i]Copyright 2012-2016 Flightradar24 AB
    2019-10-15 16:50:45 | [main][i]
    2019-10-15 16:50:45 | [main][i]DNS mode: LIBC
    2019-10-15 16:50:45 | [main][i]Automatic updates are DISABLED
    2019-10-15 16:50:45 | ERROR
    2019-10-15 16:50:45 | [main][i]Reader thread started
    2019-10-15 16:50:45 | [main][i]Socket server started
    2019-10-15 16:50:45 | [time][i]Synchronizing time via NTP
    2019-10-15 16:50:45 | [bs][i]Initializing server
    2019-10-15 16:50:45 | [bs][i]Starting server on
    2019-10-15 16:50:45 | [master][i]Starting processing thread
    2019-10-15 16:50:45 | [httpd][i]Server started, listening on
    2019-10-15 16:50:45 | [reader][i]Initializing reader
    2019-10-15 16:50:45 | [reader][i]Connecting to Beast receiver via (exe:///usr/lib/fr24/dump1090  --raw)
    2019-10-15 16:50:45 | [reader][i]Connected to the receiver, configuring
    2019-10-15 16:50:45 | [reader][i]Configured, processing messages
    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
    Last edited by mensa; 2019-10-15, 15:00.

  • #2
    Wrong command, use:


    Stop writing in multiple threads, it's really annoying.
    Last edited by wiedehopf; 2019-10-15, 15:00.


    • #3
      This thread does not belong x64 installation it is x86! That is the reason for an own thread.

      It is the correct command, because it is version 1.0.18-5. So "fr24feed --status" is the correct command.

      Can please anyone help and tell why that error occurs?


      • #4
        --status is not recognized

        It's just starting up the application, but the service is already running the application.

        pgrep -a dump1090
        pgrep -a fr24feed

        With those commands you will see what is already running and using the dongle.

        If you want to run fr24feed on the console for testing, stop the service before:
        systemctl stop fr24feed


        • #5
          Thank you.
          Can I see my own receiver also on the flightradar24 website?

          Or can I also see my tracked planes on a map on the webserver of my linux machine?
          Currently I can access only a very basic web interface on port 8754.


          • #6
            If you have lighttpd running, it should be at /dump1090-fa

            I'd recommend my improved interface:

            It even offers some advice on how to configure it with nginx.
            But using lighttpd is easier, for that it will be automatically enabled.


            • #7

              now I installed the i386 architecture on a Debian x64 and had that "usb_claim_interface error -6" again, although no other process was using the USB dongle.
              I saw in an email notification of an answer from you, that you wrote I should do type the following:

              echo -e 'blacklist rtl2832\nblacklist dvb_usb_rtl28xxu\nblacklist rtl8192cu\nblacklist rtl8xxxu\n' > /etc/modprobe.d/blacklist-rtl-sdr2.conf
              Now it works. But why? Why do I have to blacklist anything to get it to work?


              • #8
                The kernel has drivers for the device to use it as an DVB-T receiver to watch digital terrestially broadcast television.

                Those drivers use the device and it can't be used by dump1090.
                Blacklisting those drivers solves that problem.

                Dump1090 does not use those drivers, but an alternative driver to access the device.