SABnzbd Forums

switch wrote: Either of you using EXT4?

Edit: Also are you using SSL for usenet connections?

No and No.

I am using EXT 4
after seeing this thread over at the ubuntu forums I'm going to swicth back to EXT3
http://ubuntuforums.org/showthread.php?t=1135055
It very well looks like this could be the issue.

sander wrote:

switch wrote: Either of you using EXT4?

Edit: Also are you using SSL for usenet connections?

No and No.

Sorry, didn't see the second page of this thread when I posted...
Maybe EXT4 isn't the issue then ... I really don't think its SAB I want to lean more towards Ubuntu being the cause of the problem. 

Jaunty_Joke wrote:

sander wrote:

switch wrote: Either of you using EXT4?

Edit: Also are you using SSL for usenet connections?

No and No.

Sorry, didn't see the second page of this thread when I posted...
Maybe EXT4 isn't the issue then ... I really don't think its SAB I want to lean more towards Ubuntu being the cause of the problem. 

Sander is using EXT3 and NOT having CRC errors, you are using EXT4 and have CRC errors.

However after posting that I noticed you are getting CRC errors at the decoding stage, which should not be affected by the filesystem.

Errors at the decoding stage are usually either:
1) Memory errors - Data is being lost or corrupted in memory
2) Socket errors - Data isn't being read correctly from the open socket
3) Newsgroup error - The usenet provider is not sending the correct data

So I'm not sure what to think.

Sorry, I really have to start reading more before I post ...

I've pretty much eliminated the hardware component from this as I've installed on two different systems using different RAM and different NICs.
I've also eliminated the provider error because I've run the same NZB on a "known working" version of ubuntu 8.10 that I've been using for the past 6 months.

I really think this is going to be an EXT4 issue, I have done several "in place" upgrades to several servers at work and have not seen any of the freezing or hanging issues potentially because they have remained on EXT3 file systems?

I know its grasping at straws but it seems to be somewhat consistent...

Crap, I just installed Linux for the first time this weekend (ext4) and looking to install sabnzbd as my first non-point-and-click application install. Is it doomed to fail?  Have you tried previous versions of sabnzbd?

Jaunty_Joke wrote: I've also eliminated the provider error because I've run the same NZB on a "known working" version of ubuntu 8.10 that I've been using for the past 6 months.

... with what result?

Has anybody checked my hypothesis that a missing article is handled differently by SAB on Ubuntu 9.04 and/or by python 2.6, than by older versions of Ubuntu and/or python?

sander wrote:

Jaunty_Joke wrote: I've also eliminated the provider error because I've run the same NZB on a "known working" version of ubuntu 8.10 that I've been using for the past 6 months.

... with what result?

Has anybody checked my hypothesis that a missing article is handled differently by SAB on Ubuntu 9.04 and/or by python 2.6, than by older versions of Ubuntu and/or python?

When I downloaded the same NZB on my known working system (Ubuntu 8.10 running latest SAB) it worked without any errors or missing articles.

Jaunty_Joke wrote:
When I downloaded the same NZB on my known working system (Ubuntu 8.10 running latest SAB) it worked without any errors or missing articles.

To check the ext4-hypothesis: can you mount the ext4 partition as ext3? According to http://en.wikipedia.org/wiki/Ext4#Backw ... patibility this can be possible.

After mounting as ext3, re-download the NZB and see what happens...

sander wrote:

Jaunty_Joke wrote:
When I downloaded the same NZB on my known working system (Ubuntu 8.10 running latest SAB) it worked without any errors or missing articles.

To check the ext4-hypothesis: can you mount the ext4 partition as ext3? According to http://en.wikipedia.org/wiki/Ext4#Backw ... patibility this can be possible.

After mounting as ext3, re-download the NZB and see what happens...

Was going to do a complete re-install anyways so I'll reformat as EXT3 and try again.

I'll let you know what I find tonight.

Well, came home and re-installed ubuntu for about the 20th time this time using EXT3 instead of EXT4 and so far I have downloaded over 4GB with NO Errors.

I was seeing system problems before with the system hanging/freezing randomly and that problem also seems to have been fixed as well with the filesystem change. 

So I would suggest not using EXT4 at least until things have stabilized.

It seems using ext4 is a bit like playing russian roulette right now. Given that complaints about crc errors in sabnzbd started appearing after jaunty came out which just happens to be the only ubuntu release to date that supports ext4, and switching to ext3 fixed the problem for Jaunty_Joke (while never causing any for Sander) it seems this is the root cause.

Virtualshock, are you on ext4 too?

jcfp wrote: It seems using ext4 is a bit like playing russian roulette right now. Given that complaints about crc errors in sabnzbd started appearing after jaunty came out which just happens to be the only ubuntu release to date that supports ext4, and switching to ext3 fixed the problem for Jaunty_Joke (while never causing any for Sander) it seems this is the root cause.

Virtualshock, are you on ext4 too?

This makes me wonder: have or have not Ted T'so's ext4-patches for 2.6.30 been backported to Jaunty's 2.6.29-kernel? I can't find anything on that on http://www.ubuntu.com/getubuntu/releasenotes/904

FWIW: Ted T'so's initial statement was that the *applications* should behave differently, and then, after having said that, he has created patches for ext4. So, have those patches been integrated into Jaunty ... ?

sander wrote:So, have those patches been integrated into Jaunty ... ?

Probably not, the bug is still marked "in progress" and just a few days ago devs were still asking for people to provide certain filesystem data in order to reliably reproduce the problem.

Sorry all, I have not been checking the thread lately.  I am using ext3 on an AMD 64 x2 6000, 4 GB ram, a new 1TB hard drive.  I installed the AMD64 version of Jaunty.

I was previously using SABnzbd 0.4.4 on Ubuntu 8.04.  The only reason that I switched was my hard drive crashed and I replaced it.  Jaunty so far has been the biggest pain in the ass since i first started using Ubuntu at 6.06.  In addition to my SABnzbd problems which I have never had before, my SPDIF pass through audio is a train wreck.  That is another story.

No SSL on the newsgroup connections.  I am using Forte, whom I have been using for over 4 years, reliably.  I don't know if it is a SABnzbd problem but it is definitely due to my upgrade.  I was using my old system just a few days ago with no issues.  I got my new drive in 1 day and had it put in the system and did the Jaunty installation.

Edit : I am also trying out your suggestion Sander of the other newsgroup server.  I am currently downloading one of the problem files from it with my other connections removed.  I might add that my one successful download was just 100MB most of the stuff I download is between 4 and 7 GB.  Could it be that for me it is large files causing this?  Sander did download of my problem files fine on his machine, though.