Page 1 of 1

Remote NZB interface takes 30s+ when NBP is busy

PostPosted: Mon Apr 02, 2018 7:52 am
by Biship
The remote NZB interface works beautifully from Sonarr, Radarr and Lidarr most of the time.
However, NBP can time out returning a response (only from a download queue query as far as i can see).
I know the download query works most of the time as downloads have moving progress within the Sonarr interface.
It only seems to occur when NBP is 'busy'. The server isn't - CPU & Disk activity is under 50% at times I've checked. Busy as in many queued downloads & downloading at full speed.
I don't know what Sonarr's timeout is - possibly 30s. I know http://htpc:8999/api?apikey=<key>&mode=history takes 2s when NBP isn't busy, but can take ~30s(?) when it is. Even locally on the host.
Is it possible to prioritize calls via the NZB interface?

When multiple downloads are occurring, and a new item is added:
Code: Select all
18-4-2 00:40:56.6|Info|Sabnzbd|Adding report [some.nzb] to the queue. (successfull)
18-4-2 00:41:04.9|Info|DownloadService|Report sent to Newsbin. some.nzb.  (successfull)
...queries in this time frame are sucessfull...
18-4-2 00:46:40.3|Warn|Sabnzbd|Couldn't get download queue. Unable to connect to SABnzbd, please check your settings
[v10.0.0.12572] NzbDrone.Core.Download.Clients.DownloadClientUnavailableException: Unable to connect to SABnzbd, please check your settings ---> System.Net.WebException: The request was aborted: The operation has timed out.
at System.Net.HttpWebRequest.GetResponse()
...
at NzbDrone.Core.Download.Clients.Sabnzbd.Sabnzbd.GetQueue() in I:\Code\HTPC\Sonarr\src\NzbDrone.Core\Download\Clients\Sabnzbd\Sabnzbd.cs:line 57
18-4-2 00:48:20.3|Warn|DownloadMonitoringService|Unable to retrieve queue and history items from Newsbin