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

panic on startup #280

Open
utdrmac opened this issue Aug 3, 2023 · 5 comments
Open

panic on startup #280

utdrmac opened this issue Aug 3, 2023 · 5 comments

Comments

@utdrmac
Copy link

utdrmac commented Aug 3, 2023

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.

00:59:39.771085 main.go:90: Error connecting to spectrum server: dial tcp 127.0.0.1:1234: connect: connection refused
rcvr.Connect
main.(*Receiver).NewReceiver
	/go/pkg/mod/github.com/bemasher/rtlamr@v0.9.3/main.go:90
main.main
	/go/pkg/mod/github.com/bemasher/rtlamr@v0.9.3/main.go:313
runtime.main
	/usr/local/go/src/runtime/proc.go:250
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:1598
@bemasher
Copy link
Owner

bemasher commented Aug 3, 2023

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.

@utdrmac
Copy link
Author

utdrmac commented Aug 3, 2023

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.

@bemasher
Copy link
Owner

bemasher commented Aug 5, 2023

I agree, it would be a quality of life improvement. I'll have a look at it.

@Oxalin
Copy link

Oxalin commented Nov 22, 2023

I'm not using a container and I'm hitting the same error under Raspberry Pi OS Bookworm. Do you think it is related?

@Oxalin
Copy link

Oxalin commented Nov 22, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants