-
Notifications
You must be signed in to change notification settings - Fork 250
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
panic on startup #280
Comments
Yep, you'll need to be sure the spectrum server is running and reachable before rtlamr starts. If the spectrum server is in another container, I don't think you'll be able to reach it at a localhost anyway. |
Everything is in 1 container. I submitted this bug report as I figured you'd want to trap the panic and do some sleep-retry logic for a better user experience. |
I agree, it would be a quality of life improvement. I'll have a look at it. |
I'm not using a container and I'm hitting the same error under Raspberry Pi OS Bookworm. Do you think it is related? |
Forget about this, my problem is unrelated. Calling 127.0.0.1 fails, but not using the "external" IP. This is a network configuration problem on my Pi. |
Made a custom docker container with rtl-sdr, rtlamr, and rtlamr-collect. When it starts up, I think there's a race condition that I'm working out where something starts before something else resulting in this panic.
The text was updated successfully, but these errors were encountered: