DSM-G600, DNS-3xx and NSA-220 Hack Forum

KyleK · 2010-03-16 08:04:26

If you already have 1.91 installed, it is enough to just stop Transmission first, wait a couple of seconds, and then update to the new version:

Code:

$ /ffp/start/transmission.sh stop
(wait)
$ funpkg -u Transmission-1.92-1.tgz

beefy314 · 2010-03-16 08:38:08

Thanks : ) I've just upgraded! IS there anyway for me to find out if the version I'm using? How do I know it's already 1.92 from the gui?

studguy1 · 2010-03-16 08:53:31

It's not possible to find the version info from web interface.
Run this on command line (telnet/ssh)

Code:

transmission-remote -V

Last edited by studguy1 (2010-03-16 08:55:01)

Egoist · 2010-03-16 09:14:13

I'm sure this has been answered already but I couldn't find it. I run the whitelist command to include the normal 127.0.0.1 and my 192.168.2.* range. Yet I get error 403 when I try to access the page or through the remote gui. I edit the settings.json file then restart the service and I see my desired range isn't in the whitelist. WTF?

KRH · 2010-03-16 09:17:11

stop
edit
start

Egoist · 2010-03-16 09:25:58

Tried that. No dice. But it somehow magically decided to work. Next problem is that it will connect to the tracker no problem but won't actually transfer data.

Frans · 2010-03-16 13:38:07

1.92 doesn't fix my watch-dir problems: still stops adding torrents and stops logging after a few minutes.

krackpot · 2010-03-16 13:47:42

KRH wrote:
stop
edit
start

Egoist wrote:
Tried that. No dice. But it somehow magically decided to work. Next problem is that it will connect to the tracker no problem but won't actually transfer data.

& @KyleK,

I'm finding after upgrading from 1.73-7, that the current version overwrites my settings.json file to default values everytime I envoke "/ffp/start/transmission.sh start"

Not sure how I can fix this, or if this is supposed to happen or if I'm supposed to edit the .sh file to include the .json file explicitly?

EDIT: I tried chown'ing the file to root:root to prevent changes. Now I'm getting connection refused?

Last edited by krackpot (2010-03-16 13:56:52)

KyleK · 2010-03-16 14:06:39

studguy1 wrote:
It's not possible to find the version info from web interface.
Run this on command line (telnet/ssh)
Code:
transmission-remote -V

Actually, I believe the current Transmission version is shown in the preferences dialog of the web interface.
I can't check that right now since I can only access my Transmission via iPhone at the time, and that interface doesn't have the settings dialog :)

Frans · 2010-03-16 14:08:29

Yes since a few versions ago you can see the correct version in the preference dialog on the bottom left!

KyleK · 2010-03-16 14:09:48

KRH wrote:
stop
edit
start

Code:

1. edit
2. kill -SIGHUP `pidof transmission-daemon`

should work as well. No need to restart transmission.

Last edited by KyleK (2010-03-16 14:10:01)

KyleK · 2010-03-16 14:14:19

krackpot wrote:
KRH wrote:
stop
edit
start
Egoist wrote:
Tried that. No dice. But it somehow magically decided to work. Next problem is that it will connect to the tracker no problem but won't actually transfer data.
& @KyleK,

I'm finding after upgrading from 1.73-7, that the current version overwrites my settings.json file to default values everytime I envoke "/ffp/start/transmission.sh start"

Not sure how I can fix this, or if this is supposed to happen or if I'm supposed to edit the .sh file to include the .json file explicitly?

EDIT: I tried chown'ing the file to root:root to prevent changes. Now I'm getting connection refused?

You only need to modify the .sh file if you store your Transmission settings in a different location than /mnt/HD_a2/.transmission-daemon.
There is no good reason why the new version should overwrite your old settings with the defaults other than a corrupt settings.json to begin with.
Then again, a lot has changed between 1.73 and 1.92, so maybe Transmission stumbles over somthing in your .json file that it doesn't like.

Is anything mentioned in the logfile?

The settings.json must have the same owner as the user that starts it. By default, Transmission is started as user "nobody", but root can't access files that are owned by root.

You can send me your settings.json if you want, I'll investigate.

Last edited by KyleK (2010-03-16 14:15:12)

krackpot · 2010-03-16 15:24:32

KyleK wrote:
Is anything mentioned in the logfile?

The settings.json must have the same owner as the user that starts it. By default, Transmission is started as user "nobody", but root can't access files that are owned by root.

You can send me your settings.json if you want, I'll investigate.

Here's what I did:
-removed the package and the .transmission-daemon directory (rm -rf)
-reinstalled
-edited transmission.sh to change the user (according to my user/groups)
-ran "/ffp/start/transmission.sh start"
-stopped transmission
-copied over my old settings and checked permissions (didn't have to chown anything)
-started transmission again

This produced a favorable result as it works now.

The problem was:
"transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -t -u <username> -v <password> -a 127.0.0.1,192.168.*.*" (which I followed from the first page)

which I ran on the first reinstall/upgrade. That must have messed up some settings as it ran transmission as root.

Thanks for your offer to help, keep up the great work!

studguy1 · 2010-03-16 18:14:28

Frans wrote:
Yes since a few versions ago you can see the correct version in the preference dialog on the bottom left!

Yeah you are right..missed that.

krackpot wrote:
"transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -t -u <username> -v <password> -a 127.0.0.1,192.168.*.*" (which I followed from the first page)

Yeah you are right, running that command as root changes the onwership of settings.json to root and perms to 600, so when u run the transmission.sh (which runs as nobody) it cant read/write to settings.json any more

Run this command to fix the ownership everytime u run the above command

Code:

chown -R nobody:nobody /mnt/HD_a2/.transmission-daemon

Last edited by studguy1 (2010-03-16 22:18:59)

KyleK · 2010-03-16 18:51:17

I made some changes to the first post.
It now shows separate instructions for new users and those who are just updating.

Also, the initial command for starting transmission-daemon to set up the RPC whitelist is now displayed to run as user "nobody", which should fix the issue krackpot had.

Egoist · 2010-03-17 09:37:01

I still can't actually download anything from peers.

Logrus · 2010-03-17 10:47:57

Pls make correction in 1st post:

$ funkpkg -u Transmission-1.92-1.tgz

KyleK · 2010-03-17 15:38:12

Thanks, corrected.

It seems I was in a funk yesterday

KyleK · 2010-03-17 15:40:51

Egoist wrote:
I still can't actually download anything from peers.

With any torrent? Did you try something popular and fast, like OpenOffice or a Ubuntu ISO?
What does 'transmission-remote --port-test' say?
Have you set up and/or download limits? Be aware that a limit of 0 does not mean unlimited. It means 0kB/s.

Frans · 2010-03-17 15:43:13

KyleK did you had a chance to test the watch-dir / log problem? Is there another way to check why they both stop? They aren't running as anothr daemon or something like that right? I must just disable watch-dir and use Watchdog script instead...

KyleK · 2010-03-17 16:26:33

Sorry, I didn't get to that yet. I'll try to remember tonight after work

KyleK · 2010-03-17 19:57:08

Frans wrote:
KyleK did you had a chance to test the watch-dir / log problem? Is there another way to check why they both stop? They aren't running as anothr daemon or something like that right? I must just disable watch-dir and use Watchdog script instead...

I'm checking the watchdir feature right now and I cannot find any issue with it. I place a torrent in the watchdir folder, a couple of seconds later it is added Transmission.
I've done this with about 10 torrents now without a hiccup.
Can you elaborate on how it stops working for you?

You can find me on IRC at irc.freenode.net #transmission if need be.

Egoist · 2010-03-17 20:27:56

KyleK wrote:
Egoist wrote:
I still can't actually download anything from peers.
With any torrent? Did you try something popular and fast, like OpenOffice or a Ubuntu ISO?
What does 'transmission-remote --port-test' say?
Have you set up and/or download limits? Be aware that a limit of 0 does not mean unlimited. It means 0kB/s.

No sir. No limits or anything set. I get the error:

"Unexpected response: <h1>401 Unauthorized</h1>Unauthorized User

The thing is, the builtin client worked back on firmware 1.07 but fails, along with Transmission, after "upgrading" to 1.08

KyleK · 2010-03-17 20:43:13

When do you get the response "401 Unauthorized"? when your issue the port-check?

If it's an issue with the new 1.08 firmware I'm not sure I can be of much help, because I don't own the DNS-323. I have the Conceptronic CH3SNAS, which is equal in hardware but different in software.

Egoist · 2010-03-17 20:51:26

Yup. D-Link's support is useful as tits on a bull unfortunately.

DSM-G600, DNS-3xx and NSA-220 Hack Forum

Announcement

#1001 2010-03-16 08:04:26

Re: [REL] Transmission 1.3

Code:

#1002 2010-03-16 08:38:08

Re: [REL] Transmission 1.3

#1003 2010-03-16 08:53:31

Re: [REL] Transmission 1.3

Code:

#1004 2010-03-16 09:14:13

Re: [REL] Transmission 1.3

#1005 2010-03-16 09:17:11

Re: [REL] Transmission 1.3

#1006 2010-03-16 09:25:58

Re: [REL] Transmission 1.3

#1007 2010-03-16 13:38:07

Re: [REL] Transmission 1.3

#1008 2010-03-16 13:47:42

Re: [REL] Transmission 1.3

KRH wrote:

Egoist wrote:

#1009 2010-03-16 14:06:39

Re: [REL] Transmission 1.3

studguy1 wrote:

Code:

#1010 2010-03-16 14:08:29

Re: [REL] Transmission 1.3

#1011 2010-03-16 14:09:48

Re: [REL] Transmission 1.3

KRH wrote:

Code:

#1012 2010-03-16 14:14:19

Re: [REL] Transmission 1.3

krackpot wrote:

KRH wrote:

Egoist wrote:

#1013 2010-03-16 15:24:32

Re: [REL] Transmission 1.3

KyleK wrote:

#1014 2010-03-16 18:14:28

Re: [REL] Transmission 1.3

Frans wrote:

krackpot wrote:

Code:

#1015 2010-03-16 18:51:17

Re: [REL] Transmission 1.3

#1016 2010-03-17 09:37:01

Re: [REL] Transmission 1.3

#1017 2010-03-17 10:47:57

Re: [REL] Transmission 1.3

#1018 2010-03-17 15:38:12

Re: [REL] Transmission 1.3

#1019 2010-03-17 15:40:51

Re: [REL] Transmission 1.3

Egoist wrote:

#1020 2010-03-17 15:43:13

Re: [REL] Transmission 1.3

#1021 2010-03-17 16:26:33

Re: [REL] Transmission 1.3

#1022 2010-03-17 19:57:08

Re: [REL] Transmission 1.3

Frans wrote:

#1023 2010-03-17 20:27:56

Re: [REL] Transmission 1.3

KyleK wrote:

Egoist wrote:

#1024 2010-03-17 20:43:13

Re: [REL] Transmission 1.3

#1025 2010-03-17 20:51:26

Re: [REL] Transmission 1.3

Board footer