permission denied

[aykcel]

Binary package hint: transmission

when I am trying to download torrent, it is starting to downloan but after few second it stops by itslef. and error: permission denied.

ProblemType: Bug
Architecture: amd64
CheckboxSubmission: c9a290750d3438d0e84be85df60996c5
CheckboxSystem: 3e53d3ea5811723345f19eff5070f9ab
Date: Mon Mar 1 19:51:06 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/transmission
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: transmission-gtk 1.75-0ubuntu2.2
ProcEnviron:
 LANGUAGE=tr_TR.UTF-8
 PATH=(custom, no user)
 LANG=tr_TR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: transmission
Uname: Linux 2.6.31-19-generic x86_64

[Charles Kerr (charlesk)]

Sounds like you're trying to download into a folder that you don't have write permission to?

[aykcel (aykcel)]

 Actually I am starting to download than, its stop itself. An error
accured it says : permission denied. When I start to download in XP by
bittorent, I have no problem. I couldnt solve that.

Pzt, 2010-03-01 tarihinde 17:58 +0000 saatinde, charles yazdı:
> Sounds like you're trying to download into a folder that you don't have
> write permission to?
>
> ** Changed in: transmission (Ubuntu)
> Status: New => Incomplete
>

[Charles Kerr (charlesk)]

That doesn't really answer my question? :)

[aykcel (aykcel)]

  I hope it will answer your question

Çrş, 2010-03-03 tarihinde 02:10 +0000 saatinde, charles yazdı:
> That doesn't really answer my question? :)
>

[Chris Coulson (chrisccoulson)]

Is that removable media you're downloading too? Can you write anything at all to this media from something other than transmission after you see this error, or do you have to unmount it first? You will get a permission denied error if the filesystem gets remounted read-only due to errors.

