Thread: Problem cross-seeding with rTorrent

I am trying to cross-seed a scene album that I downloaded from FYT to What.CD. This usually works without any trouble. I download albums for cross-seeding with Deluge and then add the same torrents in rTorrent, usually works flawlessly. Now I get the following message in rTorrent:

Storage error: [hash checker was unable to map chunk: permission denied]

The folder is the same and the original torrent in Deluge has been hash checked.

Any ideas?

At face value, it's a permissions issue. rTorrent can't access the file.. e.g. no permission, read only or corrupt.
What OS are you using?

I have Ubuntu 10.04 LTS installed on my seedbox. There's no point to try seeding the album in What anymore since probably nobody is leeching but I'd still like to know how to fix this issue in the future. So, you mean I can maybe change the permissions on the files somehow?

I understand that the torrent was time sensitive.

The error message is telling us that rTorrent was unable to copy the file because it "didn't have permission" Linux permissions are a common source of grief.. as you are seeing at the moment. Usually this is caused by something you did previously e.g. logged in as root to do some maintenance. a typo when you went to chmod a file or create a new directory, etc.

If you simply want an easy workaround for the future.. it would be giving all applications permission to write in that directory as in the example below. Make sure that you change the path to point to the directory on your seedbox:

sudo chmod -R 777 /var/www/torrents/

.

I did sudo chmod 777 and I still get the error when I try to add the same torrent in rTorrent. I can't seem to be able to use the -r option with 777 in the same time because I get
chmod: cannot access `777': No such file or directory

Sounds like a syntax error.. probably a typo.
Can you copy + paste exactly what you typed when you get this error?

.

Here it is:


$ sudo chmod -r 777 /var/www/ext
chmod: cannot access `777': No such file or directory

Hey LateralNoise,

Do you use EvoBoxes? Have you made any changes to the rtorrent.rc file? The error is usually caused by that. If you have made changes, PM me the contents of your rtorrent.rc file and I'll try to find what is causing the problem.

What is the path to your download folder?

Try it again with a capital "R" and see if it works better. Ubuntu commands are case sensitive and r vs R mean different things i.e. read vs. recursive..

So..

$ sudo chmod -R 777 /var/www/ext/

.