-
Notifications
You must be signed in to change notification settings - Fork 51
Tracker Checker (UDP): Don't stop on the first fail #1040
Copy link
Copy link
Closed
Labels
Enhancement / Feature RequestSomething NewSomething New
Description
Parent issue: #669
When you run the checker for multiple UDP trackers, it stops when the first tracker check fails.
How to reproduce
Run the checker without running the tracker:
TORRUST_CHECKER_CONFIG='{
"udp_trackers": [
"127.0.0.1:6969",
"127.0.0.1:6969/",
"127.0.0.1:6969/announce",
"localhost:6969",
"localhost:6969/",
"localhost:6969/announce",
"udp://127.0.0.1:6969",
"udp://127.0.0.1:6969/",
"udp://127.0.0.1:6969/announce",
"udp://localhost:6969",
"udp://localhost:6969/",
"udp://localhost:6969/announce"
],
"http_trackers": [],
"health_checks": []
}' cargo run --bin tracker_checker Finished `dev` profile [optimized + debuginfo] target(s) in 0.12s
Running `target/debug/tracker_checker`
2024-09-12T15:22:55.457880Z INFO torrust_tracker::console::clients::checker::service: Running checks for trackers ...
[
{
"Udp": {
"Err": {
"remote_addr": "127.0.0.1:6969",
"results": [
[
"Setup",
{
"Ok": null
}
],
[
"Connect",
{
"Err": "Failed to receive a connect response, with error: Timeout while waiting for the socket to become readable."
}
]
]
}
}
}
]
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Enhancement / Feature RequestSomething NewSomething New