-
Notifications
You must be signed in to change notification settings - Fork 33
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
DB Sig failed to download messages make it harder to see in the logs if there's something wrong. #112
Comments
Could you please post the logs:
|
let me try that again.... If you could add a flag that doesn't attempt to download (or doesn't show failures of downloading sigs.) I had a problem where the dbs were failing to download (was a problem with the mirror) but the logs have been rotated already. But to give you an idea - there's just a lot of 404s, it'd be really nice to suppress them. Don't need help debugging what the issue was - I moved to a different mirror, but the 404s in the logs don't help.
|
I'd like to do this aswell, the 404 downloads for the *.db.sig are very annoying in the log. Is there a flag that can be set to not download the .sig files? |
Thank you for your work on pacoloco. Love it, love that it exists and it's a great tool, especially the prefetch component.
I recently had a problem where I wasn't getting any updates. While scanning the logs I saw a bunch of db.sigs failed to download - normal I thought, then realized that the .db was also failing.
Would it be possible to put behind a flag (or just an if) to not download sigs for the DBs? It would make the logs much easier to find errors, and also to setup logging rules and alerting (to indicate when there is a problem)
The text was updated successfully, but these errors were encountered: