0.6.0 BETA2 - Every file being downloaded to a new folder

[young-einstein]

Hi guys,

I've just upgraded to the latest 0.6.0 beta a few days ago, and I've noticed a couple of jobs doing weird things.  It's not all jobs that do it, but it has happened to me twice now since upgrading.

Basically when it's downloading a job the first file downloaded will go to .../incomplete/, which is exactly what you'd expect.  However, the second file doesn't get saved into that folder - like it should - and it ends up in a new folder .../incomplete/.1.

And so it continues on and on until I've got [potentially] 100's of folders, each with just a single file in them.

Of course once the download completes it results in an error because all of the files [bar one] aren't where it's expecting them to be.

The files seem to be fine though.  If I move them all back into a single folder and then manually process/extract them, then everything works fine.

I also had a quick look at the logs, and I don't appear to get any warnings/errors in the logs while it's happening either.

Any ideas / suggestions?

[shypike]

You mention nothing about your OS.
I would need to have a debug log file to analyse this.
Try running with debug level for a while and when it happens again
send in the compelete logging to bugs at sabnzbd.org (and refer to this post).
(Status page, first tab).

[young-einstein]

You mention nothing about your OS.

Ubuntu 10.10 [x86].  SABnzbd has been installed [and updated] using jcfp's PPA.

I would need to have a debug log file to analyse this.
Try running with debug level for a while and when it happens again
send in the compelete logging to bugs at sabnzbd.org (and refer to this post).
(Status page, first tab).

Thanks ... will do!

[shypike]

Bug confirmed. See "Known Problems" at the top of this board.

[young-einstein]

Bug confirmed. See "Known Problems" at the top of this board.

Thanks shypike

Is that just related to the warning about clearing the download queue before upgrading?

Otherwise, I don't actually see anything in that thread which would relate to this bug?

[shypike]

Yes, sorry. Starting with a fresh queue is the only solution for now.
Any unstarted job inherited from an 0.5.6 queue has this bad behaviour.

[young-einstein]

Hmmmm ... that's a bit of a pain, because my current queue is pretty massive [over 1500 jobs in it at the moment].

Am I correct in thinking that if I setup a new machine which is still running 0.5.6, that I should still be able to migrate my queue back to it again?

I've migrated between servers a couple of times before, just by copying the all the sabnzbd cache/incomplete folders, and that's always worked fine.

I know that 0.6.0 uses a different method for storing cache files [IE individual folders for each job, instead of a central folder], but if I cleared off all jobs which have been added since the 0.6.0 upgrade, is there any reason why I shouldn't be able to migrate my existing queue back to a server running 0.5.6?

[shypike]

You might want to wait for tomorrow.
New Beta, without this problem.

[young-einstein]

Excellent ... that's even better!  I'll just hang out and wait for the new release then.

Thanks a lot for your help!

--David

[shypike]

Beta3 is out.
Try to download a few queue entries.
It should work now.

[young-einstein]

Beta3 is out.
Try to download a few queue entries.
It should work now.

Excellent ... it does indeed look like it's fixed again.

Loving your good work shypike ... keep it up!