Details tab: Status: "Access Denied"

[coli1875]

Hi all,

This might be a dumb question but here is it anyway... I'm using Deluge 1.1.9 and I'm getting an "Access is denied" error on the Status field at the Details tab.

I guess this is an error from the tracker (demonoid.com) since it happens when I start downloading the torrent and after the next announce which happens after 60 min after starting Deluge.

My ratio with the Demonoid tracker is around 1.5 which is not stellar but I guess it's ok.

Is Demonoid tracker blocking me because of the share ratio or is this something else related specifically to Deluge ??. How can I find more details about the error ??

Thanks.

[johnnyg]

It sounds like you either don't have read/write access to the folder you're downloading to or that Deluge isn't on demonoid's whitelist.

[coli1875]

It sounds like you either don't have read/write access to the folder you're downloading to or that Deluge isn't on demonoid's whitelist.

I don't think it's a writing problem because when I restart Deluge it works for 60 minutes, ie, by doing that I have 50% of the torrent I'm downloading already so it doesn't seem to be a write problem on the folder.

About demonoid whitelist, how do I know if it's that ??, all I found on Demonoid's FAQ was:

"Why am I getting "Problem Connecting to tracker - [ errno http error ]403 'Forbidden (client banned)" error?
The tracker for the torrent has banned the client that you are using try a different one."

Is there a way in Deluge to determine what is actually it's getting from the tracker ??

Thanks.

[coli1875]

Well, I changed the tracker and I'm still getting the same error after a while so I really don't know if the problem is something that Deluge can't do or if it's something related to the trackers...

Is there a way to expand this error somehow and really determine what's going on ??

[coli1875]

I found what the problem was. I first started the Deluge daemon with logging and debugging enable. I then looked for the error and found out it was a disk error that was preventing deluge from witting to the disk.

I guess it would have been easier if the full message was simply put on the status field in Deluge's regular UI instead of having to browse through the log. Maybe in a future release....

Anyway, I found what the problem was and solve it.