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

ERROR: Limit exceeded ------. You should lower the connections to the tumblr api in Settings->Connections pane. #578

Open
GregoryWest501 opened this issue Oct 13, 2024 · 5 comments

Comments

@GregoryWest501
Copy link

Describe the bug
I keep getting this error and from that point forward none of the blogs are downloaded. What is the best way to get around this issue? Anyone have a set of Connection Settings that works for a large number of blogs?

To Reproduce
Steps to reproduce the behavior:
Select a few dozen blogs, do SHIFT - ENTER, Start the download.
After about 12-24 blogs the error pops up and nothing else downloads.

Desktop (please complete the following information):

  • TumblThree version: [e.g. 2.15.1.462]
  • OS: [e.g. Windows 10 Pro]
  • Browser [e.g. Chrome, Safari, IE, Edge] NA Authentication not working. Default browser is Edge
  • Version 129.0.2792.89 (Official build) (64-bit)

Any settings people use that work?

@ErikBrown2
Copy link

I use the following settings. Maybe they are a bit conservative but I do not get the error that you describe:

Concurrent connections: 1
Concurrent video connections: 1
Concurrent logs: 1
Scan connections: 4
Limit Tumblr API connections: 90 - 60
Limit Tumblr SVC connections: 90 - 60

@GregoryWest501
Copy link
Author

Thanks for the reply. That is what I have also. What do you have for TimeOut? I have 60, and do you have a bandwidth limitation?

@ErikBrown2
Copy link

These are my settings:

Screenshot 2024-10-21 165811

@GregoryWest501
Copy link
Author

Trying your settings out. So far it is looking good!!

@mjharwood
Copy link
Contributor

some of the API calls do not go through the same connection semaphore that limits connections during the "prep" stage of downloads. some downloaders don't share a connection semaphore either. So multiple types of blogs or a lot of blogs all downloading at once can exceed the API limit.

It's reproducible if you set concurrent blogs to a larger number, especially with large blogs.

I attempted to solve that locally and just got deadlocks, so needs more thought.

Limiting the concurrent blogs and current connections to 1 or 2 seem works, but is potentially slower.

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