Page 1 of 1
Endless cycle of servers working then timing out
Posted: March 3rd, 2024, 7:40 pm
by blissend
My setup...
- Sabnzbd Version: 4.2.2 [f730607]
- Docker container using linuxserverDOTio
- Running on a Synology DS916+
Been running this for years without issue. Something changed and trying to figure out what is preventing sabnzbd from downloading. When I click
Test Server button to...
- newsDOTsupernewsDOTcom
- newsDOTgiganewsDOTcom
via
config/server/ page it shows up as invalid server address.
What always works...
- Sabnzbd locally on my macbook
- dig/nslookup works on all devices
- traceroute to those ports
- telnet test with authserv works
So I thought I'll disable ipv6 via the special flags page and that worked. The
Test Server button always works now.
However the new problem is an endless cycle where it works for a bit before getting a time out in the logs like so...
Code: Select all
Thread 1@newsDOTsupernewsDOTcom: Timed out
The sabnzbd queue floods up to 11 pages when that happens. I only have 8 connections setup. How can I replicate this timeout? Why does the Test Server button work but logs keeping showing time outs?
Re: Endless cycle of servers working then timing out
Posted: March 3rd, 2024, 11:16 pm
by blissend
Ok I think I've now isolated it to certain downloads. When I do a queue repair and then use sabnzbd test download it works or an nzb file I know works it all works just fine until certain things get queued up start. That's when things time out. I have checked for missing articles turned on but didn't help. Still craps out.
Re: Endless cycle of servers working then timing out
Posted: March 4th, 2024, 2:35 am
by safihre
This will be fixed in 4.2.3. The release candidate is already out.
There is a problem with Giganews specifically.
Re: Endless cycle of servers working then timing out
Posted: March 4th, 2024, 12:21 pm
by blissend
safihre wrote: ↑March 4th, 2024, 2:35 am
This will be fixed in 4.2.3. The release candidate is already out.
There is a problem with Giganews specifically.
Oh thanks! Was going crazy trying to figure this out.
Re: Endless cycle of servers working then timing out
Posted: March 7th, 2024, 9:08 pm
by blissend
So I switched to the 4.2.3RC3 version (linuxserver.io docker) and it seems to work better now. However it has trouble with rar files...
Code: Select all
Your UNRAR version is 0.00, we recommend version 5.50 or higher.<br />
To prevent all helpful warnings, disable Special setting 'helpful_warnings'.
It seems to pull from
https://github.com/linuxserver/docker-unrar which seems to take from source code. I can't seem to figure out the unrar version command but I see it in /usr/bin/unrar. I also see files downloaded (rar files) but not uncompressed. Let me know if I can do anything else to help. How does it parse the unrar version?
EDIT: Oh I see it runs the unrar command without any other input if I read sabnzbd source right. In this case it outputs...
Code: Select all
root@c24ef75a4a61:/# unrar
Illegal instruction (core dumped)
Re: Endless cycle of servers working then timing out
Posted: March 7th, 2024, 10:45 pm
by sander
lsio is not provided by the SAB team.
However, I tried the lsio sabznbd image, and it goes well:
Code: Select all
$ sudo docker run lscr.io/linuxserver/sabnzbd:unstable
2024-03-08 03:44:33,429::INFO::[SABnzbd:1145] SABnzbd.py-4.2.3RC3
2024-03-08 03:42:34,085::INFO::[SABnzbd:458] UNRAR binary... found (/usr/bin/unrar)
2024-03-08 03:42:34,086::INFO::[SABnzbd:466] UNRAR binary version 7.00
So ... problem on your side?
Re: Endless cycle of servers working then timing out
Posted: March 7th, 2024, 10:56 pm
by blissend
Hmm didn't know you can use the tag unstable and it's already linked to 4.2.3. I was using the tag that specified it. Anyway now that I did that all is good! Weird.