SABnzbd Forums

Dear all,

I´m currently having the following problem.

Whenenver I move or upload a *.nzb file from my local Download folder at my Nexus 7 tablet to the "dirscan" folder at my Syno DS 213 NAS the Sabnzb Download won´t start.
All I get is a Warning message ("Incomplete NZB file ....") which is visible when I start Sabnzb on my Notebook.

Strange thing is that it works via the Notebook with Chrome browser and the Sabconnect add-on. If I use binseach and press the "Send to Sabnzbd" icon then the download starts in Sabnzbd.
But this is not my preferred way ;-)

It worked fine via the tablet until yesterday and I´m not aware that I changed anything in the configuration.

Here´s some more information about my SW & HW:

NAS: Synology DS 213 (DSM 5.0-4482) => Sabnzb+ 6.9 (v1.4) installed
Tablet: Nexus 7 (Android 4.4.3) => Sabcontrol (v3.0.2) installed; "DS file" is used to move/upload the files from the tablet to the NAS
Notebook with Win 7 => SAbnzbd v0.7.17 installed

So any help what´s this warning message is about and how this can be solved is highly appreciated.

Thanks in advance.
Cheers,

marflao

It looks that the uploading of the NZB is so slow, that SABnzbd thinks the file is complete while it isn't yet.
We have some precautions for this, but maybe not enough for this specific situation.

Thanks for your response, shypike.

Could you pls elaborate what you mean with "we have some precautions with it"?
Is there anything I can do to overcome this situation? Maybe change some settings??

Any suggestions would be great.

Cheers,
marflao

SABnzbd checks whether size and date/time stamp of a file is stable for 3 seconds.
Only then will it process a file.
from what I read, I conclude that somehow the tablet takes more time to write the NZB to the NAS.
At least it seems to have odd pauses in writing.
This is all informed speculation of course.

Hmmm...could it be that the problem is related to the file manager app (DS file)? Would an alternative app solve this issue??

If the answer is "yes", any recommendation which one I should use?

Thanks in advance.

Sorry, cannot answer that question.

OK.

From your point of view what could be a further step to narrow the problem? Is there anything in particular what I can do?
Have similiar warnings occured (and be solved) in the past?

Cheers,
marflao

I have/had a similair problem. Solved it by uploading the .nzb to a different dir on the SAB machine, and then move the .nzb to the watched folder.

The only thing I can think of is to lower the readout frequency.
Something like 10 minutes or so.
It means that it will take longer for SABnzbd to pickup your job,
unless you go to the web interface and select "Read out watched folder now".

BTW: have you checked whether the NZB files are actually complete when they're in the NAS folder?
They should end like this: </nzb>

Well.... Very strange behaviour indeed.

@wimpie1: thanks to your input, too.
@shypike: yep... files have the correct *.nzb endings.

I just tried it via ES Explorer and it worked. Once the nzb file was moved from the local DL folder to the Dirscan folder on my NAS the download started.
So I guess that there is an issue with the Syno "DS file" app (I remember that they provided a new version a week ago so maybe my issues are related to their latest version).

Anyway.... thanks again for your support. I highly appreciated it.

Cheers,
marflao

Hmm...seems my yesterday´s post isn´t shown therefore I post it again.

Just wanted to keep you updated that Synology provided an update to their "DS file" app for Android devices yesterday.
Version 4.1.1. includes also this:
"Fixed an issue where the file size of uploaded items would be bigger than the original, or appear corrupted".

Now the download starts again once the file is moved from the local DL folder to the Dirscan folder on my NAS.

Problem solved, thread can be closed ;-)

Thanks again for all your support.

Cheers,
marflao