I can no longer search within a series, because it’s still searching for something else (icon keeps rotating).
Log is filled with this:
Component Message Time
FetchFeedService Searching for [The Big Bang Theory : S06] offset: 1354680 2:01 PM
FetchFeedService Omgwtfnzbs offset [The Big Bang Theory : S06]. Found 100 2:01 PM
FetchFeedService Searching for [The Big Bang Theory : S06] offset: 1354590 2:00 PM
FetchFeedService Omgwtfnzbs offset [The Big Bang Theory : S06]. Found 100 2:00 PM
FetchFeedService Searching for [The Big Bang Theory : S06] offset: 1354500 2:00 PM
FetchFeedService Searching for [How I Met Your Mother : S08] offset: 706230 2:00 PM
FetchFeedService Omgwtfnzbs offset [The Big Bang Theory : S06]. Found 100 2:00 PM
FetchFeedService Omgwtfnzbs offset [How I Met Your Mother : S08]. Found 94 2:00 PM
FetchFeedService Searching for [The Big Bang Theory : S06] offset: 1354410 2:00 PM
Thursday, January 2 2014 2:00 PM
FetchFeedService Omgwtfnzbs offset [The Big Bang Theory : S06]. Found 100 2:00 PM
this goes on about 4000 pages.
Is there a way to restart nzbdrone without rebooting the computer? Sabnzbd, CP, SB, all have a button for this in the webinterface, but I haven’t found that in nzbdrone…
No there is not a shutdown or reboot in the UI, you can stop the drone service or kill it off via task manager for the time being.
I assume you’re using nzb megasearch? They don’t respect the offset parameter drone uses to ensure it gets the entire season when searching. Was hoping someone that used Megasearch would have opened an issue up with them, but I didn’t see one, so here it is: https://github.com/pillone/usntssearch/issues/110
Until thats fixed you will need to avoid season searches or go directly to the indexer.
As I suspected then. it would be nice to have a restart option in UI, as this service doesn’t run on my pc. It runs on my server, so I’d have to RDP into it, when I’m at home. When I’m away, no RDP option available.
I don’t use nzb megasearch, I use omgwtfnzbs. It has been able to download full seasons with automatic searches before, but now it seems to hang…
Installed nzbdrone on my new ubuntu server. Problem remains the same.
I added a series to test (Bones).
Nzbdrone first searched s09, downloaded all the episodes.
Then it searched s08 and has been doing so for the last five hours.
Sudo restart nzbdrone gets it back ofcourse, but it seems to hang at the same seasons everytime.
In the log, I can see the same as in the first post: searching for bones s08, always a different offset, always same number of found episodes
I included the log of the above described problem. Note that s09 was already fetched before, but as you can see, it processes as it should, where as s08 is in loop again.
FetchFeedService Searching for [Bones : S08] offset: 450 8:59 AM
FetchFeedService Omgwtfnzbs offset [Bones : S08]. Found 97 8:59 AM
FetchFeedService Searching for [Bones : S08] offset: 360 8:59 AM
FetchFeedService Omgwtfnzbs offset [Bones : S08]. Found 97 8:59 AM
FetchFeedService Searching for [Bones : S08] offset: 270 8:59 AM
FetchFeedService Omgwtfnzbs offset [Bones : S08]. Found 97 8:59 AM
FetchFeedService Searching for [Bones : S08] offset: 180 8:59 AM
FetchFeedService Omgwtfnzbs offset [Bones : S08]. Found 97 8:59 AM
FetchFeedService Searching for [Bones : S08] offset: 90 8:59 AM
FetchFeedService Omgwtfnzbs offset [Bones : S08]. Found 97 8:59 AM
FetchFeedService Finished searching Wombles for [Bones : S08]. Found 0 8:59 AM
FetchFeedService Wombles offset [Bones : S08]. Found 0 8:59 AM
FetchFeedService Searching for [Bones : S08] offset: 0 8:59 AM
FetchFeedService Searching for [Bones : S08] offset: 0 8:59 AM
FetchFeedService Searching for [Bones : S08] 8:59 AM
FetchFeedService Searching for [Bones : S08] 8:59 AM
NzbSearchService Searching 2 indexers for [Bones : S08] 8:59 AM
DownloadDecisionMaker Processing 36 reports 8:59 AM
NzbSearchService Total of 36 reports were found for [Bones : S09] from 2 indexers 8:59 AM
FetchFeedService Finished searching Omgwtfnzbs for [Bones : S09]. Found 36 8:59 AM
FetchFeedService Omgwtfnzbs offset [Bones : S09]. Found 36 8:59 AM
FetchFeedService Finished searching Wombles for [Bones : S09]. Found 0 8:59 AM
FetchFeedService Wombles offset [Bones : S09]. Found 0 8:59 AM
FetchFeedService Searching for [Bones : S09] offset: 0 8:59 AM
FetchFeedService Searching for [Bones : S09] offset: 0 8:59 AM
FetchFeedService Searching for [Bones : S09] 8:59 AM
FetchFeedService Searching for [Bones : S09] 8:59 AM
NzbSearchService Searching 2 indexers for [Bones : S09] 8:59 AM
Component Message Time
FetchFeedService Searching for [Bones : S08] offset: 175950 9:37 AM
FetchFeedService Omgwtfnzbs offset [Bones : S08]. Found 97 9:37 AM
The offset changes with +90 every time.
Its started at 08:59 I stopped it at 09:37.
It was at offset 175950 at that time, which equals to 1955 searches in 38 minutes (about 1 search/second)
What bothers me is it comes back with Found 97 every time, so the indexer does return a correct answer.
Looks like drone keeps requesting more results, which doesn’t appear to be supported on omgwtfnzbs, so its looping. Until that Trello ticket is closed you should avoid season/series searches because its going to hammer the indexer and never complete.
Its a bug… we’ll fix it, until then don’t do the thing that’s causing the bug. This is only an issue with omgwtfnzbs, newznab based indexers (the most common) don’t have this issue.
sorry, I copied that line yesterday to do a google search.
I saw it pass by again when I posted it, but it was too quick to copy what was in front of it.
It doesn’t show up at the logs, so for now no extra info.