[Charles Kerr (charlesk)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Charles Kerr (charlesk)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[jvin248 (jvin248)]

I've had the same problem. Fresh install of Ubuntu 10.04 server, standard transmission install from repositories.
I followed this writeup:
http://1000umbrellas.com/2010/04/21/transmission-install-on-ubuntu-10-04-server-lucid
including using the same settings.json file

I can write files in the two directories targeted in the .json setup.
I've changed all the directories specified in .json to 766 permission level.

Using the web gui I can upload a target torrent file and it starts to download the torrent data but as soon as it tries to save to disk it gives me the permissions error.

[jvin248 (jvin248)]

missed adding, the directories involved are on the main sda partition. While the plan will be to use a second drive, I wanted to minimize install variables while getting this set up.

Is there a command to list which version of Transmission?

.. in trying to find version# I found the -d command, here is what Transmission thinks it should be using vs what the .json file is telling it show differences in directories I'll have to test:

transmission-daemon -d
{
    "alt-speed-down": 50,
    "alt-speed-enabled": false,
    "alt-speed-time-begin": 540,
    "alt-speed-time-day": 127,
    "alt-speed-time-enabled": false,
    "alt-speed-time-end": 1020,
    "alt-speed-up": 50,
    "bind-address-ipv4": "0.0.0.0",
    "bind-address-ipv6": "::",
    "blocklist-enabled": false,
    "dht-enabled": true,
    "download-dir": "\/home\/nimda\/Downloads",
    "encryption": 1,
    "incomplete-dir": "\/home\/nimda\/.config\/transmission-daemon\/Incomplete",
    "incomplete-dir-enabled": false,
    "lazy-bitfield-enabled": true,
    "message-level": 2,
    "open-file-limit": 32,
    "peer-limit-global": 240,
    "peer-limit-per-torrent": 60,
    "peer-port": 51413,
    "peer-port-random-high": 65535,
    "peer-port-random-low": 49152,
    "peer-port-random-on-start": false,
    "peer-socket-tos": 0,
    "pex-enabled": true,
    "port-forwarding-enabled": true,
    "preallocation": 1,
    "proxy": "",
    "proxy-auth-enabled": false,
    "proxy-auth-password": "",
    "proxy-auth-username": "",
    "proxy-enabled": false,
    "proxy-port": 80,
    "proxy-type": 0,
    "ratio-limit": 2.0000,
    "ratio-limit-enabled": false,
    "rename-partial-files": true,
    "rpc-authentication-required": false,
    "rpc-bind-address": "0.0.0.0",
    "rpc-enabled": false,
    "rpc-password": "",
    "rpc-port": 9091,
    "rpc-username": "",
    "rpc-whitelist": "127.0.0.1",
    "rpc-whitelist-enabled": true,
    "speed-limit-down": 100,
    "speed-limit-down-enabled": false,
    "speed-limit-up": 100,
    "speed-limit-up-enabled": false,
    "umask": 18,
    "upload-slots-per-torrent": 14
}

While this is what it should be using (.json file):
{
    "alt-speed-down": 500,
    "alt-speed-enabled": true,
    "alt-speed-time-begin": 480,
    "alt-speed-time-day": 127,
    "alt-speed-time-enabled": true,
    "alt-speed-time-end": 0,
    "alt-speed-up": 10,
    "bind-address-ipv4": "0.0.0.0",
    "bind-address-ipv6": "::",
    "blocklist-enabled": false,
    "dht-enabled": true,
    "download-dir": "\/home\/nimda\/dl\/torrent",
    "download-limit": 1000,
    "download-limit-enabled": 0,
    "encryption": 2,
    "incomplete-dir": "\/var\/lib\/transmission-daemon\/info\/Incomplete",
    "incomplete-dir-enabled": false,
    "lazy-bitfield-enabled": true,
    "max-peers-global": 200,
    "message-level": 2,
    "open-file-limit": 32,
    "peer-limit-global": 240,
    "peer-limit-per-torrent": 60,
    "peer-port": 20657,
    "peer-port-random-high": 20500,
    "peer-port-random-low": 20599,
    "peer-port-random-on-start": true,
    "peer-socket-tos": 0,
    "pex-enabled": true,
    "port-forwarding-enabled": false,
    "preallocation":...

[Krzysztof Klimonda (kklimonda)]

@jvin248: if you are editing /etc/transmission-daemon/settings.json can you check the content of /var/lib/transmission-daemon/info/settings.json and see if it matches the dumped settings from transmission-daemon?

Because of the bug 571097 changes made to /etc/transmission-daemon/settings.json aren't honored.

[biebel (badk666)]

Ran into the same problem here.
I have some additional info: the permission problem only occurs when transmission-daemon gets started with the init.d script ie. on boot or (re)starting with /etc/init.d/transmission-daemon (re)start. When I start it from the cli with transmission-daemon -f everything works as it should.

[biebel (badk666)]

It was working fine after I upgraded my server from 9.10 to 10.04 at first, but after doing the updates a few days back I ran into this problem.

I still had my old transmission-daemon init.d script so I compared it to the one that is currently being used. I noticed that my old custom one had username=myusername and the new one has name=transmission-daemon and user=debian-transmission.
I tried setting name=myusername, but that broke it. The page wouldn't load. When I put the old script instead of the new one I still had the permission problem.

As a temporary workaround I changed the owner of the download folder to debian-transmission using sudo chmod -R debian-transmission:debian-transmission /home/shared/downloadfolder/

[jvin248 (jvin248)]

I restarted with a fresh install to ensure it's all as clean as possible. T-D seems to run with a configuration from somewhere other than the two noted source files.

this is what transmission-daemon is running with:
$ transmission-daemon -d

{
    "alt-speed-down": 50,
    "alt-speed-enabled": false,
    "alt-speed-time-begin": 540,
    "alt-speed-time-day": 127,
    "alt-speed-time-enabled": false,
    "alt-speed-time-end": 1020,
    "alt-speed-up": 50,
    "bind-address-ipv4": "0.0.0.0",
    "bind-address-ipv6": "::",
    "blocklist-enabled": false,
    "dht-enabled": true,
    "download-dir": "\/home\/nimda\/Downloads",
    "encryption": 1,
    "incomplete-dir": "\/home\/nimda\/.config\/transmission-daemon\/Incomplete",
    "incomplete-dir-enabled": false,
    "lazy-bitfield-enabled": true,
    "message-level": 2,
    "open-file-limit": 32,
    "peer-limit-global": 240,
    "peer-limit-per-torrent": 60,
    "peer-port": 51413,
    "peer-port-random-high": 65535,
    "peer-port-random-low": 49152,
    "peer-port-random-on-start": false,
    "peer-socket-tos": 0,
    "pex-enabled": true,
    "port-forwarding-enabled": true,
    "preallocation": 1,
    "proxy": "",
    "proxy-auth-enabled": false,
    "proxy-auth-password": "",
    "proxy-auth-username": "",
    "proxy-enabled": false,
    "proxy-port": 80,
    "proxy-type": 0,
    "ratio-limit": 2.0000,
    "ratio-limit-enabled": false,
    "rename-partial-files": true,
    "rpc-authentication-required": false,
    "rpc-bind-address": "0.0.0.0",
    "rpc-enabled": false,
    "rpc-password": "",
    "rpc-port": 9091,
    "rpc-username": "",
    "rpc-whitelist": "127.0.0.1",
    "rpc-whitelist-enabled": true,
    "speed-limit-down": 100,
    "speed-limit-down-enabled": false,
    "speed-limit-up": 100,
    "speed-limit-up-enabled": false,
    "umask": 18,
    "upload-slots-per-torrent": 14
}

while my edited file is here (copied from the URL in my prior note):
$ sudo cat /var/lib/transmission-daemon/info/settings.json
{
"alt-speed-down": 500,
"alt-speed-enabled": true,
"alt-speed-time-begin": 480,
"alt-speed-time-day": 127,
"alt-speed-time-enabled": true,
"alt-speed-time-end": 0,
"alt-speed-up": 10,
"bind-address-ipv4": "0.0.0.0",
"bind-address-ipv6": "::",
"blocklist-enabled": false,
"dht-enabled": true,
"download-dir": "\/home\/nimda\/dl\torrent",
"download-limit": 1000,
"download-limit-enabled": 0,
"encryption": 2,
"incomplete-dir": "\/var\/lib\/transmission-daemon\/info\/Incomplete",
"incomplete-dir-enabled": false,
"lazy-bitfield-enabled": true,
"max-peers-global": 200,
"message-level": 2,
"open-file-limit": 32,
"peer-limit-global": 240,
"peer-limit-per-torrent": 60,
"peer-port": 20683,
"peer-port-random-high": 20500,
"peer-port-random-low": 20599,
"peer-port-random-on-start": true,
"peer-socket-tos": 0,
"pex-enabled": true,
"port-forwarding-enabled": false,
"preallocation": 1,
"proxy": "",
"proxy-auth-enabled": false,
"proxy-auth-password": "",
"proxy-auth-username": "",
"proxy-enabled": false,
"proxy-port": 80,
"proxy-type": 0,
"ratio-limit": 0.2500,
"ratio-limit-enabled": true,
"rename-partial-files": true,
"rpc-authentication-requir...

[jvin248 (jvin248)]

Then I found the location of the configuration file being used in 10.04:

transmission-daemon -f
[23:55:41.117] Transmission 1.92 (10363) started (session.c:608)

[23:55:41.118] Using settings from "/home/nimda/.config/transmission-daemon" (daemon.c:424)
[23:55:41.118] Saved "/home/nimda/.config/transmission-daemon/settings.json" (bencode.c:1645)

[Siqdiz (oscardisch)]

sudo chown debian-transmission yourfoldernamehere

I'm running a minimal ubuntu 10.04 installation, headless with transmission-daemon. transmission-daemon is being run as debian-transmission according to the init.d/transmission-daemon file. As workaround I have changed ownership of the folder where transmission-daemon writes.

[Bas Roset (broset)]

I'm running Transmission 1.93 (10621) on Ubuntu 10.04, as a headless server, and I keep getting the same "Permission Denied" error.
I notice too that Transmission uses ~/.config/transmission-daemon/settings.json as a config file, and not the one I edit, /var/lib/transmission-daemon/info/settings.json , and I've chowned my download folder, but still this doesn't seem to do anything..

Still "permission denied".

Any updates on this?

[clark3934 (clark3934)]

I am also affected by this bug. I have made all .torrent files, download, and configuration files/folders owned by debian-transmission:debian-transmission, but the problems still persist. While others have suggested running $transmission -f or $transmission-daemon -f for debugging, I can't produce the same results since I am running transmission-daemon as a service. Is there any way I can do something roughly equivalent to $sudo service transmission -f start? If only it accepted flags.

[Justin (justin-hawkins-id)]

Just as a reference for the Interwebz, I had this problem as well, but eventually discovered that I had a bad (relative) file path in the 'incomplete-dir' configuration key.

It is quite easy to make this happen by fiddling with the transmission-remote command line utility, and passing it bad arguments :-) In my case I used -c instead of -t to specify a particular torrent, and the damage is done:

Couldn't create "2": Permission denied (utils.c:610)
Couldn't create "2/torrent.name.here": Permission denied (fdlimit.c:341)
torrent.name.here tr_fdFileCheckout failed for "2/torrent.name.here.part": Permission denied (inout.c:122)

Preumably the CWD is '/' or somewhere else that transmission can't write to, and the error message does not help identify that too much.

I'm not saying that there isn't a real bug for the people up here, I'm just telling you what happened to me and how it just might be PEBCAK :-)

[Hadrien Titeux (hadware)]

I've got the same problem on a Debian Squeeze headless server, but i'm reporting it here since it's the most active discussion I've found.
transmission-daemon -f helped , but it seems the problem stems from some kind of bad incomplete folder config.

[yemu (yemu)]

same problem here:
tr_fdFileCheckout failed for "/home/yemu/Download/Current/file.part": Permission denied (inout.c:100)
the strange thing is that the current dir is set to other directory (it was set to the one above, but I changed it).
I'd be grategul for any help
c