search

theotherp / nzbhydra2

Usenet meta search
Other
1.25k stars 75 forks source link

Integration with Sonarr not working #388

Closed masterxdk closed 5 years ago

masterxdk commented 5 years ago

Debug log file from NZBHydra2 (http://127.0.0.1:5076/system/bugreport). If other tools are involved post their logs as well.** nzbhydra-debuginfos-2019-05-14-22-42.zip

What do you expect to happen? What does happen?

Have you searched for this problem? You don't have to answer, just make sure.

Can the problem be reproduced? How?

Use a proper title. Describe the problem succinctly, don't just copy and paste the error message.

If you use a docker container please tell me which one.

tehniemer commented 5 years ago

I've noticed this as well in sonarr and lidarr

Elehiggle commented 5 years ago

Are any of your Dockers' config locations mounted on a NAS/remote directory instead of a local one (eg. it would be fine if the Dockers run on the NAS and the config directory is on the NAS as well, but not if Dockers run on your PC and config directories are on the NAS)

theotherp commented 5 years ago

The searches in your log generally complete within less than 3 seconds. Sonarr times out after 20 or 30 seconds, I think. So that's not the issue. It seems that Sonarr cannot download the NZBs for some reason.

What happens when you try to download http://10.0.1.9:5076/getnzb/api/-1230418007023858395?apikey=API in your browser (using your Hydra API key)? Is that the URL you used to add Hydra to sonarr?

tehniemer commented 5 years ago

I'm getting some timeout issues with Sonarr, logs attached. nzbhydra-debuginfos-2019-05-15-10-39.zip

masterxdk commented 5 years ago

Are any of your Dockers' config locations mounted on a NAS/remote directory instead of a local one (eg. it would be fine if the Dockers run on the NAS and the config directory is on the NAS as well, but not if Dockers run on your PC and config directories are on the NAS)

No they are all stored locally on the Docker machine.

The searches in your log generally complete within less than 3 seconds. Sonarr times out after 20 or 30 seconds, I think. So that's not the issue. It seems that Sonarr cannot download the NZBs for some reason.

What happens when you try to download http://10.0.1.9:5076/getnzb/api/-1230418007023858395?apikey=API in your browser (using your Hydra API key)? Is that the URL you used to add Hydra to sonarr?

It seems to retrieve it after a few seconds. It tends to work fine after a restart of Hydra2, but then quickly falls back to not working.

theotherp commented 5 years ago

@tehniemer I see two downloads in the log, During which actions exactly are you getting timeouts? Do you see them in Hydra?

@masterxdk Hard to say what's going on, but as long as you can load the URLs hydra itself is working fine. Please set the sonarr log level to debug and wait for the next timeout. Send me the sonarr log and the new hydra debug infos.

tehniemer commented 5 years ago

@theotherp this is the timeout I noticed, it corresponded with an indexer test from Sonarr.

2019-05-15 10:26:16.280 ERROR --- [ool-10-thread-3] org.nzbhydra.indexers.Newznab            : [Search: 531592, Host: 192.168.29.134] NZBgeek: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.278 ERROR --- [ool-10-thread-1] org.nzbhydra.indexers.Newznab            : [Search: 531592, Host: 192.168.29.134] abNZB: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.252 ERROR --- [ool-29-thread-3] org.nzbhydra.indexers.Newznab            : [Search: 350184, Host: 192.168.29.133] NZBgeek: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.246 ERROR --- [ool-11-thread-5] org.nzbhydra.indexers.Newznab            : [Search: 569945, Host: 192.168.29.133] NZBFinder: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.105 ERROR --- [ool-29-thread-5] org.nzbhydra.indexers.Newznab            : [Search: 350184, Host: 192.168.29.133] NZBFinder: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.260 ERROR --- [ool-10-thread-5] org.nzbhydra.indexers.Newznab            : [Search: 531592, Host: 192.168.29.134] NZBFinder: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.253 ERROR --- [ool-10-thread-6] org.nzbhydra.indexers.Newznab            : [Search: 531592, Host: 192.168.29.134] NzbNoob: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.259 ERROR --- [ool-11-thread-3] org.nzbhydra.indexers.Newznab            : [Search: 569945, Host: 192.168.29.133] NZBgeek: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.098 ERROR --- [ool-11-thread-2] org.nzbhydra.indexers.Newznab            : [Search: 569945, Host: 192.168.29.133] DrunkenSlug: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.109 ERROR --- [ool-29-thread-1] org.nzbhydra.indexers.Newznab            : [Search: 350184, Host: 192.168.29.133] abNZB: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.100 ERROR --- [ool-29-thread-4] org.nzbhydra.indexers.Newznab            : [Search: 350184, Host: 192.168.29.133] altHUB: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:15.957 ERROR --- [ool-11-thread-4] org.nzbhydra.indexers.Newznab            : [Search: 569945, Host: 192.168.29.133] altHUB: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:27.006 ERROR --- [ool-10-thread-4] org.nzbhydra.indexers.Newznab            : [Search: 531592, Host: 192.168.29.134] altHUB: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.484 ERROR --- [ool-29-thread-2] org.nzbhydra.indexers.Newznab            : [Search: 350184, Host: 192.168.29.133] DrunkenSlug: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.102 ERROR --- [ool-11-thread-6] org.nzbhydra.indexers.Newznab            : [Search: 569945, Host: 192.168.29.133] NzbNoob: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:27.304 ERROR --- [ool-11-thread-1] org.nzbhydra.indexers.Newznab            : [Search: 569945, Host: 192.168.29.133] abNZB: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.278 ERROR --- [ool-10-thread-2] org.nzbhydra.indexers.Newznab            : [Search: 531592, Host: 192.168.29.134] DrunkenSlug: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:15.997 ERROR --- [ool-29-thread-8] org.nzbhydra.indexers.Newznab            : [Search: 350184, Host: 192.168.29.133] newz69.keagaming: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.479 ERROR --- [ool-10-thread-7] org.nzbhydra.indexers.Newznab            : [Search: 531592, Host: 192.168.29.134] SimplyNZBs: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.481 ERROR --- [ool-29-thread-6] org.nzbhydra.indexers.Newznab            : [Search: 350184, Host: 192.168.29.133] NzbNoob: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.483 ERROR --- [ool-11-thread-7] org.nzbhydra.indexers.Newznab            : [Search: 569945, Host: 192.168.29.133] SimplyNZBs: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.483 ERROR --- [ool-10-thread-8] org.nzbhydra.indexers.Newznab            : [Search: 531592, Host: 192.168.29.134] newz69.keagaming: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
2019-05-15 10:26:16.484 ERROR --- [ool-29-thread-7] org.nzbhydra.indexers.Newznab            : [Search: 350184, Host: 192.168.29.133] SimplyNZBs: An unexpected error occurred while communicating with the indexer: Indexer did not complete request within 20 seconds
theotherp commented 5 years ago

@tehniemer Yeah, well, the indexers can't be reached by Hydra. That's a completely different issue than @masterxdk has. Hard to say what's going on. Most likely a network issue.

masterxdk commented 5 years ago

@masterxdk Hard to say what's going on, but as long as you can load the URLs hydra itself is working fine. Please set the sonarr log level to debug and wait for the next timeout. Send me the sonarr log and the new hydra debug infos.

I think something is wrong with the default docker bridge network. Seems slow for some reason. Made a new network, shared it between Sonarr and Hydra2 and it seems to work better.

@tehniemer Yeah, well, the indexers can't be reached by Hydra. That's a completely different issue than @masterxdk has. Hard to say what's going on. Most likely a network issue.

Seems you were right, not sure why though.

Will close the ticket saying Hydra2 seems good, but docker network not so much. Thanks for the help and sorry i used your time

emopinata commented 5 years ago

@masterxdk Hard to say what's going on, but as long as you can load the URLs hydra itself is working fine. Please set the sonarr log level to debug and wait for the next timeout. Send me the sonarr log and the new hydra debug infos.

I think something is wrong with the default docker bridge network. Seems slow for some reason. Made a new network, shared it between Sonarr and Hydra2 and it seems to work better.

@tehniemer Yeah, well, the indexers can't be reached by Hydra. That's a completely different issue than @masterxdk has. Hard to say what's going on. Most likely a network issue.

Seems you were right, not sure why though.

Will close the ticket saying Hydra2 seems good, but docker network not so much. Thanks for the help and sorry i used your time

Docker's networking is unfortunately notoriously bad.

masterxdk commented 5 years ago

@masterxdk Hard to say what's going on, but as long as you can load the URLs hydra itself is working fine. Please set the sonarr log level to debug and wait for the next timeout. Send me the sonarr log and the new hydra debug infos.

I think something is wrong with the default docker bridge network. Seems slow for some reason. Made a new network, shared it between Sonarr and Hydra2 and it seems to work better.

@tehniemer Yeah, well, the indexers can't be reached by Hydra. That's a completely different issue than @masterxdk has. Hard to say what's going on. Most likely a network issue.

Seems you were right, not sure why though. Will close the ticket saying Hydra2 seems good, but docker network not so much. Thanks for the help and sorry i used your time

Docker's networking is unfortunately notoriously bad.

That sucks big time :/