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 if all TAL files are deleted after running routinator init #210

Closed
ximon18 opened this issue Sep 6, 2019 · 0 comments · Fixed by #212
Closed

Panic if all TAL files are deleted after running routinator init #210

ximon18 opened this issue Sep 6, 2019 · 0 comments · Fixed by #212
Labels
bug Something isn't working

Comments

@ximon18
Copy link
Member

ximon18 commented Sep 6, 2019

With Routinator 0.5.1 (Docker) after init -f --accept-arin-rpa and docker run -d:

> docker exec -it routinator /bin/sh
/ $ rm /home/routinator/.rpki-cache/tals/*
/ $ exit

> docker restart routinator

> docker logs routinator
...
routinator    | Starting RTR listener.
routinator    | thread 'main' panicked at 'capacity must be non-zero', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/crossbeam-queue-0.1.2/src/array_queue.rs:103:9
routinator    | note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

My intent was to have just a single TAL file for testing Krill, but I forgot to put the Krill TAL file in the tals/ directory before restarting Routinator and thus had zero TAL files present.

@ximon18 ximon18 added the bug Something isn't working label Sep 6, 2019
@ximon18 ximon18 changed the title Panic if TAL all files are deleted after running routinator init Panic if all TAL files are deleted after running routinator init Sep 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant