Sonarr version (exact version): 2.0.0.4326 OS: Windows 10 ((Debug logs)):
Indexer API call returned error 5: Too many requests per second. Maximum requests allowed are 1req/2sec Please try again later!
NzbDrone.Core.Indexers.Exceptions.IndexerException: Indexer API call returned error 5: Too many requests per second. Maximum requests allowed are 1req/2sec Please try again later!
For some reason after latest September’s update - i am unable to download anything from Rarbg the first time i try manual or automatic search. It returns the error described above. However if i switch to indexers and click “test” on rarbg - everything starts to work fine.
Sonarr may be making multiple calls to the API to get all the results (or making a different request in order to get results as the first one returned none) and is being blocked by RARBG, Sonarr will stop using it temporarily to avoid continuing to run into the limit, testing successfully will immediately clear the block. Sonarr’s behaviour wasn’t changed in the latest update, but may coincide with a change on RARBG’s side.
Without seeing ((debug logs)) of the search it’s all hypothetical.
Sonarr will stop using it temporarily to avoid continuing to run into the limit, testing successfully will immediately clear the block.
Actually, markus, the Ratelimit logic in Sonarr is a pure sleep, it doesn’t trigger the back-off logic. For rarbg it’s set to 2 sec.
But I suspect rarbg has the ratelimit on the IP address, so if there are multiple services with that IP using the rarbg api, that could explain why the limit is exceeded.
Sonarr is only making one request which is getting blocked by RARBG (Sonarr is just logging the error). Do you have something else using the RARBG API from that IP? Or are you using something with a shared IP (ie. seedbox or VPN)?
It only happens once a day. Basically i switch my pc on, check sonarr, try to download something but it doesn’t find anything and produce the error above, so i switch to settings->indexers->test rarbg and everything works fine after that for the rest of the day.
I’ve tried switching off rss syncing and rebooting but it didn’t make any difference.
Please turn on ((trace logging)) (In Sonarr’s general settings) and post the logs after you start up your system in the morning, this will give us more information on how the requests are being made to RARBG.
It seems like something on RARBG changed and getting the token is now included in the rate limiting and Sonarr wasn’t waiting between requests, in the latest develop versions have a fix for this already and it should be in the next master release.
NzbDrone.Core.Indexers.Exceptions.IndexerException: Indexer API call returned error 5: Too many requests per second. Maximum requests allowed are 1req/2sec Please try again later!
at NzbDrone.Core.Indexers.Rarbg.RarbgParser.ParseResponse(IndexerResponse indexerResponse) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Indexers\Rarbg\RarbgParser.cs:line 40
at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchPage(IndexerRequest request, IParseIndexerResponse parser) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:line 286 at NzbDrone.Core.Indexers.HttpIndexerBase1.FetchReleases(IndexerPageableRequestChain pageableRequestChain, Boolean isRecent) in M:\BuildAgent\work\6c3239faf2b92630\src\NzbDrone.Core\Indexers\HttpIndexerBase.cs:line 143
If Sonarr is still making two quick requests you’ll get that, the fix hasn’t been released to master yet, if you checked System: Updates you’d see there hasn’t been an update since before October 3rd.
