Mylar doesn't seem to be searching

Post any problems / bugs / issues that are Mylar-related in here.
Post Reply
cornucrapia
Posts: 5
Joined: Sun Sep 02, 2018 11:30 pm

Mylar doesn't seem to be searching

Post by cornucrapia » Sun Sep 02, 2018 11:35 pm

Hi there,

I noticed Mylar hadn't grabbed anything in at least a week, so I went to do some digging. I'm running mylar, nzbhydra, and sabnzbd in docker containers.
If I test the search provider mylar tells me it's all good, and I can see a successful search attempt in nzbhydra. If I do a manual search or tell mylar to force search for everything I get basically nothing.
Mylar logs on debug mode:

Code: Select all

2018-09-02 17:25:09	INFO	Initiating manual search for <Comic>
2018-09-02 17:25:09	DEBUG	mode:want
2018-09-02 17:25:09	DEBUG	ComicID:<ComicID>
2018-09-02 17:24:50	INFO	Successfully tested <my server> nzbhydra [http://<my server>:5076] - valid api response received
2018-09-02 17:24:50	INFO	Connected - Status code returned: 200
2018-09-02 17:24:45	INFO	host: http://<my server>:5076/api
2018-09-02 17:23:09	INFO	Successfully tested <my server> nzbhydra [http://<my server>:5076] - valid api response received
2018-09-02 17:23:09	INFO	Connected - Status code returned: 200
2018-09-02 17:23:06	INFO	host: http://<my server>:5076/api
2018-09-02 17:22:56	DEBUG	If you can read this message, debug logging is now working
Absolutely nothing shows up on the nzbhydra side for the manual search
If I search for a comic manually in hydra and download it, mylar will pick it up on the folder scan and do the post processing, so it seems to be just something to do with the actual search not being triggered.
Thoughts on what it could be? Any other info I can provide to help debug?

Thanks.
Last edited by cornucrapia on Fri Sep 07, 2018 2:17 am, edited 1 time in total.

User avatar
evilhero
Site Admin
Posts: 2254
Joined: Sat Apr 20, 2013 3:43 pm
Contact:

Re: Mylar doesn't seem to be searching

Post by evilhero » Thu Sep 06, 2018 4:02 pm

I believe we changed things to support v2 of hydra, but v1 hydra should still work as well. Since I don't run hydra, can you enable debug logging and then perform a search for a given issue? I'd need to see the debug logs to see what url is being passed from hydra back to Mylar or vice-versa and see what's happening, as it was working a few months ago when some issues were brought forth, but nothing has come up in regards to any new problems since.

cornucrapia
Posts: 5
Joined: Sun Sep 02, 2018 11:30 pm

Re: Mylar doesn't seem to be searching

Post by cornucrapia » Fri Sep 07, 2018 2:17 am

Thanks for the reply.
So on the Mylar side, all the logging I see is in my original post, which is in debug mode. You can see that when I run the test I get a valid response, but there are no further messages beyond that it's initiating a manual search. On the hydra side it's similar, I'll put some logs below:

Code: Select all

2018-09-06 20:12:38.564  INFO --- [0.0-5076-exec-5] org.nzbhydra.api.ExternalApi             : [Search: 511778, IP: 172.19.0.1] Executing new search
2018-09-06 20:12:38.567  INFO --- [0.0-5076-exec-5] o.n.searching.IndexerForSearchSelector   : [Search: 511778, IP: 172.19.0.1] Selected 3 out of 3 indexers: altHUB, nzbplanet, NZBCat
2018-09-06 20:12:38.568  INFO --- [l-1078-thread-2] org.nzbhydra.indexers.Newznab            : [Search: 511778, IP: 172.19.0.1] nzbplanet: Calling https://nzbplanet.net/api?apikey=<apikey>&t=search&extended=1&limit=100&offset=0
2018-09-06 20:12:38.568  INFO --- [l-1078-thread-3] org.nzbhydra.indexers.Newznab            : [Search: 511778, IP: 172.19.0.1] altHUB: Calling https://api.althub.co.za/api?apikey=<apikey>&t=search&extended=1&limit=100&offset=0
2018-09-06 20:12:38.568  INFO --- [l-1078-thread-1] org.nzbhydra.indexers.Newznab            : [Search: 511778, IP: 172.19.0.1] NZBCat: Calling https://nzb.cat/api?apikey=<apikey>&t=search&extended=1&limit=100&offset=0
2018-09-06 20:12:39.567  INFO --- [l-1078-thread-1] org.nzbhydra.indexers.Newznab            : [Search: 511778, IP: 172.19.0.1] NZBCat: Successfully executed search call in 980ms with 100 results
2018-09-06 20:12:41.741  INFO --- [l-1078-thread-2] org.nzbhydra.indexers.Newznab            : [Search: 511778, IP: 172.19.0.1] nzbplanet: Successfully executed search call in 3164ms with 100 results
2018-09-06 20:12:42.611  INFO --- [l-1078-thread-3] org.nzbhydra.indexers.Newznab            : [Search: 511778, IP: 172.19.0.1] altHUB: Successfully executed search call in 4033ms with 100 results
2018-09-06 20:12:42.634  INFO --- [0.0-5076-exec-5] org.nzbhydra.searching.Searcher          : [Search: 511778, IP: 172.19.0.1] Returning results 1-100 from 291 results in cache. A total of 4780169 results is available from indexers of which 0 were already rejected and 9 were removed as duplicates
2018-09-06 20:12:42.636  INFO --- [0.0-5076-exec-5] org.nzbhydra.api.ExternalApi             : [Search: 511778, IP: 172.19.0.1] Search took 4072ms. Returning 100 results
I ran a manual search after that test and nothing showed up in the log

I'm running hydra 2.0.3 and Mylar Version: b98e0fc8263a1b6962fe75b1a0bd664c24188d19 (master)
Both are installed in docker containers built from inuxserver/mylar:latest and linuxserver/hydra2:latest

I'm happy to provide more information, but Mylar doesn't seem to be generating anything beyond what I've already posted, even in debug mode. Please let me know if I've missed anything.

Thanks

Klh
Posts: 2
Joined: Sun Mar 04, 2018 8:08 am

Re: Mylar doesn't seem to be searching

Post by Klh » Fri Sep 07, 2018 10:02 pm

I think I may have been having the same problem. Anything released since mid August was not being snatched. Manual searches via NZBHydra v1 were giving results. Just now, I decided to change the provider order in the ini file to 0, nzbhydra (then public, experimental). Immediately after removing a few "folder-scanned" items and setting them back to "wanted", mylar grabbed them from nzbhydra. YMMV

I'm running on Synology using Synocommunity packages for Mylar, NZBHydra v1, and Sabnzbd.

cornucrapia
Posts: 5
Joined: Sun Sep 02, 2018 11:30 pm

Re: Mylar doesn't seem to be searching

Post by cornucrapia » Sun Sep 09, 2018 1:14 am

I think I'm already configured that way, here's my ini:

Code: Select all

[Providers]
usenet_retention = 1500
provider_order = 0, <myserver> nzbhydra
does that look right? I don't have anything else under Providers

User avatar
evilhero
Site Admin
Posts: 2254
Joined: Sat Apr 20, 2013 3:43 pm
Contact:

Re: Mylar doesn't seem to be searching

Post by evilhero » Mon Sep 10, 2018 3:33 pm

I still have to verify the problems with v2 usage with Mylar at this point based on your log (since I don't run it normally, it's not just a quick test).

The provider order should be just a simple (as an example):

Code: Select all

0, <provider name>, 1, <provider name>
where provider name is the exact Newznab Name provided under Newznab Providers in the Mylar Search Providers configuration tab.

What do you have for Newznab Name for your nzbhydra instance within Mylar ? And is it enabled within Mylar ? (You can see your current enabled search providers/order just by going to the Search Providers tab within the configuration and at the very top it will display the search order).

cornucrapia
Posts: 5
Joined: Sun Sep 02, 2018 11:30 pm

Re: Mylar doesn't seem to be searching

Post by cornucrapia » Tue Sep 11, 2018 2:31 am

I understand it's not a quick test, I appreciate the help and will provide any info I can.
Under search providers I only have the one NewzNab listed:
istation nzbhydra
It's checked as enabled and when I click the Test button it reports that it's successful, as shown in my posts above.
From my config file:

Code: Select all

[Newznab]
newznab = True
extra_newznabs = istation nzbhydra, http://istation:5076, 0, <api key>, , 1

[Providers]
usenet_retention = 1500
provider_order = 0, istation nzbhydra

User avatar
evilhero
Site Admin
Posts: 2254
Joined: Sat Apr 20, 2013 3:43 pm
Contact:

Re: Mylar doesn't seem to be searching

Post by evilhero » Tue Sep 11, 2018 3:04 pm

Ok, so I just installed v2, set up one single indexer within it (ALThub), left everything as is setting wise therein and added the info into Mylar. Saved the config, searched. Found the item just fine, retrieved it and post-processed ended things successfully.

So this leads me to believe that you might have some config setting setup within hydra that's doing something with the searches for some reason.

Do you have anything setup differently than a default install of hydra if you can recall ?
Do you have anything under the Categories / Comics section within nzbhydra ?
Are you using hydra with torrent providers instead of/as well as newznab-based providers?

cornucrapia
Posts: 5
Joined: Sun Sep 02, 2018 11:30 pm

Re: Mylar doesn't seem to be searching

Post by cornucrapia » Thu Sep 13, 2018 1:47 am

Hmmm, this is weird. Starting to consider a reinstall.

I didn't really mess with my hydra install, it seemed to work right from the docker container setup. Beyond hooking it into sabnzbd I don't remember changing any configs.

I don't see anything out of the ordinary under the comics section,

Code: Select all

Name: Comic
Search type: General
Sub type: Comic
Apply restrictions: All searches
required words, regex, forbidden words, regex all blank
size preset 1MB:250MB
Limit API results size: off
Newznab categories: 7030
Ignore results: never
My whole setup, hydra and mylar is only newznab.

Post Reply