Server xyz will be ignored for 10 minutes

[progressive002]

Hello, I keep having the recurring issue shown below - ive had to remove the links bare so bear with me please

Code: Select all

WARNING a few seconds ago Server newshosting will be ignored for 10 minutes
WARNING a few seconds ago Cannot connect to server newshosting [Server name does not resolve]

After 10 minutes it will retry and either block for another 10 minutes, or succeed. If I force unblock (status and interface -> connections -> UNBLOCK) then it will try to reconnect and succeed 90% of the time. If it fails I hit unblock until it connects.

truncated log isn't much more help but shows:

Code: Select all

2025-03-19 08:52:43,917::INFO::[notifier:157] Sending notification: NZB added to queue - xyz.nzb (type=download, job_cat=movies)
2025-03-19 08:53:27,942::INFO::[happyeyeballs:205] Quickest IP address for self-test (port=443, IPv4-only): x.x.x.x.x.x (self-test)
2025-03-19 08:53:35,114::INFO::[notifier:157] Sending notification: Warning - Cannot connect to server newshosting [Server name does not resolve] (type=warning, job_cat=None)
2025-03-19 08:53:35,114::WARNING::[downloader:479] Cannot connect to server newshosting [Server name does not resolve]
2025-03-19 08:53:35,114::INFO::[notifier:157] Sending notification: Warning - Server newshosting will be ignored for 10 minutes (type=warning, job_cat=None)

Clicks UNBLOCK

2025-03-19 08:53:35,114::WARNING::[downloader:481] Server newshosting will be ignored for 10 minutes
2025-03-19 08:53:37,424::WARNING::[downloader:479] Cannot connect to server newshosting [Server name does not resolve]

Clicks UNBLOCK

2025-03-19 08:53:37,424::WARNING::[downloader:481] Server newshosting will be ignored for 10 minutes

Clicks UNBLOCK

2025-03-19 08:53:40,940::INFO::[happyeyeballs:205] Quickest IP address for newshosting (port=563, IPv4 or IPv6): 85.12.62.251 (news)
2025-03-19 08:53:41,039::INFO::[downloader:616] 9@newshosting: Initiating connection
2025-03-19 08:53:41,050::INFO::[downloader:616] 8@newshosting: Initiating connection
2025-03-19 08:53:41,050::INFO::[downloader:616] 1@newshosting: Initiating connection
2025-03-19 08:53:41,051::INFO::[downloader:616] 5@newshosting: Initiating connection
2025-03-19 08:53:41,051::INFO::[downloader:616] 6@newshosting: Initiating connection
2025-03-19 08:53:41,052::INFO::[downloader:616] 7@newshosting: Initiating connection
2025-03-19 08:53:41,052::INFO::[downloader:616] 10@newshosting: Initiating connection
2025-03-19 08:53:41,052::INFO::[downloader:616] 4@newshosting: Initiating connection
2025-03-19 08:53:41,052::INFO::[downloader:616] 3@newshosting: Initiating connection
2025-03-19 08:53:41,053::INFO::[downloader:616] 2@newshosting: Initiating connection
2025-03-19 08:53:41,451::INFO::[newswrapper:351] 9@newshosting: Connected using TLSv1.3 (TLS_AES_256_GCM_SHA384)
2025-03-19 08:53:41,454::INFO::[newswrapper:351] 6@newshosting: Connected using TLSv1.3 (TLS_AES_256_GCM_SHA384)
2025-03-19 08:53:41,454::INFO::[newswrapper:351] 8@newshosting: Connected using TLSv1.3 (TLS_AES_256_GCM_SHA384)
2025-03-19 08:53:41,455::INFO::[newswrapper:351] 1@newshosting: Connected using TLSv1.3 (TLS_AES_256_GCM_SHA384)
2025-03-19 08:53:41,456::INFO::[newswrapper:351] 3@newshosting: Connected using TLSv1.3 (TLS_AES_256_GCM_SHA384)
2025-03-19 08:53:41,456::INFO::[newswrapper:351] 5@newshosting: Connected using TLSv1.3 (TLS_AES_256_GCM_SHA384)
2025-03-19 08:53:41,456::INFO::[newswrapper:351] 4@newshosting: Connected using TLSv1.3 (TLS_AES_256_GCM_SHA384)
2025-03-19 08:53:41,457::INFO::[newswrapper:351] 7@newshosting: Connected using TLSv1.3 (TLS_AES_256_GCM_SHA384)
2025-03-19 08:53:41,457::INFO::[newswrapper:351] 2@newshosting: Connected using TLSv1.3 (TLS_AES_256_GCM_SHA384)
2025-03-19 08:53:41,458::INFO::[newswrapper:351] 10@newshosting: Connected using TLSv1.3 (TLS_AES_256_GCM_SHA384)
2025-03-19 08:53:42,048::INFO::[downloader:751] Connecting 9@newshosting finished
2025-03-19 08:53:42,048::INFO::[downloader:751] Connecting 1@newshosting finished
2025-03-19 08:53:42,049::INFO::[downloader:751] Connecting 6@newshosting finished
2025-03-19 08:53:42,049::INFO::[downloader:751] Connecting 8@newshosting finished
2025-03-19 08:53:42,050::INFO::[downloader:751] Connecting 4@newshosting finished
2025-03-19 08:53:42,051::INFO::[downloader:751] Connecting 2@newshosting finished
2025-03-19 08:53:42,051::INFO::[downloader:751] Connecting 7@newshosting finished
2025-03-19 08:53:42,052::INFO::[downloader:751] Connecting 5@newshosting finished
2025-03-19 08:53:42,052::INFO::[downloader:751] Connecting 10@newshosting finished
2025-03-19 08:53:42,053::INFO::[downloader:751] Connecting 3@newshosting finished

I'm running my whole arr stack through proxmox, standalone ubunutu server vm and docker. I had no issues for around 6 months until the last month or so where this issues pops up. Have flushed DNS on the VM but that hasn't made a difference.

Ideally I'd like to fix whatever is causing the DNS issue, however if I could find the config var to change 10 minutes to 10 seconds that would also work fine.

Thanks.

[sander]

Yes. Without working DNS, all kinds of strange stuff can happen.
Ugly workaround: fill out in / etc / hosts


If you run from source: change the value here in sanbzbd/downloader.py

_PENALTY_TIMEOUT = 10 # Server doesn't give an answer (multiple times)

[progressive002]

Brilliant thank you. Modifying downloader . py has worked perfectly.

Unsure what the core issue is with my DNS, particularly given the intermittent nature of the fault, but hey the work around is great so thank you!!

[sander]

Cool.

You run from source .... so ... Linux? Then the trick with /etc /hosts might be less ugly, and survives updates

[progressive002]

So would that just be mapping the news.newshosting domain name to 85.12.62.251 in hosts?

[sander]

yes