-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Instance is getting slow upon failed geoip db update #6381
Labels
Status: Waiting for answer
Waiting issue author answer
Type: Bug 🐛
Confirmed bug, at least replicated once by another contributor
Type: Performance
Comments
kontrollanten
changed the title
Instance
Instance is getting slow upon failed geoip db update
May 7, 2024
Can you paste the error log so see what type of failure it is? |
Sorry, here it comes:
We had 1 563 occurrences in 17 minutes. It should be possible to throttle it to run once each ten minutes or so. |
4 tasks
Chocobozzz
added
Type: Bug 🐛
Confirmed bug, at least replicated once by another contributor
Type: Performance
labels
May 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Status: Waiting for answer
Waiting issue author answer
Type: Bug 🐛
Confirmed bug, at least replicated once by another contributor
Type: Performance
Describe the current behavior
Our instances fails to download the geoip db, which seems to slow down the whole server. Upon start the response time is OK, but then it seems to add on response time and then gets unresponsive. When disabling geoip in the config the server works well.
Steps to reproduce
Describe the expected behavior
Peertube should handle failed geoip db downloads gently and continue to work just as when the geoip config is disabled.
Additional information
PeerTube instance:
Browser name, version and platforms on which you could reproduce the bug:
Link to browser console log if relevant:
Link to server log if relevant (
journalctl
or/var/www/peertube/storage/logs/
):The text was updated successfully, but these errors were encountered: