SABnzbd Forums

virtualshock wrote: Jaunty so far has been the biggest pain in the ass since i first started using Ubuntu at 6.06. 

Haha. "Me too"! Using Ubuntu since 5.04 (after using Mandrake for a lot of years) ...

Jaunty feels like one step forward (some eye candy with wifi and volumoe pop up messages), and three steps back (a lot of bugs: usb-creator's persistence not working anymore, totem not working automagically with asx, a lot of new features have bugs like the ext4 problems).

I see little reason to upgrade to Jaunty 9.04.

I was a long time FreeBSD user so I know the pain of trying the latest and greatest on a Unix variant.  Package management has come a long way.  I was really looking forward to Jaunty but there is no doubt about it, they got it wrong this time.  People are always bitching wanting all the latest features but this is what happens when you give in to that.

Well, looks like using the other usenet provider did not work.  Got the same exact error.
Should I dump Jaunty and go back to 8.04, maybe 8.10? 

Some Bad news...
I have now installed 8.10 on my server with Sab and I am seeing the same CRC errors in articles? This error shows up in my "Warnings" section and as long as there aren't too many errors the file can be repaired.

Now for the really bad news, I get the same exact  (article and CRC numbers at the end) error if I download that same file on my old "thought it was working perfectly" system

So does this mean that the server at giganews is causing the problem? or is it a problem with SAB?

I dunno what to do anymore?

Anyone have any ideas what could be causing this?

Can you please send a sample nzb to [email protected] for me to try on multiple providers.

My suspicion is not to blame giganews, but http://www.octanews.com/ who were the provider the uploader used, and who replicated the files to other providers.

virtualshock, do you also get CRC errors listed in the Warnings page? Or just on the history page.

That would make a lot of sense ... I have seen that name a lot in the errors I was seeing. 
I've sent in the NZB I was downloading when I got that last warning, the file did eventually complete and was able to be repaired.

Thanks again!

I hate to say this, but I have now experienced a fatal CRC problem too:

On Jaunty, with SAB 0.4.10 started with ./SABnzbd.py and thus python 2.6, I tried several times to download a certain NZB (saving it on a NTFS partition, FWIW): it failed each time with a lot of CRC errors. FWIW: it seemed like an avalanche of CRC errors: the first part went OK, after that the amount of CRC errors turned enormous.

Then, the fourth download succeeded, with only a few CRC errors. The only 'difference' was that this time I started SAB with "python SABnzbd.py", but that still starts python2.6 (not python2.5) and is thus no real difference. One more difference: the download was quite slow: it took 6 hours instead of 45 minutes to download the NZB.

Newsserver is eweka, post was 112 days old (well below eweka's retention)

Strange.

I've noticed some strange problems since upgrading to jaunty too. I'm not using ext4 either.
what's happening to me is the web ui seems to hang at certain spots. shutdown for example, NEVER works for me. I have let it sit at the 'shutting down...' screen for 5 minutes and sure enough its still running, and downloading.. also in the configuration section, every time I click save, the same thing happens, it hangs for a REALLY long time, and when I refresh, sometimes my changes have been saved, sometimes they haven't.

Use python 2.5 instead of python 2.6

switch wrote: Use python 2.5 instead of python 2.6

Thanks switch,
I Actually just did that after reading a little further through the forums, and its working great.

virtualshock wrote: I was a long time FreeBSD user so I know the pain of trying the latest and greatest on a Unix variant.  Package management has come a long way.  I was really looking forward to Jaunty but there is no doubt about it, they got it wrong this time.  People are always bitching wanting all the latest features but this is what happens when you give in to that.

Well, looks like using the other usenet provider did not work.   Got the same exact error.

Code: Select all

2009-04-30 00:57:30,864 WARNING [decoder] <Article: article=part79of131.ZauolSl2encp2W1D&[email protected], bytes=397008, partnum=79, art_id=None> => missing from all servers, discarding
2009-04-30 00:58:09,634 WARNING [assembler] <Article: article=part79of131.ZauolSl2encp2W1D&[email protected], bytes=397008, partnum=79, art_id=None> missing
2009-04-30 01:01:09,245 ERROR [newswrapper] Failed to connect: (111, 'Connection refused') [email protected]:119
2009-04-30 01:01:09,390 ERROR [newswrapper] Failed to connect: (111, 'Connection refused') [email protected]:119
2009-04-30 01:01:09,535 ERROR [newswrapper] Failed to connect: (111, 'Connection refused') [email protected]:119
2009-04-30 01:01:09,680 ERROR [newswrapper] Failed to connect: (111, 'Connection refused') [email protected]:119
2009-04-30 01:01:09,826 ERROR [newswrapper] Failed to connect: (111, 'Connection refused') [email protected]:119
2009-04-30 01:01:09,977 ERROR [newswrapper] Failed to connect: (111, 'Connection refused') [email protected]:119
2009-04-30 01:01:15,131 ERROR [newswrapper] Failed to connect: (111, 'Connection refused') [email protected]:119
2009-04-30 01:01:15,277 ERROR [newswrapper] Failed to connect: (111, 'Connection refused') [email protected]:119
2009-04-30 01:01:15,421 ERROR [newswrapper] Failed to connect: (111, 'Connection refused') [email protected]:119
2009-04-30 01:50:30,583 WARNING [newsunpack] ERROR: CRC failed in Blah.720p.BluRay.DTS.x264-CtrlHD.mkv"

Should I dump Jaunty and go back to 8.04, maybe 8.10? 

Maybe instead of crying about this, you could just do a MemTest on your RAM.  It would save all of us a lot of hassle listening to you cry about it.  It's your memory man!!!  LOL!