Closed XxUnkn0wnxX closed 4 years ago
That NZB crashes the downloader on Windows as well, so I think there's something wrong with it.
2019-12-13 19:30:44,408::INFO::[__init__:1068] Restarting because of crashed downloader
2019-12-13 19:30:44,408::INFO::[__init__:772] [SABnzbd.py.main] Performing SABnzbd shutdown
2019-12-13 19:30:44,408::INFO::[__init__:385] SABnzbd shutting down...
but sab shouldn't crash because of a download. why doesnt it abort or say it cannot complete it? when i try do using newshosting client to download it goes further up to 23% & kinda just hangs there never finishes.
but that's not the case this has been happening with nzb's over the past month i have had like 3-4 others..
at least if they can find a way to fix this so it doesn't crash. its supposed to by default to try re-trying to download the pieces and if it hangs or cannot get the pieces & it gets stuck it just skips them & tries to download the rest. if they keep failing it should abort the download. why isn't it doing that?
I don't disagree, just pointing out that it's not only a Mac issue, and that there's specifically something wrong with the NZB. It should definitely handle whatever the issue is more gracefully.
I had SABnzbd downloading that .NZB, with a lot of problems indeed, like this:
2019-12-14 14:45:00,477::INFO::[decoder:174] Badly formed yEnc article in PhFmMuPbNjKgJoZtBrNnChZp-1571246207825@nyuu 2019-12-14 14:45:00,480::INFO::[decoder:174] Badly formed yEnc article in WaZaPgYsLvNdMmUoRhYiYlKs-1571246191321@nyuu 2019-12-14 14:45:00,486::INFO::[decoder:174] Badly formed yEnc article in IdIiLfXpTvKrCqBdGuHrRuJi-1571246183777@nyuu 2019-12-14 14:45:28,350::INFO::[init:1017] Restarting because of crashed downloader 2019-12-14 14:45:28,351::INFO::[init:754] [main.main] Performing SABnzbd shutdown 2019-12-14 14:45:28,351::INFO::[init:374] SABnzbd shutting down... 2019-12-14 14:45:28,351::INFO::[directunpacker:463] Aborting all DirectUnpackers
So SAB does recognize and describe the problem: [decoder:174] Badly formed yEnc article in
. That is at least something. Maybe a problem in the sabyenc (which is a binary module)
The SABnzbd shutting down.
is bad, and should not happen because of a malformed article, IMHO
@XxUnkn0wnxX did you try the same download with DirectUnpack unchecked.
@sanderjo yes i did, did not help..
Strange NZB this is.. It's causing faulty readings in decoder and downloader. Have to see how to fix it.
It may be related to a server problem as well. When I try to download only IdIiLfXpTvKrCqBdGuHrRuJi-1571246183777@nyuu using a perl downloader it will hang for 10 seconds before it continues. I get the header and nothing else, and the server responds with 430 No Such Article after QUIT.
Contacted our technical contact at NewsHosting to debug this, I am seeing the same as @puzzledsab. The problem is that it indeed sends the end-of-article, but then the server doesn't close the connection, but sends another status code. SABnzbd can't handle that second status code, because it already received end-of-article, so it no longer has a reference to an article on the connection. So it results in a crashed downloader.
Contacted our technical contact at NewsHosting to debug this, I am seeing the same as @puzzledsab. The problem is that it indeed sends the end-of-article, but then the server doesn't close the connection, but sends another status code. SABnzbd can't handle that second status code, because it already received end-of-article, so it no longer has a reference to an article on the connection. So it results in a crashed downloader.
why not have sab just ignore erroneous server responses?
Because up to now, it has never happend in this stage. We do ignore them when connecting, just not after receiving an article.
In any case, they informed me it's a bug in their server software and they'll fix it. I'll see in the mean time if I can implement a stability patch.
I looked at improving the code, but it became such a mess that I decided for now not too apply a patch. This behavior of sending data after end-of-article just triggers a number of things throughout the code, I can't patch them all.
Newshosting have reported that they fixed the problem on their end. I can confirm that it's no longer sending the weird status-codes. Closing this now, the patch will be distributed over their servers in the upcoming days.
Hi, i'm on the stable release version of Sab V 2.3.9 - macOS
i have been noticing when downloading some nzb's sab just randomly shuts down and never starts.
the message in the log is
Restarting because of crashed downloader
<--never restarts just shuts down& it usually occurs after a few Missing Articles missing (error=430), Badly formed yEnc article
Logs: Logs.zip
Sample Log:
& here is the NZB file it's failing to download: [KH] Nakaimo - My Sister is Among Them (BD 1080p) [Dual-Audio].nzb.gz gets to around 2.5 gigs & starts crapping out.. every time i start it again shuts down within 30-40 seconds.
this is not the 1st time i have noticed this with other nzb's but i cannot recall which ones. this is the most recent one that has caused this issue.
i use newshosting as my provider.
my settings: sabnzbd.ini.zip i stripped out the keys, passwords & login details.
this has become beyond frustrating, isn't sab supposed to abort the job if it's impossible to download, i have enabled that option..