Page 1 of 1

CRC Error on job, then DELAYING, then stopped.

Posted: January 6th, 2013, 10:03 am
by NickTO
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 [email protected]
2013-01-06 08:29:16,582::DEBUG::[decoder:100] Decoding [email protected]
2013-01-06 08:29:16,602::DEBUG::[decoder:100] Decoding [email protected]
2013-01-06 08:29:16,622::DEBUG::[decoder:100] Decoding [email protected]
2013-01-06 08:29:16,642::DEBUG::[decoder:100] Decoding [email protected]
2013-01-06 08:29:16,653::DEBUG::[decoder:100] Decoding [email protected]
2013-01-06 08:29:16,655::INFO::[decoder:118] CRC Error in [email protected] (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

Re: CRC Error on job, then DELAYING, then stopped.

Posted: January 6th, 2013, 11:06 am
by Fat Rastus
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.

Re: CRC Error on job, then DELAYING, then stopped.

Posted: January 6th, 2013, 1:24 pm
by shypike
Bug in decoder confirmed.
There will be a new release asap.

Re: CRC Error on job, then DELAYING, then stopped.

Posted: January 6th, 2013, 2:20 pm
by NickTO
Thanks for your help! Much appreciated.

Re: CRC Error on job, then DELAYING, then stopped.

Posted: January 6th, 2013, 3:51 pm
by NickTO
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 [email protected]
2013-01-06 15:49:47,562::INFO::[decoder:119] CRC Error in [email protected] (EDFC771B -> 2F33AD75)
2013-01-06 15:49:47,579::DEBUG::[decoder:101] Decoding [email protected]
2013-01-06 15:49:47,599::DEBUG::[decoder:101] Decoding [email protected]
2013-01-06 15:49:47,619::DEBUG::[decoder:101] Decoding [email protected]
2013-01-06 15:49:47,639::DEBUG::[decoder:101] Decoding [email protected]
2013-01-06 15:49:47,659::DEBUG::[decoder:101] Decoding [email protected]
2013-01-06 15:49:47,674::DEBUG::[decoder:101] Decoding [email protected]
2013-01-06 15:49:47,684::DEBUG::[decoder:101] Decoding [email protected]
2013-01-06 15:49:47,794::DEBUG::[decoder:101] Decoding [email protected]

Cheers

Re: CRC Error on job, then DELAYING, then stopped.

Posted: January 7th, 2013, 5:04 am
by usk78dk
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 [email protected] (C40BA954 -> C4EC0FF4)
2013-01-07 10:59:27,444::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:35,607::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:36,186::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:39,298::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:39,308::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:39,717::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:40,114::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:40,493::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:40,668::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:41,588::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:41,642::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:41,763::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:42,480::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:43,042::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:43,480::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:43,788::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:44,397::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:44,605::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:45,638::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:45,954::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:46,319::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:47,029::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:47,303::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:47,487::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:47,628::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:47,674::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:48,605::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:49,358::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:49,967::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:50,927::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:51,055::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:51,257::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:51,500::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:51,687::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:51,881::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:53,012::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:53,101::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:53,950::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:54,062::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:54,240::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:55,740::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:56,163::INFO::[downloader:657] Thread [email protected]:80: server closed connection
2013-01-07 10:59:56,509::INFO::[downloader:657] Thread [email protected]:80: server closed connection

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

Re: CRC Error on job, then DELAYING, then stopped.

Posted: January 7th, 2013, 6:14 am
by shypike
Yes, just upgrade.

Re: CRC Error on job, then DELAYING, then stopped.

Posted: January 8th, 2013, 7:24 am
by usk78dk
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.

Re: CRC Error on job, then DELAYING, then stopped.

Posted: January 8th, 2013, 11:14 am
by shypike
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.

Re: CRC Error on job, then DELAYING, then stopped.

Posted: January 14th, 2013, 5:05 pm
by usk78dk
The one I posted above.