Article failure: Isn't next server supposed to be tried?

Get help, report and discuss bugs.
jimboe
Posts: 39
Joined: 08 Jan 2013, 05:50

Article failure: Isn't next server supposed to be tried?

Post by jimboe » 25 Oct 2017, 19:31

This download (age ~2700 days) is out of my "level 0" servers' retention (which nzbget determined by attempting to grab it from there-- retention time is set to "0" for all servers), so nzbget fell-back to my "level 1" (Server 2), which has a longer retention.
nzbgetArticleFail20171025.jpg
As you can see in the snapsot, there was a bad article found in one of the rars. My question is, I don't see any evidence looking through the log in the web interface (or grep'ing thru the actual nzbget.log on the command line) that ANY of the subsequent "higher level" servers (there are 4 more entries) were tried for the failed file.

Should not nzbget have tried to grab this article from the servers on the higher levels? Or is there some reason in this situation it does not?

Here's what the server setup in my ~/.nzbget looks like:
(note: S3 and S4 are one the same level as they are different server farms on the same account)

Code: Select all

Server1.Active=yes
Server1.Name=S1
Server1.Level=0
Server1.Optional=no
Server1.Group=0
Server1.Host=my.news.server1
Server1.Port=119
Server1.Username= ...
Server1.Password= ...
Server1.JoinGroup=no
Server1.Encryption=no
Server1.Cipher=
Server1.Connections=12
Server1.Retention=0
Server1.IpVersion=auto
Server1.Notes=

Server2.Active=yes
Server2.Name=S2
Server2.Level=1
Server2.Optional=no
Server2.Group=0
Server2.Host=my.news.server2
Server2.Port=119
Server2.Username= ...
Server2.Password= ...
Server2.JoinGroup=no
Server2.Encryption=no
Server2.Cipher=
Server2.Connections=10
Server2.Retention=0
Server2.IpVersion=auto
Server2.Notes=

Server3.Active=yes
Server3.Name=S3
Server3.Level=2
Server3.Optional=no
Server3.Group=0
Server3.Host=my.news.server3
Server3.Port=119
Server3.Username= ...
Server3.Password= ...
Server3.JoinGroup=no
Server3.Encryption=no
Server3.Cipher=
Server3.Connections=6
Server3.Retention=0
Server3.IpVersion=auto
Server3.Notes=

Server4.Active=yes
Server4.Name=S4
Server4.Level=2
Server4.Optional=no
Server4.Group=0
Server4.Host=my.news.server4
Server4.Port=119
Server4.Username= ...
Server4.Password= ...
Server4.JoinGroup=no
Server4.Encryption=no
Server4.Cipher=
Server4.Connections=6
Server4.Retention=0
Server4.IpVersion=auto
Server4.Notes=

Server5.Active=yes
Server5.Name=S5
Server5.Level=3
Server5.Optional=no
Server5.Group=0
Server5.Host=my.news.server5
Server5.Port=119
Server5.Username= ...
Server5.Password= ...
Server5.JoinGroup=no
Server5.Encryption=no
Server5.Cipher=
Server5.Connections=20
Server5.Retention=0
Server5.IpVersion=auto
Server5.Notes=

Server6.Active=yes
Server6.Name=S6
Server6.Level=4
Server6.Optional=no
Server6.Group=0
Server6.Host=my.news.server6
Server6.Port=119
Server6.Username= ...
Server6.Password= ...
Server6.JoinGroup=no
Server6.Encryption=no
Server6.Cipher=
Server6.Connections=15
Server6.Retention=0
Server6.IpVersion=auto
Server6.Notes=

hugbug
Developer & Admin
Posts: 7645
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: Article failure: Isn't next server supposed to be tried?

Post by hugbug » 25 Oct 2017, 19:59

Why do you think it didn't try it?

Click on history item, then on "Articles (total/completion)" to see which servers were used.

Per-article messages are logged as DETAIL. Set option DetailTarget=log, then you can analyse log-file. In your case you should look for messages regarding file ".r55". Each attempt on each server is logged.

It is also possible that nzb-file doesn't contain all segments, in such NZBGet shows health-badge directly after adding nzb-file to queue.

jimboe
Posts: 39
Joined: 08 Jan 2013, 05:50

Re: Article failure: Isn't next server supposed to be tried?

Post by jimboe » 25 Oct 2017, 20:24

hugbug wrote:
25 Oct 2017, 19:59
Why do you think it didn't try it?
Because I grep'd in "nzbget.log" for each of the other server names and got no results.
Click on history item, then on "Articles (total/completion)" to see which servers were used.
I've done this too. This shows, 100% failure for the Server 1 and 100% success for Server 2. Servers 3-6 have no entry at all. Also, the yellow badge next to the item says "Backup 100%"
Per-article messages are logged as DETAIL. Set option DetailTarget=log, ... look for messages regarding file ".r55". Each attempt on each server is logged.
DetailTarget=log was set. The only warn|fail|error was in the picture in the OP.
It is also possible that nzb-file doesn't contain all segments, in such NZBGet shows health-badge directly after adding nzb-file to queue.
Pretty sure it said 100% when added, BUT, as I think about it, maybe it downloaded fine but the initial quick par check after the download completed failed on that one article?

Does that make sense from the snapshot in the OP?

hugbug
Developer & Admin
Posts: 7645
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: Article failure: Isn't next server supposed to be tried?

Post by hugbug » 25 Oct 2017, 20:31

Filter the log for ".r55" and you should see what was happening. Post the filtered log via pastebin.com or send me the full log-file if you can't find anything useful.

jimboe
Posts: 39
Joined: 08 Jan 2013, 05:50

Re: Article failure: Isn't next server supposed to be tried?

Post by jimboe » 26 Oct 2017, 18:19

hugbug wrote:
25 Oct 2017, 20:31
Filter the log for ".r55" and you should see what was happening. Post the filtered log via pastebin.com or send me the full log-file if you can't find anything useful.
I see nothing. emailed you logs.

hugbug
Developer & Admin
Posts: 7645
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: Article failure: Isn't next server supposed to be tried?

Post by hugbug » 29 Oct 2017, 16:54


jimboe
Posts: 39
Joined: 08 Jan 2013, 05:50

Re: Article failure: Isn't next server supposed to be tried?

Post by jimboe » 29 Oct 2017, 21:24

Thank you Hugbug!

You're dedication and skills are MOST IMPRESSIVE!!

hugbug
Developer & Admin
Posts: 7645
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: Article failure: Isn't next server supposed to be tried?

Post by hugbug » 29 Oct 2017, 21:34

Have you tried r2147 already? I wonder if it works at all on your device (I hope it will). I've changed C-library from uClibc to glibc on x86 and ARM in this release, which may cause compatibility issues (I really hope it doesn't).

jimboe
Posts: 39
Joined: 08 Jan 2013, 05:50

Re: Article failure: Isn't next server supposed to be tried?

Post by jimboe » 29 Oct 2017, 21:52

hugbug wrote:
29 Oct 2017, 21:34
Have you tried r2147 already? I wonder if it works at all on your device (I hope it will). I've changed C-library from uClibc to glibc on x86 and ARM in this release, which may cause compatibility issues (I really hope it doesn't).
I am going to install right now and try it for tonight's d/l's ..

Is there any caveat for installing/testing the beta release? can I simply,
# sh nzbget-20.0-testing-r2147-bin-linux.run --destdir /usr/local/bin/

like I do for stable? without any issues? Or must I uninstall first? (I'd assume no)

hugbug
Developer & Admin
Posts: 7645
Joined: 09 Sep 2008, 11:58
Location: Germany

Re: Article failure: Isn't next server supposed to be tried?

Post by hugbug » 29 Oct 2017, 21:59

You can install testing from webui: Settings -> SYSTEM -> Check for updates. Updates usually go smooth but there is always a chance of (serious) bugs in testing versions.

You can also install into a separate directory and test it there without interfering with your existing setup (just shutdown your main instance first). In the new instance you can use Settings -> SYSTEM -> Restore to quickly load news server settings from your existing config file (better don't restore other settings).

Post Reply

Who is online

Users browsing this forum: No registered users and 64 guests