Results 1 to 3 of 3

Thread: dump1090-mutability: usb_claim_interface error -6

  1. #1
    Passenger
    Join Date
    Jun 2018
    Posts
    2

    dump1090-mutability: usb_claim_interface error -6

    Hey there!

    So I just set up my RPi with the script
    Code:
    sudo bash -c "$(wget -O - http //repo feed flightradar24 com/install_fr24_rpi.sh)"
    I just downloaded the script and ran every command separately because everything at once wouldn't work for me.

    However, I now reached the point where at least FR24 Link works.
    When issuing the following command I get this output:
    Code:
    sudo fr24feed-status
    
    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2018-06-26 17:25:12.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: <...>.
    [ ok ] FR24 Tracked AC:.
    [FAIL] Receiver: down ... failed!
    [FAIL] FR24 MLAT: not running ... failed!
    After doing some research I found it probably has to do something with this:
    Code:
    dump1090-mutability
    
    Tue Jun 26 19:27:39 2018 CEST  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
    Nevertheless, I cannot fix this issue. I tried to blacklist the device in various files, restated my pi and tried some stuff with cmake, but
    - blacklist has no effect on the error
    - cmake needs that strange CMakeLists.txt which I cannot find for any fr24 folder.


    Does anyone know how to get my pi running?
    Thank you!



    EDIT/SOLUTION:
    Running htop I saw that a second instance of /usr/bin/dump1050-mutability was running on my RPi. I tried to kill it (sudo kill <pid> or F9 in sudo htop) and restart fr24 afterwards (sudo service fr24feed restart) and it successfully connected.
    In order to survive a reboot I threw dump1050-mutability out of my autostart (sudo update-rc.d dump1090-mutability disable). When issuing sudo reboot and fr24feed-status, it successfully connects:
    Code:
    fr24feed-status
    [ ok ] FR24 Feeder/Decoder Process: running.
    [ ok ] FR24 Stats Timestamp: 2018-07-06 09:32:13.
    [ ok ] FR24 Link: connected [UDP].
    [ ok ] FR24 Radar: <...>.
    [ ok ] FR24 Tracked AC:.
    [ ok ] Receiver: connected (3 MSGS/0 SYNC).
    [ ok ] FR24 MLAT: ok [UDP].
    [ ok ] FR24 MLAT AC seen: 0.
    Last edited by physanus; 2018-07-06 at 09:37. Reason: adding solution, removing radar id

  2. #2
    Captain abcd567's Avatar
    Join Date
    Sep 2013
    Location
    Toronto CYYZ
    Posts
    2,169
    Quote Originally Posted by physanus View Post
    Code:
    dump1090-mutability
    
    Tue Jun 26 19:27:39 2018 CEST  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

    You are starting dump1090-mutability, while it's another instance is already running, and is using DVB-T.
    The second instance of dump1090-mutability then gives error message "Device or resource busy".


    First stop all instances of fr24feed and dump1090-mutability:
    Code:
    sudo systemctl stop dump1090-mutability
    sudo systemctl stop fr24feed
    Now run dump1090-mutability
    Code:
    dump1090-mutability
    
    Thu Jun 28 13:58:22 2018 EDT  dump1090-mutability v1.14 starting up.
    Found 1 device(s):
    0: Realtek, RTL2832U, SN: 00000000 (currently selected)
    Found Rafael Micro R820T tuner
    Max available gain is: 49.60 dB
    Setting gain to: 49.60 dB
    Exact sample rate is: 2000000.052982 Hz
    Gain reported by device: 49.60 dB
    *8dc0636499093c17300421c4a106;
    CRC: 000000
    RSSI: -35.9 dBFS
    Time: 18155.00us (phase: 0)
    DF 17: ADS-B message.
      Capability     : 5 (Level 2+, airborne)
      ICAO Address   : c06364
      Extended Squitter  Type: 19
      Extended Squitter  Sub : 1
      Extended Squitter  Name: Airborne Velocity
        EW status         : Valid
        EW velocity       : 315
        NS status         : Valid
        NS velocity       : 184
        Vertical status   : Valid
        Vertical rate src : 1
        Vertical rate     : 0
    ^C
    Thu Jun 28 13:58:25 2018 EDT  Normal exit.
    To normalize:
    Code:
    sudo reboot
    #After reboot, wait 5 minutes, then check status
    Code:
    fr24feed-status
    Last edited by abcd567; 2018-06-28 at 18:05.

  3. #3
    Passenger
    Join Date
    Jun 2018
    Posts
    2
    Okay, apparently a second instance of dump1090-mutability was running on my machine.
    I will edit my first post for the solution, thank you for your help!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •