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

DaCypressMan wrote:

Hi Kylek,

I have got a little problem with my Transmission. I had insatlled it on my Planex NAS an it works but after a day, sometimes less or more than a day, Transmission closses its session. So I have to restart it and then it works again. Why is it doing this and what can I change to solve this problem?

Regards

DaCypressMan

Good question. It shouldn't be doing that :)

Does the logfile hint at anything why it's shutting down?
Did Transmission crash or properly shutdown?

If the logfile doesn't reveal anything, I suggest starting it in foreground mode in a screen. This way you can close the ssh connection and check on it later and you'll see if and when it crashed/shut down.

please dont write in german in a public thread..

1. Install this.
2. Open a new screen by simply typing "screen".
3. Make sure Transmission is shutdown (/ffp/start/transmission.sh stop,  wait a little while)
4. Start Transmission in foreground:

$ transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon

5. You should see normal Transmission output right in the console. You can also check if it works correctly by accessing the web interface.
6. Quit the screen by pressing Ctrl-A,Ctrl-D (The console will say "[detached]")

Transmission now runs in the screen in the background, and you can close the ssh window.
When you notice Transmission doesn't work anymore (e.g. because the web interface is down), connect via ssh, then type 'screen -r'.
You'll see the last couple of logging from Transmission. Maybe it'll tell us something.


Send me a private message if you want to talk in German.

Well, 2.0.3 is still quitting without any error or reason after 2-5 minutes. I have reverted back to 1.9.3 which seems quite stable.

Last edited by cornelpopa (2010-07-25 23:44:48)

Hi all,

Can anyone provide guidedance on how to get Transmission working?
Been trying for the pass three days to no avail..

Sadly, I'm a total stranger to Linux. Hence, kindly list explaination in layman terms.

I am trying to get it working with Transmission-remote as a GUI to view the torrents.

Files installed:

Funpkg 0.5
Transmission-2.01-1.tgz
curl-7.18.1.tgz

I am able to login using web interface, thru SSH via PuTTy and using Transmission Remote UI. Torrent was able to be added, trackers are able to connect and download was able to initiate.

However, in the beginning, the torrents auto paused itself after downloading for a few seconds.
The error returned was No space left

After creating a new folder using 'mkdir' and setting it as a download folder, the error return saying permission denied /home/nobody/torrent name...

I also tried uninstallation and reinstallation with restarting of the NAS

Now when I try to uninstall, it echoed Transmission-2.01-1.tgz already installed


Please help.

Thanks Kylek for the guide.

For the installation part, I am very sure that I used the correct triggers. However, it kept echoing that it's already installed.
I tried to use -r to remove and reinstall but it can't seem to work?

Apparently, what you have diagnosed was the correct plight that I was in.
However, I have no idea on the syntax to assign the rights.

Upon trying to do what you've advised yesterday, somehow my SSH access was denied.
I tried factory reset and even to the extent of reloading the firmware, the SSH permission denied issue remains.

I was then advised to format the hard disk and start from scratch.

Somehow this round, it works perfectly fine.

Thanks for the assistance rendered.

Last edited by OrThaDoX (2010-07-27 06:36:40)

KyleK wrote:

Hey guys,

Transmission v2.03 is up. Enjoy!

Good stuff! thank you, works beautifully.

First, chown should be done on nobody:501, not simply nobody.

Second, I don't understand why you use root password for Transmission. Just use another username and password. Try setting it manually on json file (my transmission doesn't save changes from the web interface) or rerun the command kylek said:
$ su nobody -c "transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -t -u <username> -v <password> -a 127.0.0.1,192.168.*.*"

Last edited by irotjaf (2010-08-07 19:42:47)

Of course, it may need "su nobody" before you run that command.

Maybe you dont need to install/uninstall stuff. I would investigate the issue like this:

Login through telnet and do:

cd /mnt/HD_a2/.transmission-daemon     ## to go in the daemon folder
ls -l                                                           ## will show you the user and group of all folders

In my NAS all folders are owned by user nobody group 501.

drwxr-xr-x    2 nobody   501          4096 Jul 13 23:32 blocklists
-rw-------    1 nobody   501           634 Jul 30 18:14 dht.dat
drwxr-xr-x    2 nobody   501          4096 Aug  7 21:42 resume
-rw-------    1 nobody   501          1884 Aug  1 07:53 settings.json
-rw-------    1 nobody   501           161 Aug  7 21:42 stats.json
drwxr-xr-x    2 nobody   501          4096 Aug  6 14:58 torrents
-rwxrwxrwx    1 nobody   501       3367325 Aug  7 21:42 transmission-daemon.log

If its not the case in yours try reseting with chown. Do the same in /mnt/HD_a2 to see who owns .transmission-daemon. And do the same for your Download folder, chown if necessary.



At the end open settings.json and edit the username you use.
    "rpc-username": "yourusername",
(or you can use the command line but "su nobody" first.

You may also want to check who owns the transmission process:

 cd /mnt/HD_a2/ffp/start/
ls -l

-rwxr-x---    1 root     root          767 Feb 20 06:59 transmission.sh (in my case)

Good luck.

P.s. Hope kylek will look my earlier post about transmission crashing.

Last edited by irotjaf (2010-08-08 05:01:23)

Try to:

1. Stop the daemon

/ffp/start/transmission-daemon.sh stop

2. Change ownership:

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

3. Verify the ownershqip is ok (nobody 501).

ls /mnt/HD_a2/.transmission-daemon -l
ls /mnt/HD_a2/Torrents -l

4. Double verify you dont have problems accessing the folders (open the one you couldn't access before.

5. Edit settings.json with Wordpad and change:
"rpc-username": "yourusername",

6. Cross the fingers.

7. Start the daemon:

/ffp/start/transmission-daemon.sh start

8. Download a new torrent and check you can access its folder/file.

Last edited by irotjaf (2010-08-08 08:11:04)

Weird. Randomly, I'm getting my old permission error again. I've been using user forge with the attached password in order to login into the Transmission web interface. Out of the blue I'm getting the unix user/nobody permission denied things again. When attempting to look at the settings.js0n file I'm getting access denied.

When I attempt to log in via Putty/SSH, (with both root and forge) I get

BusyBox v1.00-pre1 (2009.02.11-09:07+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

Typing help does nothing.

Weird, huh. Any ideas?


EDIT: Took five minutes out of my life to reinstall FFP and my NAS configurations, and everything seems okay. I wonder what I'm doing wrong, though. I don't want to be doing this every other day.

EDIT 2: "You need permission" is happening again. The only variable that I can think of is that I turned off my laptop for the night and then logged in this morning. Is there a special procedure I have to follow when turning my laptop? Any way around this?

I'm manipulating files exclusively through Windows 7, so could it be because I'm using Windows Explorer?

Permissions seem fine, but I can't touch the files.

drwxr-xr-x    2 nobody   501          4096 Jul 30 08:53 blocklists
-rw-------    1 nobody   501           544 Aug  7 19:20 dht.dat
drwxr-xr-x    2 nobody   501          4096 Aug 10 19:51 resume
-rw-------    1 nobody   501          1895 Aug 10 10:15 settings.json
-rw-------    1 nobody   501           158 Aug 10 19:51 stats.json
drwxr-xr-x    2 nobody   501          4096 Aug 10 13:06 torrents
-rw-r--r--    1 nobody   501          1614 Aug 10 10:14 transmission-daemon.log
root@GregBox1:~# ls /mnt/HD_a2/Torrents -l
drwxr-xr-x    2 nobody   501          4096 Aug 10 16:02 Heroic Age [Blu-Ray 720p]
drwxr-xr-x    2 nobody   501          4096 Aug 10 10:19 The.Forbidden.Kingdom

Last edited by Forge (2010-08-10 23:00:13)

I'm logging into Win7 x64 with my usual username and password, the same one I used to setup the initial configuration. When I check security settings for the folders, I see "Everyone", nobody (Unix User\nobody)", and "501 (Unix Group\501)". All three of those users/groups have Read-Write permission.


Oh Kyle, where art thou?