Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Update causes device busy

See original GitHub issue

Specifications

I just attempted an upgrade from fa493ee73552d4ecdea6085aa46dac454a6468f837176aa1fe80fe894cb4e07c to latest (e6a44d31fdd73dd71fb9c433ddf9dc7e70a69eeb2009a0acd5f33a53a414a917). I did this by stoping the old container, pulling the latest image, and then trying to start the container back up using the new image. This leads to no aircraft being tracked and the following messages repeated in the logs.

Expected Behavior

Image is able to connect to USB stick.

Actual Behavior

2020-05-11 09:17:51 | [reader][i]Connecting to Beast receiver via (exe:///usr/lib/fr24/dump1090 --net --write-json /usr/lib/fr24/public_html/data --raw --mlat)
2020-05-11 09:17:51 | [reader][i]Connected to the receiver, configuring
2020-05-11 09:17:51 | [reader][i]Configured, processing messages
Mon May 11 09:17:51 2020 UTC  dump1090-fa v3.8.1 starting up.
rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 00001197)
usb_claim_interface error -6
rtlsdr: error opening the RTLSDR device: Device or resource busy
2020-05-11 09:17:51 | [reader][i]Connection terminated
2020-05-11 09:17:51 | [main][i]Terminating child process 347 with SIGETERM

Issue Analytics

State:
Created 3 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

glowfishDEcommented, Jul 1, 2020

I had the same issue and got it working with setting the /etc/fr24feed.ini like this:

receiver=“beast-tcp”
host=“127.0.0.1:30005” fr24key=“myfeederID”
bs=“yes”
raw=“yes”
logmode=“1”
procargs=“–net --write-json /usr/lib/fr24/public_html/data”

Before i had the receiver set to “dvbt”. When i changed it to “beast-tcp” (or avr-tcp) it was suddenly working without the mentioned error.

0reactions

stale[bot]commented, Dec 18, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.