SABnzbd Forums

Hello,

I'm running into an issue with a specific NZB queue download. I noticed this morning that my queue was stalled at 0 speed with no connections. I tried restarting / repairing, but keep running into the same issue:

Once the CRC error is logged, Delaying messages appear, bandwidth throttles to 0 (bpsmeter prints out the throttling). Nothing else happens.. It'll sit like this forever, I tried it as a test and it was stuck like this for 8 hours overnight.

2013-01-06 08:29:16,563::DEBUG::[decoder:100] Decoding part678of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local
2013-01-06 08:29:16,582::DEBUG::[decoder:100] Decoding part685of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local
2013-01-06 08:29:16,602::DEBUG::[decoder:100] Decoding part642of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local
2013-01-06 08:29:16,622::DEBUG::[decoder:100] Decoding part666of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local
2013-01-06 08:29:16,642::DEBUG::[decoder:100] Decoding part682of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local
2013-01-06 08:29:16,653::DEBUG::[decoder:100] Decoding part650of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local
2013-01-06 08:29:16,655::INFO::[decoder:118] CRC Error in part650of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local (EDFC771B -> 2F33AD75)
2013-01-06 08:29:16,795::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,801::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,819::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,821::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,822::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,824::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,827::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,836::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,839::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,846::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,852::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,858::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,866::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,936::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,946::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,951::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,978::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:16,980::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:17,010::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:17,182::DEBUG::[downloader:229] Delaying
2013-01-06 08:29:21,226::DEBUG::[bpsmeter:253] bps: 2728187.02865
2013-01-06 08:29:26,273::DEBUG::[bpsmeter:253] bps: 1087887.79046

If I pause this job in the queue and restart, the next job runs fine. If I unpause this job, this same error replays, and bandwidth goes back to 0, stuck there.

So it appears only this CRC error on this job causes the stall.

I checked the settings and do not have the config "Fail on yenc crc Errors" enabled.

Anyone have pointers on how to fix this?

System info:
Version: 0.7.8
OS: Linux Tower 3.4.11-unRAID #1 SMP Mon Sep 17 17:36:21 PDT 2012 i686 Intel(R) Core(TM) i3-3240 CPU @ 3.40GHz GenuineIntel GNU/Linux)
Install-type: unRaid NAS package
Skin (if applicable): Default
Firewall Software: None
Are you using IPV6? no
Is the issue reproducible? yes ( on my end )

Thanks

There is a bug report regarding this issue in the bugs conference. I was curious and replaced /usr/share/sabnzbdplus/sabnzbd/decoder.py with the one from version 0.7.7 and it seems to have corrected it. But that might have broken something else for all I know.

Bug in decoder confirmed.
There will be a new release asap.

Thanks for your help! Much appreciated.

Glad to report that 0.7.9 addressed the issue. The decoder keeps going past the article (#650) with the bad CRC.


2013-01-06 15:49:47,561::DEBUG::[decoder:101] Decoding part650of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local
2013-01-06 15:49:47,562::INFO::[decoder:119] CRC Error in part650of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local (EDFC771B -> 2F33AD75)
2013-01-06 15:49:47,579::DEBUG::[decoder:101] Decoding part631of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local
2013-01-06 15:49:47,599::DEBUG::[decoder:101] Decoding part647of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local
2013-01-06 15:49:47,619::DEBUG::[decoder:101] Decoding part655of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local
2013-01-06 15:49:47,639::DEBUG::[decoder:101] Decoding part652of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local
2013-01-06 15:49:47,659::DEBUG::[decoder:101] Decoding part654of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local
2013-01-06 15:49:47,674::DEBUG::[decoder:101] Decoding part636of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local
2013-01-06 15:49:47,684::DEBUG::[decoder:101] Decoding part660of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local
2013-01-06 15:49:47,794::DEBUG::[decoder:101] Decoding part659of2004.VAHdIsVc0Q002beKoKjJ@powerpost2000AA.local

Cheers

I seem to have a simular error. Found the following in my log:

2013-01-07 10:56:43,489::INFO::[decoder:118] CRC Fejl i B8MZEI50X27Rsu9H98pV_36o97@local.ghost (C40BA954 -> C4EC0FF4)
2013-01-07 10:59:27,444::INFO::[downloader:657] Thread 29@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:35,607::INFO::[downloader:657] Thread 23@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:36,186::INFO::[downloader:657] Thread 11@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:39,298::INFO::[downloader:657] Thread 34@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:39,308::INFO::[downloader:657] Thread 10@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:39,717::INFO::[downloader:657] Thread 47@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:40,114::INFO::[downloader:657] Thread 30@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:40,493::INFO::[downloader:657] Thread 28@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:40,668::INFO::[downloader:657] Thread 14@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:41,588::INFO::[downloader:657] Thread 44@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:41,642::INFO::[downloader:657] Thread 27@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:41,763::INFO::[downloader:657] Thread 50@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:42,480::INFO::[downloader:657] Thread 49@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:43,042::INFO::[downloader:657] Thread 26@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:43,480::INFO::[downloader:657] Thread 1@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:43,788::INFO::[downloader:657] Thread 35@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:44,397::INFO::[downloader:657] Thread 6@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:44,605::INFO::[downloader:657] Thread 41@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:45,638::INFO::[downloader:657] Thread 32@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:45,954::INFO::[downloader:657] Thread 7@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:46,319::INFO::[downloader:657] Thread 22@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:47,029::INFO::[downloader:657] Thread 33@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:47,303::INFO::[downloader:657] Thread 21@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:47,487::INFO::[downloader:657] Thread 39@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:47,628::INFO::[downloader:657] Thread 9@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:47,674::INFO::[downloader:657] Thread 40@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:48,605::INFO::[downloader:657] Thread 38@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:49,358::INFO::[downloader:657] Thread 31@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:49,967::INFO::[downloader:657] Thread 42@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:50,927::INFO::[downloader:657] Thread 36@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:51,055::INFO::[downloader:657] Thread 5@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:51,257::INFO::[downloader:657] Thread 4@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:51,500::INFO::[downloader:657] Thread 24@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:51,687::INFO::[downloader:657] Thread 37@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:51,881::INFO::[downloader:657] Thread 20@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:53,012::INFO::[downloader:657] Thread 2@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:53,101::INFO::[downloader:657] Thread 13@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:53,950::INFO::[downloader:657] Thread 18@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:54,062::INFO::[downloader:657] Thread 25@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:54,240::INFO::[downloader:657] Thread 15@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:55,740::INFO::[downloader:657] Thread 45@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:56,163::INFO::[downloader:657] Thread 19@europe-ssl.newsdemon.com:80: server closed connection
2013-01-07 10:59:56,509::INFO::[downloader:657] Thread 12@europe-ssl.newsdemon.com:80: server closed connection

Can someone confirm this is a related issue and also is expected solved in the mentioned new release?

Yes, just upgrade.

Ok. Thanks!

I had already upgraded, but got it solved by changing the local IP address in the settings from 127.0.0.1 to 0.0.0.0.

usk78dk wrote: I had already upgraded, but got it solved by changing the local IP address in the settings from 127.0.0.1 to 0.0.0.0.

What kind of problem did you have?
The bug in 0.7.8 had nothing to do with the host address.

The one I posted above.