I installed Xubuntu and transmission daemon, set the download path to my home/user/TV shows, and get a permission denied when trying to download torrents through the transmission.
I tried chmod -r 777
on this folder without success.
Please help!
Following is the output of ps -ef | grep transmission
chen@htpc:~$ ps -ef | grep transmission
109 1023 1 1 21:46 ? 00:00:35 /usr/bin/transmission-daemon --config-dir /var/lib/transmission-daemon/info
chen@htpc:~$ ps aux | grep transmission
109 1023 3.2 0.4 47684 16620 ? Ssl 21:46 1:20 /usr/bin/transmission-daemon --config-dir /var/lib/transmission-daemon/info
chen 1852 0.0 0.0 4200 772 pts/0 S+ 22:27 0:00 grep --color=auto transmission
enter code here
asked Nov 23, 2012 at 19:55
6
Assuming the path to the download folder is /home/chen/TV shows
, run the following:
-
add chen to the debian-transmission group
sudo usermod -a -G debian-transmission chen
-
change the folder ownership
sudo chgrp debian-transmission /home/chen/TV shows
-
grant write access to the group
sudo chmod 770 /home/chen/TV shows
-
Stop the deamon with
sudo service transmission-daemon stop
-
The last thing to do is change the file creation mask, so that the downloaded files would be writeable by chen.
sudo nano /etc/transmission-daemon/settings.json
… and change
"umask": 18
to"umask": 2
. Hit Ctrl+O to save and Ctrl+X to exit.
Start the daemon with
sudo service transmission-daemon start
answered Nov 23, 2012 at 20:58
mikewhatevermikewhatever
31.8k10 gold badges85 silver badges97 bronze badges
8
Check if you’re using an «incomplete» folder.
The error can be misleading in this case and it may be the incomplete folder you do not have write access to.
answered Sep 23, 2015 at 17:41
blockdorblockdor
911 silver badge1 bronze badge
4
This is a permission issue based on the user ID that is running Transmission. Transmission sets up a default user that you might not expect on first install. The user name is debian-transmission
.
I will explain how to change that:
- Stop the Transmission daemon
sudo service transmission-daemon stop
- Open the Transmission config file for editing:
sudo nano /etc/init.d/transmission-daemon
- Find the line that says
USER=debian-transmission
and change it to the user that owns the folder in question. If you are not concerned about security issues, you can also useUSER=root
in this file. (Not advised, but good for troubleshooting). - Alternatively (instead of point number 3), modify the /etc/fstab folder to mount the folder with correct permissions for the user that runs the transmission-daemon.
- Start the Transmission daemon
sudo service transmission-daemon start
answered Nov 16, 2013 at 7:09
TerryTerry
2743 silver badges9 bronze badges
2
Since this is the top search result in Google, for anyone reading this, I spend over an hour trying to get it to work. Turns out, the downloads folder specified in settings.json is «Downloads» instead of «downloads». Note the case.
answered Nov 23, 2016 at 13:21
This might be an apparmor profile problem. Transmission runs under the sanitized_helper
profile in apparmor.
Look for complaints in /var/log/kern.log. grep transm /var/log/kern.log
, particularly just after trying to run transmission and it failing.
answered Nov 23, 2012 at 23:58
Jim SalterJim Salter
4,3031 gold badge15 silver badges33 bronze badges
This just happened to me. I found this page, was intimidated by all the jargon, so I restarted Transmission, reserved the torrent file to a different location, and saved the torrent data to the same different location (desktop). Worked like a charm…
24601
9,12517 gold badges36 silver badges55 bronze badges
answered Jul 31, 2015 at 15:02
my problem was that transmission somehow was running as the user «transmissions-daemon» instead of the user it was supposed to run with.
answered Aug 11, 2020 at 14:24
1
In my case the problem was how the drive was being mounted. Using this in /etc/fstab
worked for me:
UUID=2069-1A05 /mnt/ext vfat rw,user,exec,umask=0000 0 0
Zanna♦
68.2k55 gold badges210 silver badges320 bronze badges
answered Jan 2, 2017 at 19:24
1
Make sure that the path for your incomplete torrents is absolute. My main directory was using ~/path-to-download
, which gave me an error. My incomplete directory was ~/path-to-download/incomplete
.
I received an error the first time I tried to download a torrent not using an absolute directory. I fixed that, but kept receiving a permission denied error, even after adding the correct permissions. Once I fixed my incomplete path to an absolute path, everything worked.
answered Dec 22, 2019 at 19:49
Mounting the external drive into my home directory resolved this issue;
sudo mkdir /home/plex/media-server
sudo chmod 770 /home/plex/media-server
sudo mount /dev/sdxx/ /home/plex/media-drive
sdxx
is the name of your hdd. you can use the following command to find yours:
lsblk
Zanna♦
68.2k55 gold badges210 silver badges320 bronze badges
answered Feb 22, 2019 at 11:37
Try this:
sudo setfacl -m u:debian-transmission:rxw /home/*your user*/*your path to folder*
answered Sep 14, 2020 at 10:23
1
None of these suggestions worked for me so I just set fstab to use transmission-daemon’s default download directory as the mountpoint to mount my USB stick.
- First I set the ownership of my USB stick to match that of the default download directory:
sudo chown debian-transmission:debian-transmission /media/pi/[mountpoint]/
- Edit fstab:
sudo nano /etc/fstab
Insert the following text:
UUID=[insert device UUID here] /var/lib/transmission-daemon/downloads ext4 rw,user,exec 0 0
Note: you can find your USB sticks UUID by running sudo blkid
- Reboot the system:
sudo reboot
- You can test whether it is writing data to your USB stick by running
df -ha
and checking whether the data written to your USB stick increases when you add a new torrent. Note that the data increase happens all at once when you add a new torrent and NOT gradually as the torrent downloads.
answered Apr 11, 2022 at 13:32
0
I added the debian-transmission user to my $USER group:
sudo usermod -a -G <myusername> debian-transmission
answered Jun 26, 2022 at 19:27
Mark SmithMark Smith
5544 silver badges9 bronze badges
In my case I have the «download-dir», «incomplete-dir» (and «watch-dir») situated in my home-directory.
(presume my userid is ‘[user]
‘)
ls -la /home/[user]/Transmission
results in:
drwxr-xr-x 5 [user] debian-transmission 4096 sep 17 21:21 ./
drwxr-x--- 19 [user] [user] 4096 sep 20 20:08 ../
drwxrwxr-x 3 [user] debian-transmission 4096 sep 18 23:04 Completed/
drwxrwxr-x 4 [user] debian-transmission 4096 sep 20 20:11 Incomplete/
drwxrwxr-x 2 [user] debian-transmission 4096 sep 17 21:21 Torrents/
As you can see the user debian-transmission
has all the necessary permissions to write in those directories except… it has no read and execute permission on /home/[user]
!!! So as a result, debian-transmission
cannot access its subdirectories either.
- Lesson learned: check the permissions for the entire path ! Not just the final target directory !
There are now 3 options (choose one !):
- Add the group
[user]
to the userdebian-transmission
(sudo usermod -a -G [user] debian-transmission
) - Set x-permissions on world for
/home/[user]
(sudo chmod o+x /home/[user]
) - Stop the deamon, move the whole directory tree
/home/[user]/Transmission
to the home directory ofdebian-transmission
. Set ownership of those directories todebian-transmission:debian-transmission
. Edit/etc/transmission-daemon/settings.json
likewise. Add groupdebian-transmission
to[user]
and -finally- start the deamon again.
Option 1 and 2 have some minor security issues so option 3 is probably the best.
answered Sep 20, 2022 at 18:49
T-menT-men
11 bronze badge
2022 and I had the same issue.
A simple sudo chown debian-transmission:debian-transmission -R /path/to/download
solved it for me.
answered Dec 7, 2022 at 23:15
For those with custom locations, be sure you are applying chown to the original folder path and not a symlink.
sudo chown -R debian-transmission:debian-transmission /mnt/nas/downloads
NOT
sudo chown -R debian-transmission:debian-transmission /home/coolguy/nas/downloads
Add a 755
sudo chmod -R 755 /mnt/nas/downloads
I was able to get around the permissions issue by doing that. Also, no need to change the umask or 777 (or running as root, not a good plan).
Also, the latest transmission-daemon doesn’t seem to include and error log. Add this to your config file if you need some error output for debugging:
"log-error-file": "/var/log/transmission-error.log"
Be sure to restart
systemctl restart transmission-daemon
answered Jan 6 at 2:19
I had same issue, and that was a mistake I had made when sym-linking the transmission download directory to my home/user/ directory, I changed the ownership of the sym-linked file which by consequence also changed the ownership of the transmission ‘download’ directory…
I just chowned back to ‘debian-transmission’ ownership and it worked like a charm (without need to restart service)
#chown debian-transmission:debian-transmission /var/lib/transmission/downloads
(well, you’ll have to check according your own linux distribution what is the right owner and eventually also your right path to the downloads directory)
answered Dec 9, 2014 at 10:37
I had similar issue with transmission. I got Permission Error while downloading even with correct folder permission settings on the external USB HDD.
I just mounted the external HDD to the /home/pi/
with the same permissions and it worked fine.
mount /dev/sda /home/pi/USB-HDD-MOUNTED
permissions are drwxrwxrwx (0777) pi:debian-transmission
.
user name is changed to pi
in /etc/init.d/transmisssion-daemon
.
answered Feb 12, 2016 at 10:00
I installed Xubuntu and transmission daemon, set the download path to my home/user/TV shows, and get a permission denied when trying to download torrents through the transmission.
I tried chmod -r 777
on this folder without success.
Please help!
Following is the output of ps -ef | grep transmission
chen@htpc:~$ ps -ef | grep transmission
109 1023 1 1 21:46 ? 00:00:35 /usr/bin/transmission-daemon --config-dir /var/lib/transmission-daemon/info
chen@htpc:~$ ps aux | grep transmission
109 1023 3.2 0.4 47684 16620 ? Ssl 21:46 1:20 /usr/bin/transmission-daemon --config-dir /var/lib/transmission-daemon/info
chen 1852 0.0 0.0 4200 772 pts/0 S+ 22:27 0:00 grep --color=auto transmission
enter code here
asked Nov 23, 2012 at 19:55
6
Assuming the path to the download folder is /home/chen/TV shows
, run the following:
-
add chen to the debian-transmission group
sudo usermod -a -G debian-transmission chen
-
change the folder ownership
sudo chgrp debian-transmission /home/chen/TV shows
-
grant write access to the group
sudo chmod 770 /home/chen/TV shows
-
Stop the deamon with
sudo service transmission-daemon stop
-
The last thing to do is change the file creation mask, so that the downloaded files would be writeable by chen.
sudo nano /etc/transmission-daemon/settings.json
… and change
"umask": 18
to"umask": 2
. Hit Ctrl+O to save and Ctrl+X to exit.
Start the daemon with
sudo service transmission-daemon start
answered Nov 23, 2012 at 20:58
mikewhatevermikewhatever
31.8k10 gold badges85 silver badges97 bronze badges
8
Check if you’re using an «incomplete» folder.
The error can be misleading in this case and it may be the incomplete folder you do not have write access to.
answered Sep 23, 2015 at 17:41
blockdorblockdor
911 silver badge1 bronze badge
4
This is a permission issue based on the user ID that is running Transmission. Transmission sets up a default user that you might not expect on first install. The user name is debian-transmission
.
I will explain how to change that:
- Stop the Transmission daemon
sudo service transmission-daemon stop
- Open the Transmission config file for editing:
sudo nano /etc/init.d/transmission-daemon
- Find the line that says
USER=debian-transmission
and change it to the user that owns the folder in question. If you are not concerned about security issues, you can also useUSER=root
in this file. (Not advised, but good for troubleshooting). - Alternatively (instead of point number 3), modify the /etc/fstab folder to mount the folder with correct permissions for the user that runs the transmission-daemon.
- Start the Transmission daemon
sudo service transmission-daemon start
answered Nov 16, 2013 at 7:09
TerryTerry
2743 silver badges9 bronze badges
2
Since this is the top search result in Google, for anyone reading this, I spend over an hour trying to get it to work. Turns out, the downloads folder specified in settings.json is «Downloads» instead of «downloads». Note the case.
answered Nov 23, 2016 at 13:21
This might be an apparmor profile problem. Transmission runs under the sanitized_helper
profile in apparmor.
Look for complaints in /var/log/kern.log. grep transm /var/log/kern.log
, particularly just after trying to run transmission and it failing.
answered Nov 23, 2012 at 23:58
Jim SalterJim Salter
4,3031 gold badge15 silver badges33 bronze badges
This just happened to me. I found this page, was intimidated by all the jargon, so I restarted Transmission, reserved the torrent file to a different location, and saved the torrent data to the same different location (desktop). Worked like a charm…
24601
9,12517 gold badges36 silver badges55 bronze badges
answered Jul 31, 2015 at 15:02
my problem was that transmission somehow was running as the user «transmissions-daemon» instead of the user it was supposed to run with.
answered Aug 11, 2020 at 14:24
1
In my case the problem was how the drive was being mounted. Using this in /etc/fstab
worked for me:
UUID=2069-1A05 /mnt/ext vfat rw,user,exec,umask=0000 0 0
Zanna♦
68.2k55 gold badges210 silver badges320 bronze badges
answered Jan 2, 2017 at 19:24
1
Make sure that the path for your incomplete torrents is absolute. My main directory was using ~/path-to-download
, which gave me an error. My incomplete directory was ~/path-to-download/incomplete
.
I received an error the first time I tried to download a torrent not using an absolute directory. I fixed that, but kept receiving a permission denied error, even after adding the correct permissions. Once I fixed my incomplete path to an absolute path, everything worked.
answered Dec 22, 2019 at 19:49
Mounting the external drive into my home directory resolved this issue;
sudo mkdir /home/plex/media-server
sudo chmod 770 /home/plex/media-server
sudo mount /dev/sdxx/ /home/plex/media-drive
sdxx
is the name of your hdd. you can use the following command to find yours:
lsblk
Zanna♦
68.2k55 gold badges210 silver badges320 bronze badges
answered Feb 22, 2019 at 11:37
Try this:
sudo setfacl -m u:debian-transmission:rxw /home/*your user*/*your path to folder*
answered Sep 14, 2020 at 10:23
1
None of these suggestions worked for me so I just set fstab to use transmission-daemon’s default download directory as the mountpoint to mount my USB stick.
- First I set the ownership of my USB stick to match that of the default download directory:
sudo chown debian-transmission:debian-transmission /media/pi/[mountpoint]/
- Edit fstab:
sudo nano /etc/fstab
Insert the following text:
UUID=[insert device UUID here] /var/lib/transmission-daemon/downloads ext4 rw,user,exec 0 0
Note: you can find your USB sticks UUID by running sudo blkid
- Reboot the system:
sudo reboot
- You can test whether it is writing data to your USB stick by running
df -ha
and checking whether the data written to your USB stick increases when you add a new torrent. Note that the data increase happens all at once when you add a new torrent and NOT gradually as the torrent downloads.
answered Apr 11, 2022 at 13:32
0
I added the debian-transmission user to my $USER group:
sudo usermod -a -G <myusername> debian-transmission
answered Jun 26, 2022 at 19:27
Mark SmithMark Smith
5544 silver badges9 bronze badges
In my case I have the «download-dir», «incomplete-dir» (and «watch-dir») situated in my home-directory.
(presume my userid is ‘[user]
‘)
ls -la /home/[user]/Transmission
results in:
drwxr-xr-x 5 [user] debian-transmission 4096 sep 17 21:21 ./
drwxr-x--- 19 [user] [user] 4096 sep 20 20:08 ../
drwxrwxr-x 3 [user] debian-transmission 4096 sep 18 23:04 Completed/
drwxrwxr-x 4 [user] debian-transmission 4096 sep 20 20:11 Incomplete/
drwxrwxr-x 2 [user] debian-transmission 4096 sep 17 21:21 Torrents/
As you can see the user debian-transmission
has all the necessary permissions to write in those directories except… it has no read and execute permission on /home/[user]
!!! So as a result, debian-transmission
cannot access its subdirectories either.
- Lesson learned: check the permissions for the entire path ! Not just the final target directory !
There are now 3 options (choose one !):
- Add the group
[user]
to the userdebian-transmission
(sudo usermod -a -G [user] debian-transmission
) - Set x-permissions on world for
/home/[user]
(sudo chmod o+x /home/[user]
) - Stop the deamon, move the whole directory tree
/home/[user]/Transmission
to the home directory ofdebian-transmission
. Set ownership of those directories todebian-transmission:debian-transmission
. Edit/etc/transmission-daemon/settings.json
likewise. Add groupdebian-transmission
to[user]
and -finally- start the deamon again.
Option 1 and 2 have some minor security issues so option 3 is probably the best.
answered Sep 20, 2022 at 18:49
T-menT-men
11 bronze badge
2022 and I had the same issue.
A simple sudo chown debian-transmission:debian-transmission -R /path/to/download
solved it for me.
answered Dec 7, 2022 at 23:15
For those with custom locations, be sure you are applying chown to the original folder path and not a symlink.
sudo chown -R debian-transmission:debian-transmission /mnt/nas/downloads
NOT
sudo chown -R debian-transmission:debian-transmission /home/coolguy/nas/downloads
Add a 755
sudo chmod -R 755 /mnt/nas/downloads
I was able to get around the permissions issue by doing that. Also, no need to change the umask or 777 (or running as root, not a good plan).
Also, the latest transmission-daemon doesn’t seem to include and error log. Add this to your config file if you need some error output for debugging:
"log-error-file": "/var/log/transmission-error.log"
Be sure to restart
systemctl restart transmission-daemon
answered Jan 6 at 2:19
I had same issue, and that was a mistake I had made when sym-linking the transmission download directory to my home/user/ directory, I changed the ownership of the sym-linked file which by consequence also changed the ownership of the transmission ‘download’ directory…
I just chowned back to ‘debian-transmission’ ownership and it worked like a charm (without need to restart service)
#chown debian-transmission:debian-transmission /var/lib/transmission/downloads
(well, you’ll have to check according your own linux distribution what is the right owner and eventually also your right path to the downloads directory)
answered Dec 9, 2014 at 10:37
I had similar issue with transmission. I got Permission Error while downloading even with correct folder permission settings on the external USB HDD.
I just mounted the external HDD to the /home/pi/
with the same permissions and it worked fine.
mount /dev/sda /home/pi/USB-HDD-MOUNTED
permissions are drwxrwxrwx (0777) pi:debian-transmission
.
user name is changed to pi
in /etc/init.d/transmisssion-daemon
.
answered Feb 12, 2016 at 10:00
При начале закачки нового торрента сразу же выдает такую ошибку:
Transmission daemon Error: permission denied
Полагаю проблема с правами доступа, как исправить
Система Ubuntu Linux 18.04.2
Конфиги:
settings.json
{
«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,
«blocklist-url»: «www.example.com/blocklist»,
«cache-size-mb»: 4,
«dht-enabled»: true,
«download-dir»: «/media/FILMS»,
«download-limit»: 100,
«download-limit-enabled»: 0,
«download-queue-enabled»: true,
«download-queue-size»: 5,
«encryption»: 1,
«idle-seeding-limit»: 30,
«idle-seeding-limit-enabled»: false,
«incomplete-dir»: «/media/.incomplete»,
«incomplete-dir-enabled»: true,
«lpd-enabled»: false,
«max-peers-global»: 200,
«message-level»: 1,
«peer-congestion-algorithm»: «»,
«peer-id-ttl-hours»: 6,
«peer-limit-global»: 200,
«peer-limit-per-torrent»: 50,
«peer-port»: 51413,
«peer-port-random-high»: 65535,
«peer-port-random-low»: 49152,
«peer-port-random-on-start»: false,
«peer-socket-tos»: «default»,
«pex-enabled»: true,
«port-forwarding-enabled»: false,
«preallocation»: 1,
«prefetch-enabled»: true,
«queue-stalled-enabled»: true,
«queue-stalled-minutes»: 30,
«ratio-limit»: 2,
«ratio-limit-enabled»: false,
«rename-partial-files»: true,
«rpc-authentication-required»: false,
«rpc-bind-address»: «0.0.0.0»,
«rpc-enabled»: true,
«rpc-host-whitelist»: «»,
«rpc-host-whitelist-enabled»: true,
«rpc-password»: «{8f756f1341a8a27ad60d25ed4f95ced0e1ea7fe3tUAtbBjY»,
«rpc-port»: 9091,
smb.conf
[global]
security = user
directory mode = 777
map to guest = Bad User
workgroup = WORKGROUP
server string = Samba
create mode = 777
force directory mode = 777
writeable = yes
force create mode = 777
os level = 20
[TORRENTS]
path = /media/TORRENTS
browseable = Yes
guest ok = Yes
writeable = Yes
public = yes
[.incomplete]
path = /media/.incomplete
browseable = Yes
guest ok = Yes
writeable = Yes
public = yes
На большинстве ресурсов (форумы, обсуждения) подразумевается, что если качать файлы этим клиентом, то каталог, куда идет скачивание и сами файлы должны быть с правами самого демона. Точнее говоря, даже не подразумевается, что его можно запустить от имени другого пользователя.
Есть момент, концептуально отличающийся от принятого — эта торрентокачалка может использоваться не только для того, что бы качать ею файлы в каталог $Downloaddir. К примеру, у меня может быть каталог, где я храню книги, документы, фильмы, музыку итд. Что-то раздается, над чем-то может идти работа, а это доступ через samba, или через ftp. Что-то вообще не раздается через торрентокачалку. То есть, политика работы с данными — разнородная. Компьютер, где все это хранится — это не десктоп. Эдакий nas. Десктопом, вообще выступает OS X, которая через nfs, или самбу ходит на такой nas.
теперь, картина. Запускается transmission. Качает файлы в свою transmission диру. На нее наложены свои права. Обращение к демону идет с OS X, посредством Transmission remote GUI. В этой морде есть возможность перемещения файлов. Мне не совсем удобно, что все файлы, которые качаются, прыгают в эту Download директорию. То есть, все валится в одну кучу.
переместить же я эти данные способом Transmission re,ote GUI не могу, ибо в моем медиа каталоге права традиционные — юзерские. И самба настроена так же — парольный доступ под юзера Ubuntu.
Вопрос. Почему принято скидывать все в одну кучу, когда речь заходит об этом клиенте?
Просто, в инете такая тема (подход) в 90% процентов случаев.
Люди описывают альтернативы настроек этого клиента, но на лицо костыли. Кто-то вообще советует хреначить права 777. Другие, более интеллигентно — поправки sgid на директории всей своей «медии», замена прав такого пространства на юзера transmission.
Гентушники имеют возможность пускать клиента от обычного юзера.
Под Ubuntu — это не проходит:
cat /etc/default/transmission-daemon | grep USER
USER="zanzibar"
sudo service transmission-daemon restart
ps -ef | grep trans
106 1429 1 1 12:24 ? 00:00:02 /usr/bin/transmission-daemon -f --config-dir /var/lib/transmission-daemon/info
Честно сказать, третьи сутки пытаюсь распутать эту проблему.
И второй вопрос. Главный. Почему появляются такие сложности? Это такие руки у меня?
Hello hopefully my saviours!
I’ve been bashing my head against this problem for a few days now looking at guides all over the web and these forums but just can’t seem to get it working. I’m hoping someone sees some obvious mistake I’m making so we can finally call it a day! I know I’m not the only one with a problem like this before, and while I couldn’t find a solution that worked for me out there, maybe I will now.
Anyways, I just wanted to install the Transmission plugin and have it work. No matter how I seem to configure it I get permission denied errors like so:
My Transmission plugin config is here. I chose 775 for the umask since I plan on having group access to the download folder for Sonarr and such.
I’ve set up a dataset called DownloadTemp to store the torrents in I later want Sonarr and such to have access too so I have it owned by the group «media» (816) with the intention of having them all able to access it as a group.
Naturally I have this group in the GUI as well, using GID 816 to match what I’m told some other plugins like Plex use to make things easier in the future.
So I followed the steps of mounting the dataset to a location in the jail using the GUI as shown here.
Then I followed the lovely guide provided by forum member joshua-parker-ruehlig here at https://forums.freenas.org/index.ph…plugins-write-permissions-to-your-data.27273/ and went with solution #3, group write access. For this I added a group called media with GID 816 to the jail and added transmission to said group which I show here.
This however, did not seem to be enough with all the errors I got, so with some more digging and learning about UNIX permissions (I’m still new to this, but that’s part of the reason I built this machine, to learn!) I found that the umask could be a concern. Now with the Transmission daemon supposedly setting this based on the settings file, I checked that immediately and found it to be 2 as expected.
So then I started looking at the umask and permissions of all the folders themselves starting with the dataset:
Looks good to me. Then the mount point from the main shell/freenas perspective:
Still looks good, now finally from the jail’s perspective:
This does not look good! All the ownerships and permissions seem fine to me if the GIDs map between FreeNAS and the jails as described, but that umask is still 22 not 2. Changing it only makes it stay until the next time the jail is restarted which is no good, and does nothing anyways until it is.
On top of all of this I even tried setting the dataset permissions to 777 and the umask to 0 but it always seems to change back to 22 no matter what I do. I feel like the problem has something to do with that, and if it is or something else entirely, please let me know, and I appreciate you getting this far through my post anyways.
Thanks in advance!
Gunsmithy
Содержание
- “Error: permission denied” error from Transmission Client
- 1 Answer 1
- Transmission
- transmission-daemon permission denied on ubuntu server
- transmission-daemon permission denied on ubuntu server
- Re: transmission-daemon permission denied on ubuntu server
- Re: transmission-daemon permission denied on ubuntu server
- Re: transmission-daemon permission denied on ubuntu server
- Re: transmission-daemon permission denied on ubuntu server
- Re: transmission-daemon permission denied on ubuntu server
- Re: transmission-daemon permission denied on ubuntu server
- Re: transmission-daemon permission denied on ubuntu server
- Re: transmission-daemon permission denied on ubuntu server
- Re: transmission-daemon permission denied on ubuntu server
- Re: transmission-daemon permission denied on ubuntu server
- Re: transmission-daemon permission denied on ubuntu server
- Permission denied when downloading with transmission daemon
- 18 Answers 18
- Transmission. Started with a «permission denied», now it won’t even run
“Error: permission denied” error from Transmission Client
When I try downloading files with Transmission I get:
I’ve tried searching for this problem, and everyone always says to set permissions correctly, but I’ve done that:
This is running on a debian headless server and I did have it working until I moved the folders out of my home directory and into one of their own; ever since then I haven’t been able to get it up and running, even in my home directory again. I’ve even purge removed it and installed it again, setting it all up following one of the countless number of guides step for step, and I have gotten nowhere.
I’m not sure if transmission-daemon -f can help you guys to help me, but I thought what it outputs may be relevant because I saw «transmission-daemon requiring authentication»:
1 Answer 1
Your permissions aren’t right—but its somewhere you’re not looking:
It could be on /home/Transmission (you need to make sure it has execute (x) permission on that; ls -ld /home/Transmission to check). As well as on /home , but /home should be a+x already.
Alternatively, it could be on the files themselves—you didn’t give an ls -l Transmission/Downloads/ .
If you’re running SELinux or similar, you may also need to configure that.
Also, are you sure your daemon is running as user debian-transmission ? If so, as root:
That should run without error; if you get permission denied, you definitely have a permission problem.
You may also find running strace on the running daemon to be useful. For example, if the daemon is pid 123:
and leaving that running as you add another torrent, or stop/start an existing torrent should quickly find you the permission denied error. It may turn out that its a file you didn’t know Transmission was trying to access.
Источник
Transmission
A Fast, Easy, and Free BitTorrent client
transmission-daemon permission denied on ubuntu server
transmission-daemon permission denied on ubuntu server
Post by toto56 » Mon Aug 23, 2010 8:59 pm
I have read a lot of posts on the permission denied problem but none solved my problem.
I have transmission-daemon running on ubuntu server 10.04. I acces it via the WebUI.
The download folder is a Samba shared folder that I mounted with debian-transmission user.
When I had a torrent, the file created by transmission-daemon is owned by root and therefore it says «Permission denied».
To enable the download I do a chown -R debian-transmission /media/myDLfolder and it starts.
But each time I add a new torrent I have to do this.
Is there a way to have the newly created files owned by debian-transmission or my user?
(I installed transmission-daemon with sudo apt-get install debian-transmission if it helps)
Re: transmission-daemon permission denied on ubuntu server
Post by Iw9WlOuY » Mon Aug 23, 2010 10:54 pm
Re: transmission-daemon permission denied on ubuntu server
Post by toto56 » Tue Aug 24, 2010 5:44 am
Re: transmission-daemon permission denied on ubuntu server
Post by toto56 » Tue Aug 24, 2010 6:36 am
Re: transmission-daemon permission denied on ubuntu server
Post by toto56 » Tue Aug 24, 2010 6:38 am
Re: transmission-daemon permission denied on ubuntu server
Post by rb07 » Tue Aug 24, 2010 11:46 pm
Re: transmission-daemon permission denied on ubuntu server
Post by toto56 » Wed Aug 25, 2010 6:35 am
Thanks for your reply.
I am on ubuntu server, so I stop the daemon with sudo (sudo /etc/init.d/transmission-daemon stop). Start/stop transmission daemon is only allowed with sudo (root).
The folder is mounted with debian-transmission user, the files are owned by debian-transmission user and group (chown -R debian-transmission, chgrp -R debian-transmission). I have made a chmod -R 777 on the download folder.
But still when a new file is created, it is owned by root.
Re: transmission-daemon permission denied on ubuntu server
Post by rb07 » Wed Aug 25, 2010 3:15 pm
Then it is running as root.
Let’s try something simple, run:
Is the second field (the user name) different than root?
If it is
- root: did you check that the init script changes users? If it does, did you check that the program is not suid (set user id)?
- not root: check if the download directory has not the sgid (set group id) permission.
There are probably more possible causes, like your Samba options. but this is a Transmission forum, and all of these has nothing to do with Transmission, its about using Linux.
Re: transmission-daemon permission denied on ubuntu server
Post by toto56 » Wed Aug 25, 2010 8:27 pm
Thanks for your reply,
The command ps -ef | grep trans returns that transmission-daemon is running under user 104 which is debian-transmission
I am now testing with the download folder on a the local folder (no samba mount) and I still have the same problem.
Re: transmission-daemon permission denied on ubuntu server
Post by toto56 » Wed Aug 25, 2010 8:44 pm
Re: transmission-daemon permission denied on ubuntu server
Post by costales » Fri Oct 18, 2013 4:48 pm
mkdir /your_path/progress
mkdir /your_path/completed
sudo usermod -a -G debian-transmission your_user
chgrp debian-transmission /your_path/progress
chgrp debian-transmission /your_path/completed
chmod 770 /your_path/progress
chmod 770 /your_path/completed
sudo service transmission-daemon stop
sudo adduser your_user debian-transmission
sudo nano /etc/init.d/transmission-daemon
sudo chown your_user -R /var/lib/transmission-daemon/info/
sudo chown your_user -R /your_path/progress
sudo chown your_user -R /your_path/completed
sudo chown your_user -R /etc/transmission-daemon/settings.json
And change in the file:
sudo nano /etc/transmission-daemon/settings.json
«rpc-whitelist»: «127.0.0.1» > «rpc-whitelist»: «*.*.*.*»,
«rpc-password»: «password» > «rpc-password»: «your_password»,
«download-dir»: «/var/lib/transmission-daemon/downloads» > «download-dir»: «/your_path/completed»
«incomplete-dir»: «/var/lib/transmission-daemon/downloads» > «incomplete-dir»: «/your_path/progress»
Just restart the daemon:
service transmission-daemon start
Re: transmission-daemon permission denied on ubuntu server
Post by Cuore Sportivo » Thu Jun 30, 2016 11:58 am
Hello everyone and sorry for digging such an old thread, but I have the exact same problem.
I have a samba shares server (running on a Ubuntu VM) with guest access enabled, so that guests can read/write files.
On another Ubuntu VM, I have installed transmission daemon, and I have also mounted on /media/torrents the torrents folder of my ubuntu shares server (//samba.local.ip/torrents), so that transmission can immediately download torrents to the local folder.
Even though I can read/write files without any problem to the samba shares, when transmission starts to download any torrent, after a couple of seconds, it will get an error (permission denied).
I added transmission-daemon to user group (sudo usermod -a -G user debian-transmission), but nothing changes. I also tried to change the group owner of /media/torrents, but I get a permission denied.
Источник
Permission denied when downloading with transmission daemon
I installed Xubuntu and transmission daemon, set the download path to my home/user/TV shows, and get a permission denied when trying to download torrents through the transmission.
I tried chmod -r 777 on this folder without success.
Following is the output of ps -ef | grep transmission
18 Answers 18
Assuming the path to the download folder is /home/chen/TV shows , run the following:
add chen to the debian-transmission group
change the folder ownership
grant write access to the group
Stop the deamon with
The last thing to do is change the file creation mask, so that the downloaded files would be writeable by chen.
… and change «umask»: 18 to «umask»: 2 . Hit Ctrl + O to save and Ctrl + X to exit.
Start the daemon with
Check if you’re using an «incomplete» folder. The error can be misleading in this case and it may be the incomplete folder you do not have write access to.
This is a permission issue based on the user ID that is running Transmission. Transmission sets up a default user that you might not expect on first install. The user name is debian-transmission .
I will explain how to change that:
- Stop the Transmission daemon sudo service transmission-daemon stop
- Open the Transmission config file for editing: sudo nano /etc/init.d/transmission-daemon
- Find the line that says USER=debian-transmission and change it to the user that owns the folder in question. If you are not concerned about security issues, you can also use USER=root in this file. (Not advised, but good for troubleshooting).
- Alternatively (instead of point number 3), modify the /etc/fstab folder to mount the folder with correct permissions for the user that runs the transmission-daemon.
- Start the Transmission daemon sudo service transmission-daemon start
This might be an apparmor profile problem. Transmission runs under the sanitized_helper profile in apparmor.
Look for complaints in /var/log/kern.log. grep transm /var/log/kern.log , particularly just after trying to run transmission and it failing.
This just happened to me. I found this page, was intimidated by all the jargon, so I restarted Transmission, reserved the torrent file to a different location, and saved the torrent data to the same different location (desktop). Worked like a charm.
Since this is the top search result in Google, for anyone reading this, I spend over an hour trying to get it to work. Turns out, the downloads folder specified in settings.json is «Downloads» instead of «downloads». Note the case.
my problem was that transmission somehow was running as the user «transmissions-daemon» instead of the user it was supposed to run with.
In my case the problem was how the drive was being mounted. Using this in /etc/fstab worked for me:
Make sure that the path for your incomplete torrents is absolute. My main directory was using
/path-to-download , which gave me an error. My incomplete directory was
I received an error the first time I tried to download a torrent not using an absolute directory. I fixed that, but kept receiving a permission denied error, even after adding the correct permissions. Once I fixed my incomplete path to an absolute path, everything worked.
Mounting the external drive into my home directory resolved this issue;
sdxx is the name of your hdd. you can use the following command to find yours:
None of these suggestions worked for me so I just set fstab to use transmission-daemon’s default download directory as the mountpoint to mount my USB stick.
- First I set the ownership of my USB stick to match that of the default download directory:
sudo chown debian-transmission:debian-transmission /media/pi/[mountpoint]/
sudo nano /etc/fstab
Insert the following text:
UUID=[insert device UUID here] /var/lib/transmission-daemon/downloads ext4 rw,user,exec 0 0
Note: you can find your USB sticks UUID by running sudo blkid
- You can test whether it is writing data to your USB stick by running df -ha and checking whether the data written to your USB stick increases when you add a new torrent. Note that the data increase happens all at once when you add a new torrent and NOT gradually as the torrent downloads.
I added the debian-transmission user to my $USER group:
In my case I have the «download-dir», «incomplete-dir» (and «watch-dir») situated in my home-directory.
(presume my userid is ‘ [user] ‘)
ls -la /home/[user]/Transmission results in:
As you can see the user debian-transmission has all the necessary permissions to write in those directories except. it has no read and execute permission on /home/[user] . So as a result, debian-transmission cannot access its subdirectories either.
- Lesson learned: check the permissions for the entire path ! Not just the final target directory !
There are now 3 options (choose one !):
- Add the group [user] to the user debian-transmission ( sudo usermod -a -G [user] debian-transmission )
- Set x-permissions on world for /home/[user] ( sudo chmod o+x /home/[user] )
- Stop the deamon, move the whole directory tree /home/[user]/Transmission to the home directory of debian-transmission . Set ownership of those directories to debian-transmission:debian-transmission . Edit /etc/transmission-daemon/settings.json likewise. Add group debian-transmission to [user] and -finally- start the deamon again.
Option 1 and 2 have some minor security issues so option 3 is probably the best.
Источник
Transmission. Started with a «permission denied», now it won’t even run
So I just ventured into the land of Ubuntu. It was a pleasant stroll until I came onto the chasm of users and permissions.
I installed transmission-daemon. Everything looked nice and easy, but once a download gets going, it gives a shiny red «Permission denied» to my download path. So I started reading up on permissions. Learned how to use «gksudo nautilus» amongst other things. But things didn’t clear up at all. The download folder had no owner as far as I could see when I worked through the files dialog. With «gksudo nautilus», it just crashed the window. I couldn’t even see who owned it. Through the terminal it seemed all set like it should. Both owner and group set to debian-transmission.
Then I stumbled on this topic: Transmission daemon: permission denied even if debian-transmission has root group and I thought: «Hey, those are clear instructions I can follow! Let’s do this!». Now I’m stuck with a transmission that won’t even start. It gives me a nice «transmission-daemon start/running, process 29525». But that’s it. It stops right away and it’s gone. No error or anything that my untrained eyes can work with.
Can somebody help me with this? Some commands that can help me get further? Or should I just remove the whole thing and start over? Thanks in advance.
I have followed muru’s instructions and the daemon is back up and running but I am getting this error now:
Источник
-
April 16 2022, 16:34
- IT
- Кино
- Cancel
Под xigmanas у меня сейчас и временно используется старый ноутбук. (Новое железо уже куплено, но руки не доходят.) В основном качает старые фильмы и сериалы. Все работает нормально — но на некоторых торрентах возникает странная ошибка — закачка начинается и через несколько десятков секунд останавливается с ошибочкой permission denied… и далее указывается куда должен был писаться файл. Причем возникает на сериалах, с фильмом пока ни разу не отмечал.
Перевод — отказано в доступе. Но все права на запись есть, более того, в то же самое место соседний торрент прекрасно качается. Пару раз я боролся тем, что качал просто соседний торрент. Но вчера столкнулся с тем, что нужный мне сезон скачать не удается. Пришлось разбираться.
Проблема оказалась в слишком длинном имени — или файла или пути к нему. Объясню на примере
Папка для закачки пусть будет /mnt/Pool/Download
Сами сериалы некоторые релизеры именуют пространно.
Например (все названия вымышленные) сам сериал называется
Жизнь и удивительные приключения Робинзона Крузо, моряка из Йорка, написанная им самим, Дефо Даниель-Зинзевул Вуфелсон, 2137, Disney-Fox Limited. H377.8Kanamorf, trizhdyzloydemon877
А его серии вместо того чтобы быть S02E04.mkv оказываются
Жизнь и удивительные приключения Робинзона Крузо, моряка из Йорка, написанная им самим. Укрощение Пятницы.S02E04.mkv
ZFS имеет лимит на имя файла 255 байт. Так как кодировка символа сейчас духбайтная — то это всего 127 букв.
В качестве костыля в таком сериале после запуска его сразу ставлю на паузу, затем в Transmission Remote перименовываею сам сериал покороче. Если не помогает — приходится переименовывать и эпизоды, что довольно муторно.
PS Замечу, что если в xigmanas не качается вообще ни один торрент и выскакивает сообщение permission denied — дело в правах на запись для transmission для всех(!) папок указанных вами при настройке
А если скачивание даже не начинается (советую потестить на чем-то вроде образа Ubuntu, который всегда доступен) то дело скорее всего в том, что transmission имеет доступа к сети. Если на компе под Windows в этой же сети качается — попробуйте посмотреть какой порт выставлен для клиента и установить transmission такой же.