-
Notifications
You must be signed in to change notification settings - Fork 55
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
Comments
Can you try to disable mlat ? |
How do I do that? I tried changing the following options to both be "no" without luck.
|
Do you mount the config file or are you using the environment var ? |
I had the same issue and got it working with setting the /etc/fr24feed.ini like this: receiver="beast-tcp" 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. |
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. |
Strange I have something like this and it works, maybe you have more options:
|
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. |
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
The text was updated successfully, but these errors were encountered: