Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update causes device busy #23

Closed
AustinShalit opened this issue May 11, 2020 · 7 comments
Closed

Update causes device busy #23

AustinShalit opened this issue May 11, 2020 · 7 comments
Labels

Comments

@AustinShalit
Copy link

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:https:///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
@Thom-x
Copy link
Owner

Thom-x commented May 11, 2020

Can you try to disable mlat ?
We already had this issue #14

@AustinShalit
Copy link
Author

AustinShalit commented May 12, 2020

How do I do that? I tried changing the following options to both be "no" without luck.

mlat="yes"
mlat-without-gps="yes"

@Thom-x
Copy link
Owner

Thom-x commented Jul 1, 2020

Do you mount the config file or are you using the environment var ?
I recommend you to use the env var, so no need to bind mount any file.
With env you only need to change your credentials (not mlat or anything else).

@glowfishDE
Copy link

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.

@glowfishDE
Copy link

Do you mount the config file or are you using the environment var ?
I recommend you to use the env var, so no need to bind mount any file.
With env you only need to change your credentials (not mlat or anything else).

I tried that before but it seems the export variables for fr24feed.ini were not recognized. So i had to use the mounted file instead :(

The export variables for piaware.conf were working howsoever.

@Thom-x
Copy link
Owner

Thom-x commented Jul 1, 2020

Strange I have something like this and it works, maybe you have more options:

    environment:
      - "HTML_SITE_LAT=47.xxxxxx"
      - "HTML_SITE_LON=-1.xxxxxx"
      - "HTML_SITE_NAME=HOME"
      - "FR24FEED_FR24KEY=xxxxxx"
      - "PIAWARE_FEEDER_DASH_ID=xxxxxxx"

@stale
Copy link

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.

@stale stale bot added the wontfix label Dec 18, 2020
@stale stale bot closed this as completed Dec 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants