Can‘t start transmission on DSM7.0

Question

Can‘t start transmission on DSM7.0

jinfeng1985 opened this issue 4 years ago · 97 comments

jinfeng1985 commented 4 years ago

For new Package Requests, see the guidelines

Setup

Package Name: transmission
Package Version: 3.0

NAS Model: synology
NAS Architecture: 920+
DSM version: 7.0

Expected behavior

No root permission for installation and running
Will the software support 7.0?

Answer 1 · 2020-12-17T20:36:48.000Z

In DSM7 packages can not run as a root user anymore and so scripts need updating. Please see issue #4215 and the dsm7 branch for current progress. Pull requests are welcome.

Answer 2 · 2020-12-31T02:48:44.000Z

transmission also needs additional "resources" in order to access the files in the download folder. I've managed to get it running manually (with root in the terminal), but starting from the GUI ends up in transmission not being able to access the files or read/save its state.

Answer 3 · 2021-01-02T12:21:12.000Z

I've added the ability to add shared folders through "resources". So if you want you should be able to build and use transmission from the dsm7 branch without root. Please let me know if there are any problems.

Running as root may damage your permissions, I don't recommend doing it. You have to manually reset the permissions later back the original owners of the files. You may also need to reinstall transmission.

Answer 4 · 2021-01-04T11:28:48.000Z

@publicarray seems to work beautifully now, thanks a lot. I noticed that conf/priviledge has "groupname" set to "sc-transmission" - shouldn't it be "sc-download"? Probably my mistake, sorry about that...

Answer 5 · 2021-01-04T11:47:33.000Z

@publicarray seems to work beautifully now, thanks a lot. I noticed that conf/priviledge has "groupname" set to "sc-transmission" - shouldn't it be "sc-download"? Probably my mistake, sorry about that...

how to install the transmission?

Answer 6 · 2021-01-04T16:10:19.000Z

Depends on what kind of model you want to run it on, but in general, you need to check out the latest dev version and compile the package yourself, then manually install it.

Check the guide here: https://github.com/SynoCommunity/spksrc#docker
Then you want to switch to the dsm7 branch: git checkout dsm7
Then you want to follow this guide: https://github.com/SynoCommunity/spksrc/wiki/Developers-HOW-TO#build-a-package

But you probably want to compile for a different architecture, so don't write make arch-88f6281. I have a DS216j, so I had to make arch-armada38x-7.0. The package will be built and will lie in spksrc/packages - you want to exit your docker container and docker cp it out. Then you load your DS GUI (in your browser), go to the package manager and manually upload that package.

Answer 7 · 2021-01-04T21:11:02.000Z

@zyrill the DSM7 has a new permission system. From my testing the group here does not show up in any GUI element (on a new system, I deleted the group from the GUI). However the user is shown in the GUI as a "system internal user". It appears that there are different groups. One set by the user for actual users and one for internal groups for packages, hidden.

Answer 8 · 2021-01-05T03:19:31.000Z

Sorry, it's closed by mistake

Answer 9 · 2021-01-05T03:20:52.000Z

@publicarray When is the update expected?We will not manually compile and install those that are not technically strong

Answer 10 · 2021-01-05T09:51:20.000Z

@jinfeng1985 I guess the answer is as always with community-driven open source projects: there is no ETA, if somebody has time and wants to work on it in their free time, they are going to eventually. If you need it now, you have to do it yourself or pay somebody to do it. Seeing as DSM 7 is still not productive but a beta, I think quite some patience is required.

Answer 11 · 2021-01-06T02:02:37.000Z

@zyrill Thanks, I could not have put it better myself.

While I have some packages that I have compiled on my machine and made public, they are intended for people that have technical know-how of some linux commands to fix things that may break,

We will not manually compile and install those that are not technically strong

Know that you are not the target audience (yet). But if you like to live dangerously: (packages are of alpha quality, only very limited testing in my enviroment, sample size of 1 etc.) https://seby.io/download/synology-7.0

Answer 12 · 2021-01-11T06:57:47.000Z

@publicarray I install the Jellyfin in the best list（https://seby.io/download/synology-7.0），is this version supported the hardware transcoding .Why do all the 4k movies prompt"The client is not compatible with media"

Answer 13 · 2021-01-11T09:05:59.000Z

@jinfeng1985 what NAS/ CPU are you trying this with? Did you configure the ffmpeg location to an ffmpeg that has hardware decoding (compiled with VAAPI) ? See below screenshot. Note especially 4k and up hardware acceleration may not work on some NASs: https://docs.google.com/spreadsheets/d/1MfYoJkiwSqCXg8cm5-Ac4oOLPRtCkgUxU0jdj3tmMPc

418play hardware acceleration Jellyfin screenshot (click on this text to show)

Answer 14 · 2021-01-11T09:22:34.000Z

@jinfeng1985 in the future can you create a new issue please? If it's related to packages that I released (not from synocommunity) you can create an issue here instead: https://github.com/publicarray/spksrc Thanks

Answer 15 · 2021-01-14T02:56:48.000Z

@publicarray already submit publicarray#26

Answer 16 · 2021-01-16T08:32:36.000Z

I’ve tried the precompiled binary transmission_x64-7.0_3.00-19.spk for my 718+ but I am unable to install because I am told that port 9091 is used or reserved for system use. I was getting it on an upgrade, so assumed it was the old install, but this is a new DSM install with hyper-backup config restored.

Any ideas what I can try to clear this? I‘ve ssh‘d in and tried sudo netstat -lp but nothing there.

Answer 17 · 2021-01-17T23:27:47.000Z

It's complaining about a pre-existing firewall rule. It must have been leftover after an uninstall, you can manually remove the binding:

sudo servicetool --remove-configure-file --package transmission.sc

Answer 18 · 2021-04-11T02:06:25.000Z

