CRC Error on job, then DELAYING, then stopped.
Posted: January 6th, 2013, 10:03 am
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
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