Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transmission permission issue on DSM5.0beta #827

Closed
jsweon4623 opened this issue Feb 6, 2014 · 20 comments
Closed

Transmission permission issue on DSM5.0beta #827

jsweon4623 opened this issue Feb 6, 2014 · 20 comments

Comments

@jsweon4623
Copy link

There's a permission issue that created share folder with DSM5.0.

It is normal created share folder with DSM4.3.

@Diaoul
Copy link
Member

Diaoul commented Feb 7, 2014

The transmission SPK doesn't create any share. What are the permissions on the folder?

@jsweon4623
Copy link
Author

I mean, created shared folder myself.

@Dr-Bean
Copy link
Contributor

Dr-Bean commented Feb 8, 2014

I think Synology changed things up with default shared folder permissions. DSM5.0 permissions are set to 755, whereas DSM4.3 permissions are set to 777.

Might be easiest to add a chmod 777 wizard_download_dir during install.

@eggeh1982
Copy link

Has anyone fixed this, im having the permission issue myself

@Diaoul
Copy link
Member

Diaoul commented Feb 20, 2014

If this is a DSM 5.0 bug, then it should be fixed, if not, we'll implement a fix.
For now Synology didn't answer the question. I'm still waiting from an answer from them.

@Dr-Bean
Copy link
Contributor

Dr-Bean commented Mar 17, 2014

@Diaoul It seems Synology did this "on purpose" when implementing ACL to limit the default permissions on directories. There are two ways to solve this that I can think of:

Solving it via the ACLs means creating users with synouser (or whatever the cmd was), and have the users be visible in the Synology GUI. We'll likely run into some configuration issues with home folders etc.

If not via the ACLs, it's either chmodding or chowning the dir to enable access to the user (or maybe a synocommunity group?).
Any other suggestions?

NZBGet, SAB, Transmission are the main packages which will be affected by this (only with clean install on DSM5: when upgrading from 4.3, 777 permissions are retained on shared folders)

@Dr-Bean
Copy link
Contributor

Dr-Bean commented Mar 28, 2014

So, looked into it a bit:
Doing something like synoshare --setuser sabnzbd RW + sabnzbd won't work when users are created via adduser.
Using the same command does work for users created via the Synology GUI (or synouser --add [..] for that matter), but that has the downside of not being able to set the home folder :/

@Diaoul, did you ever get a response from Synology on the subject?

@Diaoul
Copy link
Member

Diaoul commented Mar 28, 2014

Synology confirmed this is a feature not a bug so we need to fix this in a way.

I'm against using non-system users as the ACL settings won't work anyway (well at least it didn't work last time I tried, this is pure UNIX permission issue, no DSM layer involved AFAIK) and it adds complexity to the packages.

The issue is that the users group don't have write access anymore due to 755. The most elegant way to fix this I think is chmod g+rw /path/to/share

@Dr-Bean
Copy link
Contributor

Dr-Bean commented Mar 28, 2014

ACL doesn't seem a viable option, no, and if we keep away from DSM, that's all the better.

I was checking your fix, and there might be a minor catch: A freshly created shared folder is owned by root:root, so we'll have to chgrp users too, right? In all (well, a lot of) packages that use shared folders...

Besides that, I did notice some packages use the nobody group (although not sure if any of 'm need access to a share) I'd prefer a standard approach for the installer myself ;)

@dobber81
Copy link

Just ran in to this issue on a new ds214play with DSM 5.0. Is there a quick fix with chmod or so to fix the problem? I tried setting my downloads path to 777 but no luck. Files are not created.

Edit: I solved the problem temporarily by /volume1/transmission to 777 only changed /volume1/transmission/download before.

@FlishGer
Copy link

Hello guys,

I hope I can solve this problem for you. So what I did seems quite simple.

  1. Open the shared folder permissions for the folder transmission is set to download to
  2. On the top left do not select "local users" but "local groups"
  3. Select the group "users" and give "read and write permission"

After I did this, everything seems to be working again. Screenshot included, but only in German.

For any questions, feel free to reply.
git

@Dr-Bean
Copy link
Contributor

Dr-Bean commented Apr 10, 2014

Thanks, although 8c5f37f should take care of it without having to do manual actions.
The new packages are not yet published though, so with the current packages you still run into it.

@dobber81
Copy link

dobber81 commented May 1, 2014

Anyone know when to expect the new package to be released?

@Dr-Bean
Copy link
Contributor

Dr-Bean commented May 2, 2014

Hopefully, next week, unless someone beats me to it.

@dobber81
Copy link

dobber81 commented May 3, 2014

Great! :)

@Dr-Bean
Copy link
Contributor

Dr-Bean commented Jun 1, 2014

The new Transmission package has been released in the SynoCommunity repository, along with an update to the latest Transmission version.

When doing a fresh installation, the necessary permissions should be set correctly. Permissions are not changed when doing an upgrade of a previous package. So, closing as resolved.

@Dr-Bean Dr-Bean closed this as completed Jun 1, 2014
@mcroba
Copy link

mcroba commented Jun 29, 2014

Hi,

I would like to set my destinations folders in an external HDD (/VolumeUSB1/usbshare/...) but there is the same issue with permissions (even if I've done chmod -R 777)

DS214Play
Transmission package v. 2.83-6
DSM v. 5.0-4493 update 2

Could you help me with that ?

@arbyter
Copy link

arbyter commented Aug 10, 2014

Hi, I use a similar configuration like mcobra an run into the same permission problems. Is this problem actually solved?

DS414
Transmission 2.84 (14307)
DSM 5.0-4493 Update 3

@jjshocka
Copy link

File Station > Right Click (Share) Tab > [button] Create > User or Group (Everyone) .. (ok button) seemed to work for me .. user did not

@arbyter
Copy link

arbyter commented Aug 13, 2014

Yes, that's a nice work around but this not is practical is in a multiuser environment :|

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

10 participants