Solved Download Station Error Status

[lehm01]

Hi all

I've seen numerous threads with some similarities to this, however, they are all extremely outdated and provide no solution.

Issue:

I have a two NAS setup, both running up to date DSM 6.2.1; NAS1 acts as Download Station and NAS2 as storage. I have the two linked via NFS so that the files are able to transfer from NAS1 to NAS2.

The programs on NAS1 are set to pull and load files into DS, but when the download completes and starts an integrity check, the status of the download returns 'error'. I've confirmed that the files themselves have in fact been downloaded and can be located within the appropriate folder on NAS2, but because of the error, post-processing by the programs will not work.

Given that the files can be located within the download directory, I don't imagine there being a path or permissions mix-up.

Does anyone have experience with this issue and can provide a solution?

 

[lehm01]

To add to this, I’ve experimented with this setup using the Transmission client, which works wonderfully without issue.

Perhaps this boils down to a DS config bug?

 

[Rusty]

Odd, considering that DS is Transmission with a different "skin". Not using it in this scenario, so really can't help on the matter.

 

[akahan]

I do, successfully, exactly what you are attempting to do. The only difference is that I link the destination folder (on the storage NAS) to the NAS running download station using CIFS (File Station / Tools / Mount Remote Folder).

 

[lehm01]

I do, successfully, exactly what you are attempting to do. The only difference is that I link the destination folder (on the storage NAS) to the NAS running download station using CIFS (File Station / Tools / Mount Remote Folder).

Taking this as a suggestion, I mounted via CIFS and everything works great! Thank you

It's my understanding that these protocols are very similar, but to say what the difference is in this situation is beyond me.

 

[akahan]

Yeah, I have no idea why one would work and the other wouldn't, but I'm glad to hear this fixed it for you!

 

[akahan]

Incidentally, I noticed some behavior that seems odd with this setup; I wonder if your experience is the same. Once a task has completed, and the files have been downloaded to the NAS running Download Station, and then "transferred" to the NAS being used as a repository, the downloaded files remain on the NAS running Download Station (taking up space...) until the task is removed from the task list. I would have expected that once the files were transferred to their final destination, the temporary copies on the downloading NAS would be deleted, but that appears not to be the case. Until I figured out that this was what was going on, I was mystified as to why I was losing storage space on the downloading NAS, particularly as the downloaded files are stored in some system area not visible to File Station.

I'd be interested to know if you're seeing the same behavior.

 

[lehm01]

I've actually had zero issues so far with this setup. Once the task completes in Download Station, the programs that handle post-processing transfer the files over to the respective folder flawlessly, then delete the downloaded folder and wipe the task.

I'm not sure what you use for post-processing of tasks but from what you've described, it might be a kink on that end.

 

[akahan]

The difference may be that you’re wiping the task immediately after completing downloading and I’m keeping the task seeding?