@publicarray thanks for transmission_armv7-7.0_3.00-19.spk (downloaded from https://seby.io/download/synology-7.0). Can confirm it works on DS216j 💪

Answer 19 · 2021-06-21T02:43:17.000Z

@publicarray thanks for transmission_armv7-7.0_3.00-19.spk (downloaded from https://seby.io/download/synology-7.0). Can confirm it works on DS216j 💪

yes, it works for me too, thanks

Answer 20 · 2021-06-24T20:51:46.000Z

@publicarray thanks for transmission_armv7-7.0_3.00-19.spk (downloaded from https://seby.io/download/synology-7.0). Can confirm it works on DS216j 💪

thanks a lot for a way to run it on dsm 7.0

Answer 21 · 2021-06-30T02:25:18.000Z

works for me to using the x64 package, thanks !

Answer 22 · 2021-06-30T14:29:38.000Z

no armv8 compatibility for DS220j ?

Answer 23 · 2021-06-30T15:24:16.000Z

DS220j

use transmission_aarch64-7.0_3.00-19.spk

Answer 24 · 2021-06-30T15:47:41.000Z

The package was detected by DSM but the installation failed

Edit :

Now he tells me he can't fix it

Answer 25 · 2021-07-03T08:37:59.000Z

Any chance of fixed packages being released now that DSM 7 is officially out? Trying to get it working on my DS120j...

Answer 26 · 2021-07-06T17:33:01.000Z

I'm trying to install the transmission_aarch64-7.0_3.00-19.spk package for the DS218play but I get an unidentified error.
Is there any way to install the package through the console to get what the error is?

Answer 27 · 2021-07-08T03:47:45.000Z

Thanks a bunch for the recompiled versions. The x64 version appears to be up and running on my 918+, although I did have to clear the firewall rule (as above) using sudo servicetool --remove-configure-file --package transmission.sc but fine after that.

Legend!

Answer 28 · 2021-07-08T22:45:54.000Z

Can't install the transmission_aarch64-7.0_3.00-19.spk package too on my DS418. Got "failed installation" at the end. Does someone find any fix for that pls ?

Answer 29 · 2021-07-13T12:32:08.000Z

Can't install the transmission_aarch64-7.0_3.00-19.spk package too on my DS418. Got "failed installation" at the end. Does someone find any fix for that pls ?

Please be patient as the DSM7 packages are not officially released yet and are hence unsupported. If somebody finds the time and wants to help you, you may support the analysis by providing all relevant logs. The "Failed installation" message is not sufficient to analyze what went wrong.

Answer 30 · 2021-07-14T00:04:26.000Z

you should try to install transmission using docker. After going through the same issue (see above) I finally decided to give docker a try, it's super easy and no more package not updated and/or "installation failed" anymore !

Answer 31 · 2021-07-14T00:23:10.000Z

On my end, I wish I could try. But from what I understand, my ds218j doesn't support docker. I'm hoping it can be updated eventually, just grateful for those who are working on it and following this thread for any news.

Answer 32 · 2021-07-16T09:01:43.000Z

@zyrill Thanks, I could not have put it better myself.

While I have some packages that I have compiled on my machine and made public, they are intended for people that have technical know-how of some linux commands to fix things that may break,

We will not manually compile and install those that are not technically strong

Know that you are not the target audience (yet). But if you like to live dangerously: (packages are of alpha quality, only very limited testing in my enviroment, sample size of 1 etc.) https://seby.io/download/synology-7.0

THANK. YOU. Works well, had to uninstall twice and run the port clear command twice before it worked but everything is right how I left it, perfect!

Answer 33 · 2021-07-19T20:33:47.000Z

Команда sudo servicetool --remove-configure-file --package transfer.sc дает ошибку:
remove configure file fail! file=transfer.sc error=[0x0700 servise_conf_remove.c:111]

Answer 34 · 2021-07-21T00:53:30.000Z

@OldBrave You can also find the transfer.sc file in /usr/local/etc/services.d/ but if the file is missing maybe a restart is enough?

Answer 35 · 2021-07-21T17:35:55.000Z

Thank you! There is transmission.sc at the specified address:[transmission]title = "Transmission"desc = "Transmission"port_forward = "yes"dst.ports = "9091 / tcp"Should it be removed?21.07.2021, 03:53, "Sebastian Schmidt" ***@***.***>: @OldBrave You can also find the transfer.sc file in /usr/local/etc/services.d/ but maybe a restart is enough? And, lo and behold! In the command "sudo servicetool --remove-configure-file --package transfer.sc" renamed transfer.sc -> transmission.sc and the remaining service was removed. Next, install as described above and everything worked! Thanks for the help!

Answer 36 · 2021-07-25T12:25:08.000Z

Hi, I've tried to download the package directly through console using sudo synopkg install transmission_aarch64-7.0_3.00-19.spk.

All I got was the following error message:

{
   "error":{
      "code":0
   },
   "results":[
      {
         "action":"repair",
         "beta":false,
         "betaIncoming":false,
         "error":{
            "code":278,
            "description":"\"failed to acquire postinst worker\"",
            "worker_msg":[
               
            ]
         },
         "finished":true,
         "installReboot":false,
         "installing":true,
         "language":"enu",
         "last_stage":"postupgrade",
         "package":"transmission",
         "packageName":"Transmission",
         "pid":20622,
         "scripts":[
            {
               "code":0,
               "message":"",
               "type":"preupgrade"
            },
            {
               "code":0,
               "message":"",
               "type":"preuninst"
            },
            {
               "code":0,
               "message":"",
               "type":"postuninst"
            },
            {
               "code":0,
               "message":"",
               "type":"preinst"
            },
            {
               "code":0,
               "message":"",
               "type":"postinst"
            },
            {
               "code":0,
               "message":"",
               "type":"postupgrade"
            }
         ],
         "spk":"transmission_aarch64-7.0_3.00-19.spk",
         "stage":"install_failed_and_stopped",
         "status":"broken",
         "success":false,
         "username":""
      }
   ],
   "success":false
}

The synopkg log file gives me this:

2021/07/25 14:22:43 Installing flag of [transmission] exists.
2021/07/25 14:22:43 upgrade transmission 3.00-19 Begin preupgrade
2021/07/25 14:22:43 upgrade transmission 3.00-19 End preupgrade ret=[0]
2021/07/25 14:22:43 upgrade transmission 3.00-19 Begin preuninst
2021/07/25 14:22:43 upgrade transmission 3.00-19 End preuninst ret=[0]
2021/07/25 14:22:43 Release systemd-unit for transmission when 0x0002 (ready)
2021/07/25 14:22:43 Release systemd-unit for transmission when 0x0002 (done)
2021/07/25 14:22:43 upgrade transmission 3.00-19 Begin /bin/rm -rf /volume1/@appstore/transmission
2021/07/25 14:22:43 upgrade transmission 3.00-19 End /bin/rm -rf /volume1/@appstore/transmission ret=[0]
2021/07/25 14:22:43 upgrade transmission 3.00-19 Begin /bin/rm -rf /volume1/@apptemp/transmission
2021/07/25 14:22:44 upgrade transmission 3.00-19 End /bin/rm -rf /volume1/@apptemp/transmission ret=[0]
2021/07/25 14:22:44 Release data-share for transmission when 0x0002 (ready)
2021/07/25 14:22:44 Release data-share for transmission when 0x0002 (done)
2021/07/25 14:22:44 Release data-share for transmission when 0x0002 (ready)
2021/07/25 14:22:44 Release data-share for transmission when 0x0002 (done)
2021/07/25 14:22:44 Release data-share for transmission when 0x0002 (ready)
2021/07/25 14:22:44 Release data-share for transmission when 0x0002 (done)
2021/07/25 14:22:44 upgrade transmission 3.00-19 Begin postuninst
2021/07/25 14:22:44 upgrade transmission 3.00-19 End postuninst ret=[0]
2021/07/25 14:22:44 upgrade transmission: Uninstall 3.00-19 successfully
2021/07/25 14:22:44 Acquire data-share for transmission when 0x0002 (ready)
2021/07/25 14:22:44 Acquire data-share for transmission when 0x0002 (done)
2021/07/25 14:22:44 upgrade transmission 3.00-19 Begin preinst
2021/07/25 14:22:44 upgrade transmission 3.00-19 End preinst ret=[0]
2021/07/25 14:22:44 upgrade transmission 3.00-19 Begin /bin/mkdir -p /volume1/@appstore/transmission
2021/07/25 14:22:44 upgrade transmission 3.00-19 End /bin/mkdir -p /volume1/@appstore/transmission ret=[0]
2021/07/25 14:22:44 upgrade transmission 3.00-19 Begin /bin/rm -rf /volume1/@appstore/transmission
2021/07/25 14:22:44 upgrade transmission 3.00-19 End /bin/rm -rf /volume1/@appstore/transmission ret=[0]
2021/07/25 14:22:44 upgrade transmission 3.00-19 Begin /bin/mv -f /volume1/@tmp/pkginstall/extract.LOxNRy/package /volume1/@appstore/transmission
2021/07/25 14:22:44 upgrade transmission 3.00-19 End /bin/mv -f /volume1/@tmp/pkginstall/extract.LOxNRy/package /volume1/@appstore/transmission ret=[0]
2021/07/25 14:22:44 upgrade transmission 3.00-19 Begin /bin/rm -rf /var/packages/transmission
2021/07/25 14:22:45 upgrade transmission 3.00-19 End /bin/rm -rf /var/packages/transmission ret=[0]
2021/07/25 14:22:45 upgrade transmission 3.00-19 Begin /bin/mkdir -p /var/packages/transmission
2021/07/25 14:22:45 upgrade transmission 3.00-19 End /bin/mkdir -p /var/packages/transmission ret=[0]
2021/07/25 14:22:45 upgrade transmission 3.00-19 Begin /bin/touch /var/packages/transmission/installing
2021/07/25 14:22:45 upgrade transmission 3.00-19 End /bin/touch /var/packages/transmission/installing ret=[0]
2021/07/25 14:22:45 upgrade transmission 3.00-19 Begin /bin/mv -f /volume1/@tmp/pkginstall/extract.LOxNRy/INFO /var/packages/transmission/INFO
2021/07/25 14:22:45 upgrade transmission 3.00-19 End /bin/mv -f /volume1/@tmp/pkginstall/extract.LOxNRy/INFO /var/packages/transmission/INFO ret=[0]
2021/07/25 14:22:45 upgrade transmission 3.00-19 Begin /bin/rm -rf /var/packages/transmission/scripts
2021/07/25 14:22:45 upgrade transmission 3.00-19 End /bin/rm -rf /var/packages/transmission/scripts ret=[0]
2021/07/25 14:22:45 upgrade transmission 3.00-19 Begin /bin/mv -f /volume1/@tmp/pkginstall/extract.LOxNRy/scripts /var/packages/transmission/scripts
2021/07/25 14:22:45 upgrade transmission 3.00-19 End /bin/mv -f /volume1/@tmp/pkginstall/extract.LOxNRy/scripts /var/packages/transmission/scripts ret=[0]
2021/07/25 14:22:45 upgrade transmission 3.00-19 Begin /bin/rm -rf /var/packages/transmission/WIZARD_UIFILES
2021/07/25 14:22:45 upgrade transmission 3.00-19 End /bin/rm -rf /var/packages/transmission/WIZARD_UIFILES ret=[0]
2021/07/25 14:22:45 upgrade transmission 3.00-19 Begin /bin/mv -f /volume1/@tmp/pkginstall/extract.LOxNRy/WIZARD_UIFILES /var/packages/transmission/WIZARD_UIFILES
2021/07/25 14:22:45 upgrade transmission 3.00-19 End /bin/mv -f /volume1/@tmp/pkginstall/extract.LOxNRy/WIZARD_UIFILES /var/packages/transmission/WIZARD_UIFILES ret=[0]
2021/07/25 14:22:45 upgrade transmission 3.00-19 Begin /bin/rm -rf /var/packages/transmission/conf
2021/07/25 14:22:45 upgrade transmission 3.00-19 End /bin/rm -rf /var/packages/transmission/conf ret=[0]
2021/07/25 14:22:45 upgrade transmission 3.00-19 Begin /bin/mv -f /volume1/@tmp/pkginstall/extract.LOxNRy/conf /var/packages/transmission/conf
2021/07/25 14:22:45 upgrade transmission 3.00-19 End /bin/mv -f /volume1/@tmp/pkginstall/extract.LOxNRy/conf /var/packages/transmission/conf ret=[0]
2021/07/25 14:22:45 Acquire systemd-unit for transmission when 0x0002 (ready)
2021/07/25 14:22:45 Acquire systemd-unit for transmission when 0x0002 (done)
2021/07/25 14:22:45 Acquire data-share for transmission when 0x0002 (ready)
2021/07/25 14:22:45 Acquire data-share for transmission when 0x0002 (fail)
2021/07/25 14:22:48 upgrade transmission 3.00-19 Begin postinst
2021/07/25 14:22:49 upgrade transmission 3.00-19 End postinst ret=[0]
2021/07/25 14:22:49 upgrade transmission 3.00-19 Begin postupgrade
2021/07/25 14:22:49 upgrade transmission 3.00-19 End postupgrade ret=[0]
2021/07/25 14:22:49 upgrade transmission from 3.00-19 to 3.00-19 failed

Any ideas?

Answer 37 · 2021-07-26T11:34:59.000Z

The package failed to update/create a shared folder: Acquire data-share for transmission when 0x0002 (fail) what shared folder name did you use? Maybe try reinstalling with a different or default path.

Answer 38 · 2021-07-27T19:32:35.000Z

It's complaining about a pre-existing firewall rule. It must have been leftover after an uninstall, you can manually remove the binding:
sudo servicetool --remove-configure-file --package transmission.sc

many tnx !
now i can install on 418 play+
x64 version

Answer 39 · 2021-08-04T07:38:56.000Z

goddam, after installation i got lost all my torrents (but the files remained)!!!
how can i recover them?

Answer 40 · 2021-08-04T12:07:03.000Z

The package failed to update/create a shared folder: Acquire data-share for transmission when 0x0002 (fail) what shared folder name did you use? Maybe try reinstalling with a different or default path.

Well ... as I specified I didn't configure anything during the install, it's just using the default parameters.

Answer 41 · 2021-08-04T22:20:07.000Z

@lovk1y that is unfortunate. We always try to avoid any issues like that. Unfortunately There is no way to recover package files unless you scann your entire raid or have backups. Do you have logfiles that explain how this happened?

@clemthi can you install the package manually using the GUI? I suspect that when using the command line you don't get the install wizard wich sets the shared folder name. Without that the install fails.

Answer 42 · 2021-08-05T00:18:00.000Z

Hi,

I'm having exactly the same issue @clemthi is having. Same version, same logs etc…

I tried using the GUI with the install wizard, chose the default directory /volume1/downloads, still having the error Acquire data-share for transmission when 0x0002 (fail)

I tried after adding read/write permissions to sc-transmission user on the directory, still having the same error.

Answer 43 · 2021-08-05T08:51:21.000Z

@lovk1y that is unfortunate. We always try to avoid any issues like that. Unfortunately There is no way to recover package files unless you scann your entire raid or have backups. Do you have logfiles that explain how this happened?

well, that's easy, i deleted Transmission from the package center because the previous version didn't work on the new DSM 7. i saw advice somewhere, that i have to do that before installing a new one (from https://seby.io/download/synology-7.0). there also have been said that i will have a choice to save the settings, but there was none :(

Answer 44 · 2021-08-05T16:05:35.000Z

@lovk1y that is unfortunate. We always try to avoid any issues like that. Unfortunately There is no way to recover package files unless you scann your entire raid or have backups. Do you have logfiles that explain how this happened?

I also lost all my torrents :( In my case, I kept clicking "Repair" and it was failing, so I decided to try deleting and re-installing, and I suspect that deleting the package wiped all the data. And DSM upgrade didn't even make a btrfs snapshot before the upgrade :(

Answer 45 · 2021-08-06T15:20:49.000Z

I also lost all my torrents :( In my case, I kept clicking "Repair" and it was failing, so I decided to try deleting and re-installing, and I suspect that deleting the package wiped all the data. And DSM upgrade didn't even make a btrfs snapshot before the upgrade :(

yep, it sucks!

Answer 46 · 2021-08-07T07:38:02.000Z

Thank you for this thread! I checked the release notes for DSM 7 and - not seeing transmission on there - foolishly thought it was safe to upgrade. I'm now only slightly regretting that choice, as I have been (apparently) successful in installing transmission_aarch64-7.0_3.00-19.spk as linked above.

The DSM Package Manager now says it is "running", and at least one tracker website on which I had active torrents says that my seeding torrents have updated in the past few minutes, so I have reason to believe the service is running (and my technique of backing up the app's "var" directory, then restoring that directory, has been successful in restoring all running torrents). There is just one problem: the web admin interface won't load. It doesn't refuse the connection (like it does if I choose any other port), or generate an error message, it just starts the connection with the web interface but never loads anything.

My steps so far have been:

Upgrade my DS418 to DSM 7.0-41890
Discover Transmission wouldn't work (prompted to "Repair")
Sweated a little
Attempted to use the Repair button, but of course it failed immediately
Swore, googled, found this page
Breathed a tentative sigh of relief, read through the various posts here
Made a tar backup of the var directory so I could restore torrents after uninstalling the dead version and installing the new version
Used Package Manager to uninstall the non-working Transmission (completed with no errors)
Used Package Manager to do a "manual" install of the downloaded transmission_aarch64-7.0_3.00-19.spk package (completed with no errors, and started running)
Used Package Manager to stop the Transmission service
Restored the Transmission "var" directory from the tar backup, and changed user/group ownership to match other installed files (all "sc-transmission", although I note that user does not appear at all in the Users & Groups Control Panel)
Used Package Manager to start the Transmission service
Attempted to load the web interface for Transmission

I've looked in the Log Center viewer, but there aren't any apparent system-level errors appearing there. Is there another logfile I should look for to discover why the web interface might be failing to respond? All of my existing torrents are working, but I would really like to be able to access the web interface again... it's not terribly useful without it.

Answer 47 · 2021-08-07T09:58:11.000Z

If the web interface does not load, you can change port 9091 to 9092, which worked for me earlier and will check access rights. I am uploading TransGUI on port 9091 from the Transmit-demon user.
If the web interface is loading, but there are no previously installed torrent files, then you should check the specified paths and write permissions for them.
If there are no previously installed torrent files in the working web interface, then you should download them again and specify the download path to the actually existing downloaded files and run such a torrent file in hash check mode. It takes a long time, but what to do. This way you can restore everything.

Answer 48 · 2021-08-07T12:46:47.000Z

Thanks - I tried changing port 9091 to 9092, and that at least clued me into a problem I didn't know I had: the path I was restoring into (/volume1/@appstore/transmission/var) no longer seems to be the path used for the settings file (or torrent files, for that matter). So now I have located and restored the files to the correct directory (/volume1/@appdata/transmission), and that at least has it responding correctly to/loading the settings.json file, and all the existing torrent files. I can see this because the transmission.log file is appearing in that directory and being updated, so at least I get some info... but that's not giving any clues yet as to why the web interface is timing out/failing to respond. The behaviour remains identical when I change the port to 9092 (same as it was on 9091) - just sitting there doing nothing. The only error I've been able to see is in the web console, which - when it loaded the interface but with errors/no info, it said it had been unable to load "/transmission/rpc". But there is no corresponding message in transmission.log

Answer 49 · 2021-08-07T13:30:08.000Z

So I went away and left it... and it now appears to be fully working! So apparently after fixing those paths and starting it again, the answer was just "do nothing for quite a while".

I'd like to add my thanks to the folks who updated it - I'm now feeling a whole lot less foolish about my decision to upgrade the DSM!

Answer 50 · 2021-08-07T18:18:40.000Z

Thank you for this thread! I checked the release notes for DSM 7 and - not seeing transmission on there - foolishly thought it was safe to upgrade. I'm now only slightly regretting that choice, as I have been (apparently) successful in installing transmission_aarch64-7.0_3.00-19.spk as linked above.

The DSM Package Manager now says it is "running", and at least one tracker website on which I had active torrents says that my seeding torrents have updated in the past few minutes, so I have reason to believe the service is running (and my technique of backing up the app's "var" directory, then restoring that directory, has been successful in restoring all running torrents). There is just one problem: the web admin interface won't load. It doesn't refuse the connection (like it does if I choose any other port), or generate an error message, it just starts the connection with the web interface but never loads anything.

My steps so far have been:
1. Upgrade my DS418 to DSM 7.0-41890

2. Discover Transmission wouldn't work (prompted to "Repair")

3. Sweated a little

4. Attempted to use the Repair button, but of course it failed immediately

5. Swore, googled, found this page

6. Breathed a tentative sigh of relief, read through the various posts here

7. Made a tar backup of the var directory so I could restore torrents after uninstalling the dead version and installing the new version

8. Used Package Manager to uninstall the non-working Transmission (completed with no errors)

9. Used Package Manager to do a "manual" install of the downloaded `transmission_aarch64-7.0_3.00-19.spk` package (completed with no errors, and started running)

10. Used Package Manager to stop the Transmission service

11. Restored the Transmission "var" directory from the tar backup, and changed user/group ownership to match other installed files (all "sc-transmission", although I note that user does not appear at all in the Users & Groups Control Panel)

12. Used Package Manager to start the Transmission service

13. Attempted to load the web interface for Transmission
I've looked in the Log Center viewer, but there aren't any apparent system-level errors appearing there. Is there another logfile I should look for to discover why the web interface might be failing to respond? All of my existing torrents are working, but I would really like to be able to access the web interface again... it's not terribly useful without it.

Same Nas as you (DS418) with the same package : transmission_aarch64-7.0_3.00-19.spk. But the installation doesn't success. I don't know how to get informations or logs about this problem.

Answer 51 · 2021-08-08T09:26:10.000Z

Thank you for this thread! I checked the release notes for DSM 7 and - not seeing transmission on there - foolishly thought it was safe to upgrade. I'm now only slightly regretting that choice, as I have been (apparently) successful in installing transmission_aarch64-7.0_3.00-19.spk as linked above.
The DSM Package Manager now says it is "running", and at least one tracker website on which I had active torrents says that my seeding torrents have updated in the past few minutes, so I have reason to believe the service is running (and my technique of backing up the app's "var" directory, then restoring that directory, has been successful in restoring all running torrents). There is just one problem: the web admin interface won't load. It doesn't refuse the connection (like it does if I choose any other port), or generate an error message, it just starts the connection with the web interface but never loads anything.
My steps so far have been:
1. Upgrade my DS418 to DSM 7.0-41890

2. Discover Transmission wouldn't work (prompted to "Repair")

3. Sweated a little

4. Attempted to use the Repair button, but of course it failed immediately

5. Swore, googled, found this page

6. Breathed a tentative sigh of relief, read through the various posts here

7. Made a tar backup of the var directory so I could restore torrents after uninstalling the dead version and installing the new version

8. Used Package Manager to uninstall the non-working Transmission (completed with no errors)

9. Used Package Manager to do a "manual" install of the downloaded `transmission_aarch64-7.0_3.00-19.spk` package (completed with no errors, and started running)

10. Used Package Manager to stop the Transmission service

11. Restored the Transmission "var" directory from the tar backup, and changed user/group ownership to match other installed files (all "sc-transmission", although I note that user does not appear at all in the Users & Groups Control Panel)

12. Used Package Manager to start the Transmission service

13. Attempted to load the web interface for Transmission
I've looked in the Log Center viewer, but there aren't any apparent system-level errors appearing there. Is there another logfile I should look for to discover why the web interface might be failing to respond? All of my existing torrents are working, but I would really like to be able to access the web interface again... it's not terribly useful without it.
Same Nas as you (DS418) with the same package : transmission_aarch64-7.0_3.00-19.spk. But the installation doesn't success. I don't know how to get informations or logs about this problem.

In my case, DS414 (Marvell Armada processor) so I guess the package I should install is transmission_armv7-7.0_3.00-19.spk

Answer 52 · 2021-08-08T19:40:11.000Z

In my case, DS916+ so I guess the package I should install is transmission_armv7-7.0_3.00-19.spk

No, DS-916+ has an intel braswell cpu (x86_64) and you need transmission_x64-7.0_3.00-19.spk (see wiki Synology and SynoCommunity Package Architectures

Answer 53 · 2021-08-08T20:29:08.000Z

7. Made a tar backup of the var directory so I could restore torrents after uninstalling the dead version and installing

Can you please explain how to make the backup of the var directory? I guess you can only do it through SSH 'cause FileStation does not allow to see the system files.

Answer 54 · 2021-08-09T01:26:12.000Z

7. Made a tar backup of the var directory so I could restore torrents after uninstalling the dead version and installing
Can you please explain how to make the backup of the var directory? I guess you can only do it through SSH 'cause FileStation does not allow to see the system files.

Yes - I did all that through SSH. The old installation had files in /volume1/@appstore/transmission/var, but the new installation put the data/config/torrent files in /volume1/@appdata/transmission instead.

Answer 55 · 2021-08-09T01:28:43.000Z

Used Package Manager to uninstall the non-working Transmission (completed with no errors)

Used Package Manager to do a "manual" install of the downloaded transmission_aarch64-7.0_3.00-19.spk package (completed with no errors, and started running)

Same Nas as you (DS418) with the same package : transmission_aarch64-7.0_3.00-19.spk. But the installation doesn't success. I don't know how to get informations or logs about this problem.

Did uninstalling the old package work for you? If not, it sounds from other posts like there might be some manual clean-up required before attempting to install the new one. Is there any error message at all when the new one doesn't install, or does it appear to work and then just not work?

I can recommend an extra reboot after upgrading to DSM7. I found there were a couple of things that didn't quite come up right immediately after the first boot, but sorted themselves after the second.

Answer 56 · 2021-08-10T14:36:50.000Z

Used Package Manager to uninstall the non-working Transmission (completed with no errors)

Used Package Manager to do a "manual" install of the downloaded transmission_aarch64-7.0_3.00-19.spk package (completed with no errors, and started running)

Same Nas as you (DS418) with the same package : transmission_aarch64-7.0_3.00-19.spk. But the installation doesn't success. I don't know how to get informations or logs about this problem.

Did uninstalling the old package work for you? If not, it sounds from other posts like there might be some manual clean-up required before attempting to install the new one. Is there any error message at all when the new one doesn't install, or does it appear to work and then just not work?

I can recommend an extra reboot after upgrading to DSM7. I found there were a couple of things that didn't quite come up right immediately after the first boot, but sorted themselves after the second.

Did uninstalling the old package work for you ?

Yes. perfectly.

Is there any error message at all when the new one doesn't install, or does it appear to work and then just not work?

Nothing. When I'm starting the installation after entered all parameters before, i got this message : "failed package installation" & nothing more. I tried with default parameters too & no effect. I also cleaned Firewall rules like recommended in previous post & no effects too.

I can recommend an extra reboot after upgrading to DSM7. I found there were a couple of things that didn't quite come up right immediately after the first boot, but sorted themselves after the second.

Already did that multiple times. No effect.

Answer 57 · 2021-08-10T14:56:46.000Z

I've got a DS220+ running DSM 6.2.4-25556. I've installed Transmission via the 'Community' section in the Package Center and all works well. Should I hold off upgrading to version 7 for the moment then if Transmission isn't going to work afterwards ?

Answer 58 · 2021-08-11T17:14:32.000Z

I've got a DS220+ running DSM 6.2.4-25556. I've installed Transmission via the 'Community' section in the Package Center and all works well. Should I hold off upgrading to version 7 for the moment then if Transmission isn't going to work afterwards ?

Yes, that's the easiest option by far. Note that transmission isn't the only package that's currently not available for 7.0. Watch #4524 for when a 7.0-compatible version is available (namely, "Published" column).

Alternatively, you can download an unpublished version referenced in the comments above and install it manually after the upgrade.

In both cases I'd also recommend to backup transmission configs and data, either with tar or by making a btrfs snapshot of the main subvolume.

Answer 59 · 2021-08-11T18:21:48.000Z

Thanks @imax9000 - I'm going to hold off upgrading then for the timebeing until a new version of Transmission is released which looks to be in the works and hopefully won't be too long. Thanks !

Answer 60 · 2021-08-14T20:21:44.000Z

Hello, I'm in the same boat at many after DSM7. So far I manage to copy the var directory somewhere, but using sudo cp -r and not tar (didn't know that it would be an issue).
I manage to install the spk and it works (at least) but now I cannot restore the backup because of permissions issues. How can I set back the right permissions once I sudo cp -r back the var directory to /volume1/@appdata/transmission ?
Any help would be welcome, I give up for tonight, this DSM update is so frustrating like most major update in the past.

Answer 61 · 2021-08-15T14:58:54.000Z

Manual install is working for me on my DS918+ running DSM 7.0-41890 with all 750+ of my seeded torrents intact. I more or less followed the steps in #4313 (comment) but here's an updated step-by-step:

Make a tar backup of the var directory files:
cd /volume1/@appstore/transmission/var
sudo tar -czvf ~/trans-var-backup.tar.gz .
(assumes your apps are installed in volume1 as should be the case for most users)
Uninstall the old SynoCommunity Transmission package via the Package Center
Download a DSM 7.0 compatible Transmission package from https://seby.io/download/synology-7.0, take note of your Synology's architecture.
My DS918+ is x86_64 so I downloaded https://seby.io/download/synology-7.0/transmission_x64-7.0_3.00-19.spk.
Click on Manual Install in the Package Center window and browse for your downloaded Transmission package.
Follow the on screen steps. Note the last on screen step which talks about permissions for the System Internal User sc-transmission. Make sure this internal user has R/W permissions to all folders where you save the data of your torrents. The last on screen step provides a link on how to do this for DSM 7.
Stop the Transmission service by clicking on "Stop" in the Package Center for the Transmission app.
Restore the var directory files to /volume1/@appdata/transmission:
sudo tar -xzvf ~/trans-var-backup.tar.gz -C /volume1/@appdata/transmission
Change ownership of your restored files so Transmission can R/W them:
sudo chown -R sc-transmission:sc-transmission /volume1/@appdata/transmission
Start Transmission again via the Package Center.
Confirm Transmission is working by loading the web interface or connecting via the Remote GUI. It might take some time to load initially if you have many torrents.
As done by @DarthJapan and @mrjfilippo, it's probably necessary to restart your Synology device if Transmission doesn't seem to be working properly at first.

@ElucGeek, step 8 should do the trick for you.

Answer 62 · 2021-08-17T08:14:38.000Z

I have DS420j with DSM 7.0-41890 and I can confirm that it is working great. Only thing, that I have to do was restart of device, because earlier I have permission denied while starting torrent download process.

Answer 63 · 2021-08-17T09:57:57.000Z

Same as @DarthJapan . I followed @chris-ayala 's clear instructions, updated permissions, and restarted the machine just to be safe. It seems to be running just like before (DS218j), thanks!

Answer 64 · 2021-08-17T10:13:19.000Z

Glad to hear more success stories. Added a note about restarting which I did multiple times myself while trying to troubleshoot the exact steps.

Answer 65 · 2021-08-17T10:14:14.000Z

Manual install is working for me on my DS918+ running DSM 7.0-41890 with all 750+ of my seeded torrents intact. I more or less followed the steps in #4313 (comment) but here's an updated step-by-step:

1. Make a tar backup of the var directory files:
   `cd /volume1/@appstore/transmission/var`
   `sudo tar -czvf ~/trans-var-backup.tar.gz .`
   (assumes your apps are installed in `volume1` as should be the case for most users)

2. Uninstall the old SynoCommunity Transmission package via the Package Center

3. Download a DSM 7.0 compatible Transmission package from https://seby.io/download/synology-7.0, take note of your [Synology's architecture](https://github.com/SynoCommunity/spksrc/wiki/Synology-and-SynoCommunity-Package-Architectures).
   My DS918+ is x86_64 so I downloaded https://seby.io/download/synology-7.0/transmission_x64-7.0_3.00-19.spk.

4. Click on Manual Install in the Package Center window and browse for your downloaded Transmission package.

5. Follow the on screen steps. Note the last on screen step which talks about permissions for the System Internal User `sc-transmission`. Make sure this internal user has R/W permissions to all folders where you save the data of your torrents. The last on screen step provides a link on [how to do this for DSM 7](https://github.com/SynoCommunity/spksrc/wiki/Permission-Management).

6. Stop the Transmission service by clicking on "Stop" in the Package Center for the Transmission app.

7. Restore the var directory files to `/volume1/@appdata/transmission`:
   `sudo tar -xzvf  ~/trans-var-backup.tar.gz -C /volume1/@appdata/transmission`

8. Change ownership of your restored files so Transmission can R/W them:
   `sudo chown -R sc-transmission:sc-transmission /volume1/@appdata/transmission`

9. Start Transmission again via the Package Center.

10. Confirm Transmission is working by loading the web interface or connecting via the Remote GUI. It might take some time to load initially if you have many torrents.

11. As done by @DarthJapan and @mrjfilippo, it's probably necessary to restart your Synology device if Transmission doesn't seem to be working properly at first.

@ElucGeek, step 8 should do the trick for you.

Thanks for your detailled step. As I said, I didn't do the sudo tar -czvf ~/trans-var-backup.tar.gz . initially so my var directory has been copied in /volume1/public/transmission with sudo cp -r and now the original files are gone in the @appdata folder.

I tried to tar the file in the public folder and tar them back to the new folder. Then I did the sudo chown command as you instructed (I did tried before already) and then if I try to start back Transmission package it fails to start. If I try to cd to /volume1/@appdata/transmission I get this error: -sh: cd: transmission/: Permission denied

If I don't restore the data and install transmission then manually edit the settings.json I can run Transmission but without all my torrents. I tried to restore only the torrents folder (and restore folder) but it doesn't make them appear in Transmission after restart of the package.

Answer 66 · 2021-08-17T10:14:57.000Z

Glad to hear more success stories. Added a note about restarting which I did multiple times myself while trying to troubleshoot the exact steps.

When you say restarting, it's the complete NAS or just the transmission package?

Answer 67 · 2021-08-17T10:17:16.000Z

That would be restarting the NAS itself. I'm reading your previous reply, trying to figure out what's happening there.

Answer 68 · 2021-08-17T10:31:11.000Z

Thanks for your detailled step. As I said, I didn't do the sudo tar -czvf ~/trans-var-backup.tar.gz . initially so my var directory has been copied in /volume1/public/transmission with sudo cp -r and now the original files are gone in the @appdata folder.

I think doing sudo cp -r to your public folder as temporary place to keep the files is sufficient. Tar-ing to an archive file is just another way.

I tried to tar the file in the public folder and tar them back to the new folder. Then I did the sudo chown command as you instructed (I did tried before already) and then if I try to start back Transmission package it fails to start.

You didn't have to tar the files again. It was fine just to copy them directly from /volume1/public/transmission to /volume1/@appdata/transmission and then change ownership via chown.

If I try to cd to /volume1/@appdata/transmission I get this error: -sh: cd: transmission/: Permission denied

This is strange. /volume1/@appdata/transmission should at least have read permissions for all users which means you should be able to cd into this folder without sudo. Does ls -l /volume1/@appdata/transmission also give the same error? If so, can you do ls -l /volume1/@appdata and see what permissions are set to the transmission folder?

If I don't restore the data and install transmission then manually edit the settings.json I can run Transmission but without all my torrents. I tried to restore only the torrents folder (and restore folder) but it doesn't make them appear in Transmission after restart of the package.

It might be a permissions problem. Could you try the steps above to confirm your folder permissions?

Answer 69 · 2021-08-17T13:10:57.000Z

It might be a permissions problem. Could you try the steps above to confirm your folder permissions?

ls -l /volume1/@appdata/transmission gives "ls: cannot open directory '/volume1/@appdata/transmission': Permission denied"

ls -l /volume1/@appdata gives:

drwx------ 6 777 sc-transmission 4096 Aug 14 22:10 transmission

Thus I did chown -r 777 to see if it helps before that.

Is it really necessary to restart the NAS completely ? I never had situation where it was necessary in the past as far as I remember. I cannot restart right now as kids are watching videos out of it. I should try tonight, but I would be surprise and a bit frustrated if it works.

I tried once again to reinstall the package (with deletion of all data), sudo cp -r the file in the new transmission folder but I have immediately the issue that the moved folder cannot be open, even by the admin user I'm logged with.

So I did once again but I did run the package after install. Instead I open the transmission folder, did create manually the torrents and resume folders. chown them with sc-transmission, then I copy all the file in these folders from the backup to the new created folders. This time I can cd in them without error. Then I did chown sc-transmission on all files (with *) in both directory. And I reconfigured manually the settings.json. Then I run the app, the app run but still no torrents visible (unless it needs some time?? I have about 2000 torrents in the folder).

It's not the end of the world, I can start clean with the torrent, re-add manually the ones I really want to keep in seed. But I'm furstrated not to understand what's wrong.

Answer 70 · 2021-08-17T14:09:08.000Z

ls -l /volume1/@appdata/transmission gives "ls: cannot open directory '/volume1/@appdata/transmission': Permission denied"

ls -l /volume1/@appdata gives:

drwx------ 6 777 sc-transmission 4096 Aug 14 22:10 transmission

That is strange. Are the other folders in /volume1/@appdata like this too? The folders in here generally have a 755 permission (drwxr-xr-x). I'm not sure why the installation package would create the transmission folder like that. It shouldn't. Maybe someone more knowledgeable knows why that happened. But the user ownership of the folder is also strange because...

Thus I did chown -r 777 to see if it helps before that.

chown changes the ownership of the file/folder. Basically, you assigned the user "777" (which probably doesn't exist for you) to be the owner. To change permission, you'd use chmod 777. It is better to use "755" (drwxr-xr-x) for the transmission folder itself and the folders inside. I left out -r part because this will also change the file permissions too. It's better practice to have files as "664" (rw-rw-r--) depending on how the file will be used.

Here's how the contents of my /volume1/@appdata/transmission folder looks like:

drwxr-xr-x 1 sc-transmission sc-transmission      0 Aug 15 19:25 blocklists
-rw------- 1 sc-transmission sc-transmission    298 Aug 15 23:13 dht.dat
drwxr-xr-x 1 sc-transmission sc-transmission  71252 Aug 17 22:28 resume
-rw------- 1 sc-transmission sc-transmission   2325 Aug 15 23:16 settings.json
-rw------- 1 sc-transmission sc-transmission    149 Aug 17 22:28 stats.json
drwxr-xr-x 1 sc-transmission sc-transmission  72768 Aug 16 00:18 torrents
-rw-r--r-- 1 sc-transmissiodn sc-transmission 346910 Aug 17 22:31 transmission.log
-rw-rw-r-- 1 sc-transmission sc-transmission      5 Aug 15 23:16 transmission.pid

But you should not have to use chmod at all for this installation, just chown. I suggest the following:

Make sure you still have your transmission files safely stored somewhere like /volume1/public/transmission as you have done. It should more or less look like the set of files/folders listed above. I think the most important are: dht.dat, resume (folder), torrents (folder), and settings.json. (disclaimer: I'm not a transmission expert)
Uninstall transmission via the package center.
Delete /volume1/@appdata/transmission if it still exists:
sudo rm -fr /volume1/@appdata/transmission
Reinstall transmission following the instructions above. In particular (assuming the appropriate files/folders are in /volume1/public/transmission), sudo cp -r /volume1/public/transmission/* /volume1/@appdata/transmission. Then sudo chown -R sc-transmission:sc-transmission /volume1/@appdata/transmission.
As a check, do ls -l /volume1/@appdata once again to confirm the permissions of the transmission folder. If it is still 700 (drwx------), then some thing strange is going on and I'm not sure if I can help you with that.
If all is OK, you should be able to start the transmission service once again and check the web interface to see if your torrents load up. 2000+ torrents is a lot, so it may take a couple of minutes to connect (you may get timeout errors too). If it times out, just wait 10-20 mins or so, and try again.

Is it really necessary to restart the NAS completely ? I never had situation where it was necessary in the past as far as I remember. I cannot restart right now as kids are watching videos out of it. I should try tonight, but I would be surprise and a bit frustrated if it works.

I feel it is not completely necessary. I only did it in my case because I was still working out the exact steps. Other users mention that it helped. My thinking is that it just took time for transmission to reload all the torrents. In your case, a restart is not going to help until you try the above first.

It's not the end of the world, I can start clean with the torrent, re-add manually the ones I really want to keep in seed. But I'm furstrated not to understand what's wrong.

I hope the above works for you. I'm almost confident it should unless there's some other strange configuration that's making the package center create folders with weird permissions.

Answer 71 · 2021-08-17T14:25:15.000Z

I did exactly like your describe but the torrents doesn't load up, I have the Web-UI directly loaded empty. The only thing I could not restore is settings.json, otherwise I have a fail to start the package and fail to repair, so I redid the configuration manually again by copying all important parameters (and leaving the one I'm not sure or that should not be relevant). However everything looks as it should now:
Transmission folder is like this:
drwxr-xr-x 5 sc-transmission sc-transmission 4096 Aug 17 16:13 transmission
Inside it:
drwxr-xr-x 2 sc-transmission sc-transmission 4096 Aug 17 15:05 blocklists -rw------- 1 sc-transmission sc-transmission 1793 Aug 17 16:12 dht.dat drwxr-xr-x 2 sc-transmission sc-transmission 86016 Aug 17 15:04 resume -rw------- 1 sc-transmission sc-transmission 2315 Aug 17 16:13 settings.json drwxr-xr-x 2 sc-transmission sc-transmission 81920 Aug 17 15:03 torrents -rw-r--r-- 1 sc-transmission sc-transmission 165959 Aug 17 16:13 transmission.log -rw-r--r-- 1 sc-transmission sc-transmission 5 Aug 17 16:13 transmission.pid
So it's exactly like yours without stats.json but I don't think this file is necessary.

As I said, at least I have a working Transmission again, so I might not touch and start from scratch with my torrents. It might be a good oppertunity to clean up the download folder (that is extremly messy) and by the way save some space, even if most video files should be symlink from my media folder, so not taking twice the space. It might be necessary as I'm running soon out of space on my NAS with all bay full.

Answer 72 · 2021-08-17T15:43:53.000Z

It sounds like the permissions are fine now. Are your settings in settings.json truly reflected in Transmission? If so, then Transmission appears to be accessing /volume1/@appdata/transmission fine now.

The resume and torrents folder are key for Transmission to reload all your torrents. Are they populated with 2000+ files? If they are, then I'm not sure what the problem is. I guess you can use this opportunity to clean up and restart torrents from scratch as you mentioned.

Answer 73 · 2021-08-20T12:22:12.000Z

I'm trying to run transmission on DSM218
I've downloaded https://seby.io/download/synology-7.0/transmission_armv7-7.0_3.00-19.spk and modified INFO file to support rtd1296 .
Everything is installed but it won't start . In transmission.log I have errors like

Fri Aug 20 14:15:17 CEST 2021
Starting transmission command /volume1/@appstore/transmission/bin/transmission-daemon -g /volume1/@appdata/transmission -x /volume1/@appdata/transmission/transmission.pid -e /volume1/@appdata/transmission/transmission.log
/var/packages/transmission/scripts/start-stop-status: line 75: /volume1/@appstore/transmission/bin/transmission-daemon: No such file or directory
transmission is not running

while
root@Synek:/volume1/@appdata/transmission# ls -ltr /volume1/@appstore/transmission/bin/transmission-daemon
-rwxr-xr-x 1 sc-transmission sc-transmission 445400 Aug 18 15:38 /volume1/@appstore/transmission/bin/transmission-daemon

What could cause that problem ? How can I solve it ?
@publicarray any suggestion ?

Answer 74 · 2021-08-21T09:34:58.000Z

@mgrkisiek you need the aarch64 version for your CPU. https://github.com/SynoCommunity/spksrc/wiki/Synology-and-SynoCommunity-Package-Architectures#x18-series

Answer 75 · 2021-08-21T19:22:28.000Z

@mgrkisiek you need the aarch64 version for your CPU. https://github.com/SynoCommunity/spksrc/wiki/Synology-and-SynoCommunity-Package-Architectures#x18-series

And that was my fault ...
I was looking at wrong page with cpu architecture . Everything is working perfect .

Answer 76 · 2021-08-24T06:58:28.000Z

@mgrkisiek ds218 and this package https://seby.io/download/synology-7.0/transmission_aarch64-7.0_3.00-19.spk works fine?? No problem??

Answer 77 · 2021-08-24T07:03:32.000Z

@mgrkisiek ds218 and this package https://seby.io/download/synology-7.0/transmission_aarch64-7.0_3.00-19.spk works fine?? No problem??

Yes. Works as expected.

Answer 78 · 2021-08-25T16:34:01.000Z

Hello
Do you have any clue when it will be officially released and available thru the Synolgy Community Package ?
Thank you in advance
Cheers

Answer 79 · 2021-08-25T17:02:40.000Z

Once all the open tickets and issues for DSM 7 releases have been adressed and most (all?) the packages are stable. You may check the progress here: #4524

…

________________________________ Von: Fandaor ***@***.***> Gesendet: Wednesday, August 25, 2021 6:34:12 PM An: SynoCommunity/spksrc ***@***.***> Cc: pkleinejaeger ***@***.***>; Mention ***@***.***> Betreff: Re: [SynoCommunity/spksrc] Can‘t start transmission on DSM7.0 (#4313) Hello Do you have any clue when it will be officially released and available thru the Synolgy Community Package ? Thank you in advance Cheers — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#4313 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAAIDWO7N3I6NZ2L63KB2I3T6ULQJANCNFSM4U5K2QNA>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>.

Answer 80 · 2021-08-29T18:46:31.000Z

Well, I downloaded and installed the arm7 package from https://seby.io/download/synology-7.0/ and that worked well. Unfortunately I blatantly uninstalled the old version of Transmission and lost the config. Oh well, my bad.

The installation of the new Transmission creates a shared folder in /volume1/downloads, which contains another folder called incomplete that stores the torrents being downloaded. After download is finished, Transmission wants to move the files to where I want them, eg: /volume1/media/downloads. But that does not work: "permission denied!"

More specifically: Unable to create directory for new file: Permission denied (torrent.c:3299)

I have set Read/Write permission on /volume1/media for user sc-transmission as explained here https://github.com/SynoCommunity/spksrc/wiki/Permission-Management#option-1---full-shared-folder-access but that has 0 effect.

I should also mention that I chowned the /volume1/media/downloads folder (plus sub folders) to sc-transmission:sc-transmission (ie: user and group sc-transmission) and chmoded everything under /volume1/media/ to 755.

Note that the previous version of Transmission didn't do this - it would download the torrent files directly to the target folder (eg: /volume1/media/downloads) with the .part extension. That extension would simply be removed after the download finished. This has always worked fine.

What am I missing? Any solution?

Answer 81 · 2021-08-29T22:08:20.000Z

The installation of the new Transmission creates a shared folder in /volume1/downloads, which contains another folder called incomplete that stores the torrents being downloaded.
Note that the previous version of Transmission didn't do this -

Yea we changed it to give an out of box experience that works when migrating from dsm6 to dsm7

if you really don't want that you can change the config file here /var/packages/transmission/var/settings.json

{
    "incomplete-dir-enabled": false,
    "watch-dir-enabled": false,
}

After download is finished, Transmission wants to move the files to where I want them, eg: /volume1/media/downloads

I tried this and it worked for me.

I should also mention that I chowned

Please don't Synology uses ACL:

This is what you should get with https://github.com/SynoCommunity/spksrc/wiki/Permission-Management#option-1---full-shared-folder-access

root@DSM7 /# synoacltool -get /volume1/downloads
ACL version: 1 
Archive: has_ACL,is_support_ACL 
Owner: [root(user)] 
--------------------- 
	 [0] group:administrators:allow:rwxpdDaARWc--:fd-- (level:0)
	 [1] user:sc-transmission:allow:rwxpdDaARWc--:fd-- (level:0)
	 [2] group::allow:rwxpdDaARWc--:fd-- (level:0)

root@DSM7 /# synoacltool -get /volume1/media
ACL version: 1 
Archive: has_ACL,is_support_ACL 
Owner: [root(user)] 
--------------------- 
	 [1] user:sc-transmission:allow:rwxpdDaARWc--:fd-- (level:0)
         [..]
	 [7] group:administrators:allow:rwxpdDaARWc--:fd-- (level:0)

root@DSM7 /# synoacltool -get /volume1/media/download
ACL version: 1 
Archive: is_inherit,is_support_ACL 
Owner: [seby(user)] 
--------------------- 
	 [1] user:sc-transmission:allow:rwxpdDaARWc--:fd-- (level:1)
         [..]
	 [7] group:administrators:allow:rwxpdDaARWc--:fd-- (level:1)

This is what you should get with https://github.com/SynoCommunity/spksrc/wiki/Permission-Management#option-2---per-folder-access:

root@DSM7 /# synoacltool -get /volume1/downloads
ACL version: 1 
Archive: has_ACL,is_support_ACL 
Owner: [root(user)] 
--------------------- 
	 [0] group:administrators:allow:rwxpdDaARWc--:fd-- (level:0)
	 [1] user:sc-transmission:allow:rwxpdDaARWc--:fd-- (level:0)
	 [2] group::allow:rwxpdDaARWc--:fd-- (level:0)
         [..]

root@DSM7 /# synoacltool -get /volume1/media
ACL version: 1 
Archive: has_ACL,is_support_ACL 
Owner: [root(user)] 
--------------------- 
	 [1] group:administrators:allow:rwxpdDaARWc--:fd-- (level:0)
	 [2] user:sc-transmission:allow:r-x----------:fd-- (level:0)
         [..]

root@DSM7 /# synoacltool -get /volume1/media/download
ACL version: 1 
Archive: is_inherit,has_ACL,is_support_ACL 
Owner: [seby(user)] 
--------------------- 
	 [0] user:sc-transmission:allow:rwxpdDaARWc--:fd-- (level:0)
	 [1] group:administrators:allow:rwxpdDaARWc--:fd-- (level:1)
	 [2] user:sc-transmission:allow:r-x----------:fd-- (level:1)
         [..]

Can you confirm these are the permissions you set?

Answer 82 · 2021-08-30T18:06:51.000Z

Thanks for the response @publicarray, that helped. I think the root of the problem was that the /volume1/media folder has been created before DSM7 and I have been unable to set the appropriate permissions. I've created a new destination shared folder and had no problems since. Had to reload shares on my NVidia Shield for the new share to show up, but it's been smooth sailing since: Transmission can write, Plex can read, and Shield can find. All's good now. :)

Answer 83 · 2021-09-03T09:42:34.000Z

Thought I'd leave a quick note to say that I have now upgraded to DSM 7.0-41890 on my DS220+. I fully uninstalled my current transmission installation and did a clean manual install of transmission 7 from the website listed in one of the posts above. I added the additional permissions in the shared folder section and on the downloads folder and besides me forgetting that synology is case sensitive on the folder names ( Downloads rather than downloads ) everything seems to be running smoothly.

Answer 84 · 2021-09-18T09:39:02.000Z

Hey all, new to the community and inexperienced. Was intending to upgrade to DSM7 but not keen to without Transmission. I've read this thread and #4524 and appreciate the information, but not confident I fully understand what is required, so perhaps best in my case to wait for Transmission to become available in the synocommunity section of Package Center.

Am I correct in understanding that although #4524 indicates Transmission is published, that doesn't indicate it is available in the synocommunity section of Package Center in DSM7?

Answer 85 · 2021-09-18T11:24:02.000Z

Hi @ihatethinkin I'm not sure if I understand your question. When a package is listed as published it will show up in the package center.

Answer 86 · 2021-09-18T11:33:55.000Z

Hi @ihatethinkin I'm not sure if I understand your question. When a package is listed as published it will show up in the package center.

Oh I see, glad I asked. In that case I'm all good to upgrade to DSM7. Apologies for such a simple query, thanks for the reply!

Answer 87 · 2021-09-18T21:15:55.000Z

Hello
Do you have any hint when it will be possible to fix the 'Subdirecotry are not allowed' during installation, in a clean release, please ?
I really don't want to have another directory for downloads.

Thank you a thousand

Answer 88 · 2021-09-19T10:36:30.000Z

You can still set a custom folder in the transmission settings and manually set the correct permissions.

The install wizard is made on a compromise to fit DSM7's updated permission model, so unless someone (maybe you) has a brilliant idea on how to fix it, make it reliable and create a PR this won't change

Answer 89 · 2021-09-19T10:56:06.000Z

Hallo Sebastian,
Unfortunately I am not good at this.
I tried the solution you gave me.
When installing I set up 'BitTorrent' instead of 'download' as the download directory
When installed I went to the settings and changed it to '/volume1/MySyno/media/BitTorrent/' as the download directory.
But when I tried to reload some already dloaded files, it doesn't find them, and start to redownload them instead.
"Verify local Data" doesn't help at all.
Do you have any clue why ?

Thanks for the kind reply.

Answer 90 · 2021-09-19T13:36:09.000Z

The easiest way: in the Transmissionon GUI at the beginning, stop all torrens, set the old download directory, transfer the downloads to the new directory. Then set the new directory as the download directory and run the torrents. It may be necessary to update the hash for some downloads.

Answer 91 · 2021-09-19T13:44:26.000Z

The easiest way: in the Transmissionon GUI at the beginning, stop all torrens, set the old download directory, transfer the downloads to the new directory. Then set the new directory as the download directory and run the torrents. It may be necessary to update the hash for some downloads.

Hello OldBrave,
That's what I thought but didn't work. It still wants to check the 'download/incomplete' directory for existing file... Even if I create a '/volume1/MySyno/media/BitTorrent/incomplete' directory it doesn't work... it is really insisting on wokring with this 'volume1/download' architecture... It is driving me crazy ... :-)

Answer 92 · 2021-09-19T14:08:59.000Z

it is really insisting on wokring with this 'volume1/download' architecture... It is driving me crazy ... :-)

You can change that in the settings. See the message of @publicarray: #4313 (comment)

Answer 93 · 2021-09-19T14:21:23.000Z

Thanks Webtweakers,
Thing is : I am no Dev and I really don't know how to change this settings and then repackage this so I could manually reinstall the app ... :-/

Answer 94 · 2021-09-20T04:09:10.000Z

I haven't made the move to DSM7 yet, but intend to ASAP.

My primary concern is ensuring a smooth transition from my existing Transmission 3.00-19 install via package center on DSM 6.2.4-25556 Update 2. Can someone please point me to a step by step idiots guide (if such a guide exists) so I can be confident that my current seeded torrents remain intact after migrating to the new version?

I presume I need to follow many of the steps in this guide but am not familiar with some of the basics such as "tar backup of the var directory" which I presume I will need to do.

Apologies for the inexperience, which I can only assume makes for a frustrating read to most of you who have a much better idea of what you're doing! Really appreciate the guidance, thank you in advance.

Answer 95 · 2021-09-24T09:42:47.000Z

Having read and understood as much as I could I have transitioned to DSM7 successfully. The same can't be said for Transmission unfortunately.

I attempted to install Transmission from DSM7 package center which did not work (received error about incompatable version which seemed odd but presumably a conflict having not uninstalled prior DSM6 package centre version). Failing that I installed Docker and now have a functional transmission container, but with issues.

Unfortunately I blatantly uninstalled the old version of Transmission and lost the config. Oh well, my bad.

I read your explanation but decided to do the same regardless due to a conflict when attempting to install transmission in Docker. Figured I could painfully add all of my seeded torrents manually again if only I could get transmission working. Uninstalling the old incompatible package centre version of transmission removed the conflict (which in hindsight was likely only due to both installations using port 9091).

The installation of the new Transmission creates a shared folder in /volume1/downloads, which contains another folder called incomplete that stores the torrents being downloaded.

This is my experience, files stay within the "incomplete" folder once torrent has completed download successfully. Regardless of the folder I instruct transmission to download to, torrents always land in "incomplete" and stay there.

I have set Read/Write permission on /volume1/media for user sc-transmission as explained here https://github.com/SynoCommunity/spksrc/wiki/Permission-Management#option-1---full-shared-folder-access but that has 0 effect.

Also attempted option 1 with no success.

Note that the previous version of Transmission didn't do this - it would download the torrent files directly to the target folder (eg: /volume1/media/downloads)

Always worked for me too.

I think the root of the problem was that the /volume1/media folder has been created before DSM7 and I have been unable to set the appropriate permissions. I've created a new destination shared folder and had no problems since.

The next logical step for me but has not worked in my case. Whatever I attempt to change in terms of permissions, download locations, shared folders, files download to "incomplete" and remains there. Watch folder works as expected which surprised me.

Hoping someone can offer advice. I'm tempted to remove the Docker installation now I have it partially working and attempt the package centre version again, but seems two steps backwards.

So what is the obviously stupid thing I'm doing?

Answer 96 · 2021-11-18T20:52:23.000Z

spk is not available anymore.
There is some solution to install transmission directly on DSM? In docker network is limited. With transmission on dsm6 was able to 50MB/s downloas, but in docker I'm limited to 30MB/s max
Thanks'

Answer 97 · 2021-11-18T21:18:39.000Z

spk is not available anymore.

There is some solution to install transmission directly on DSM? In docker network is limited. With transmission on dsm6 was able to 50MB/s downloas, but in docker I'm limited to 30MB/s max

Thanks'

What makes you say that? It's been published here:

https://synocommunity.com/package/transmission

Please open a new issue this one is already long enough