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

DasCrushinator · 2009-06-13 03:06:29

KyleK wrote:
You mean the configuration files?
The default /home/root sits on the RAM disk of the NAS, so every time you restart the NAS, they're wiped. Therefore it is best to place them on either of the hard disks (/mnt/HD_a2 is the default but /mnt/HD_b2 works as well if you have 2 disks), or you can even put the config files on a USB stick if you use one on the NAS.
Just open the file /ffp/start/transmission.sh with an editor and edit the path at the very top of the file.

Just to clarify, the files I am talking about are the Transmission-x.xx-1.tgz, Automatic-x.xx-1.tgz, etc.

KyleK · 2009-06-13 03:11:29

Those are the install packages. You can place them wherever you want (but remember, everything in /home/root gets wiped after a restart!).

After you install these packages via "funpkg -i Transmission-1.71-3.tgz", they're unpacked and their content is put in the appropriate places. The archives themselves (the .tgz files) are not needed at all anymore (unless you want to reinstall the app at a later time).

DasCrushinator · 2009-06-13 03:13:15

KyleK wrote:
Those are the install packages. You can place them wherever you want (but remember, everything in /home/root gets wiped after a restart!).

After you install these packages via "funpkg -i Transmission-1.71-3.tgz", they're unpacked and their content is put in the appropriate places. The archives themselves (the .tgz files) are not needed at all anymore (unless you want to reinstall the app at a later time).

Great! I think that solves all of my problems! Thanks again!

Edit: I spoke too soon

How do I go about adding torrents from sites that require certificates/SSL?

What folder does transmission watch for .torrent files in?

How do I add torrents through the GUI?

How can I view the GUI (or for that matter the DNS-323) securely from outside the network?

Last edited by DasCrushinator (2009-06-13 05:24:58)

mefmax · 2009-06-13 11:28:45

Hello, KyleK!
Please, help me with some trouble after transmission installation:
DNS-323, Transmission 1.71 (8654). I am install, configure and start it.
In log file I get an error
"Couldn't create "12.Raundov.2009.D.DVD/VTS_06_1.VOB": parent folder "/usr/share/ftp_server/Downloads" does not exist". But in config file signed a right path:

...
"download-dir": "\/mnt\/HD_b2\/Video_new",
...

command "su nobody -c "mkdir /mnt/HD_b2/Video_new/downloads" create a folder without problems,
command "su nobody -c "mkdir /mnt/HD_a2/.transmission-daemon/downloads" work too. It seems like daemon can't read a config file and use default path...
But editing path via web- interface work fine (=> daemon can read/write config). As result, I can't download any torrent

KyleK · 2009-06-13 12:35:47

How did you start Transmission? If you start it manually via the command-line, you have to tell it where to put the configuration files:

Code:

$ su nobody -c "transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -w /mnt/HD_b2/Video_new"

It will then put its config files in /mnt/HD_a2/.transmission-daemon, and download files to /mnt/HD_b2/Video_new.

muv · 2009-06-13 23:09:32

Soprano wrote:
I am getting constant crashing with this version. The latest log entry is: /ffp/bin/transmission-daemon: event.c: 875: timeout_next: Assertion `tv->tv_usec >= 0' failed.

Is anyone else having this issue, or how to fix this? It also seems to ignore the upload limit I have set.

I'm having the same! With the same message.
I suspect it happens after it stays idle from both download and client app requests for some time like 20-30 min. Just a guess.

Looking forward to getting any help on this thread...

KyleK · 2009-06-13 23:43:46

The cause for this has been found and the bug will be fixed in Transmission 1.72. As soon as that's out I'll have a new package ready.

muv · 2009-06-14 01:03:31

Hello,

KyleK wrote:
How did you start Transmission? If you start it manually via the command-line, you have to tell it where to put the configuration files:
Code:
$ su nobody -c "transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -w /mnt/HD_b2/Video_new"
It will then put its config files in /mnt/HD_a2/.transmission-daemon, and download files to /mnt/HD_b2/Video_new.

To mefmax and anybody else struggling with the same problem: I confirm that the settings work OK only when you specify them in the command line. I actually changed the transmission.sh specifying all the necessary parameters explicitly:

Code:

    su $user -c "$command -f -g ${TRANSMISSION_HOME} -a "127.0.0.1,192.168.*.*" -w /mnt/HD_a2/Downloads 1>${TRANSMISSION_HOME}/$name.log 2>&1 &"

I've spent a few hours getting to this (well, studying basics of linux at the same time ). None of the other variants seemed to work, like changing the settings in the /mnt/HD_a2/.transmission-daemon/settings.json or through the remote .NET client. Particularly with the download folder: even when both transmission-daemon -d and the Windows client showed it customized, it didn't want to download, aborting with the log message about not finding "/usr/share/ftp_server....".

Regarding the config file: now I understand that I should have tried to change it in /.config/ instead: the one in /mnt/HD_a2/.transmission-daemon gets overwritten after every exit.

muv · 2009-06-14 01:05:25

KyleK wrote:
The cause for this has been found and the bug will be fixed in Transmission 1.72. As soon as that's out I'll have a new package ready.

Nice to hear

mefmax · 2009-06-14 13:16:27

I solve my problem. Reason was in torrents - I add it to Transmission before reconfigure it.
It seems, like Transmission store path inside torrent's tasks, and after changing path in ini - it has no effect for old task. It is not a bug - it is right logic, sorry for spending attention.
After removing tasks and adding again downloading began.
PS:
I understand it after installing "Transmission Remote GUI" - nice tolls for lamers like Me )

Last edited by mefmax (2009-06-14 13:17:04)

muv · 2009-06-14 13:30:29

mefmax wrote:
I solve my problem. Reason was in torrents - I add it to Transmission before reconfigure it.
It seems, like Transmission store path inside torrent's tasks, and after changing path in ini - it has no effect for old task. It is not a bug - it is right logic, sorry for spending attention.
After removing tasks and adding again downloading began.
PS:
I understand it after installing "Transmission Remote GUI" - nice tolls for lamers like Me )

Sounds reasonable - the cause of my problems could be the same - actually this idea crossed my mind. I just didn't want to spend any more time on trying to reproduce it after I got it working.

Iznakurnog · 2009-06-14 17:29:38

maxim_fr wrote:
Very good news! I will surely test this one today...

Link to Experimental transmission build compiled for testing the patch on DNS-323 with ffp-05:
http://slil.ru/27748402

Was your test successful ? if so I think the ticket needs some votes/user's feedback to speed up application to official T
Please report to developers what we really need that improvement and what patched build works nice and smoothly ....

http://trac.transmissionbt.com/ticket/2196
and topic in forum
http://forum.transmissionbt.com/viewtop … amp;t=7253

And note for everyone who goes to try experimental build
Don' t forget to stop Transmission, set preallocation:3 in settings.json and start it again

I've tested experimental build thoroughly myself and I like it. Preinitialization of 30 GB BD-remux takes about 5-10 minutes
download to finish and yahoooo !!! I can watch the movie immediately from my NAS without any copying to new location

Last minute update:
There is new experimental version. Zero-patching code block now moved to fallback section under preallocation mode 2
You can take new build from link in ticket.

Last edited by Iznakurnog (2009-06-15 10:42:21)

Martin · 2009-06-15 09:43:05

Hi

I'm having a small problem adding torrents via gui;

I installed and ran this:

Code:

transmission-daemon -f -g /mnt/HD_a2/.transmission-daemon -t -u Mar
tin -v manina -a 127.0.0.1,192.168.1.40
[07:35:53.399] Couldn't bind port 51413 on 0.0.0.0: Address already in use
[07:35:53.424] RPC Server: Adding address to whitelist: 127.0.0.1
[07:35:53.427] RPC Server: Adding address to whitelist: 192.168.1.40
[07:35:53.435] RPC Server: Serving RPC and Web requests on port 9091
[07:35:53.436] RPC Server: Whitelist enabled
[07:35:53.436] RPC Server: Password required
[07:35:53.437] Transmission 1.71 (8654) started
[07:35:53.568] transmission-daemon: requiring authentication
[07:35:53.818] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
[07:35:53.819] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
poll: Interrupted system call
[07:35:59.652] Port Forwarding: State changed from "Not forwarded" to "Starting"
[07:35:59.661] Saved "/mnt/HD_a2/.transmission-daemon/settings.json"
[07:35:59.664] Port Forwarding: Stopped

Then uploaded a torrent via GUI, but it's not being added, nothing really happens..

I assume it's a chmod issue?

Martin · 2009-06-15 09:59:08

ok, since you didn't answer within 10 seconds I had a go my self I chown'ed all torrent folders (complete, incomplete, torresnts) and all is now well in regards to this particular problem

Logrus · 2009-06-17 16:07:45

1.72 is out!)
Better file preallocation on embedded systems!

http://www.transmissionbt.com/

Last edited by Logrus (2009-06-17 16:08:29)

KyleK · 2009-06-17 17:17:05

And you tell us this why?

KyleK · 2009-06-17 17:55:10

Transmission v1.72 up and running. Check out the first post for the changelog & link.

nickdns · 2009-06-17 18:34:50

For those that used the pre-allocation test version posted above, dont' forget to update this line in settings.json, in case you had it set at 3:

"preallocation": 2,

Otherwise transmission will fail with the following line in transmission-daemon.log:
/ffp/bin/transmission-daemon: session.c: 638: tr_sessionInitImpl: Assertion `tr_isPreallocationMode( i )' failed.

nickdns · 2009-06-17 18:36:18

KyleK wrote:
And you tell us this why?

Out of excitement I guess.. something new and shiny is out

Or in case someone wants to build from source

uyuni · 2009-06-17 23:49:15

I don't know when this was released but transmission-daemon now supports a watch-dir.
I tried adding a watch-dir setting to the settings.json file and it works (remember to shut down the transmission-daemon while you edit it!).
See some info on the settings.json file here: http://trac.transmissionbt.com/wiki/EditConfigFiles.
You need to add both watch-dir and watch-dir-enabled

carnifex · 2009-06-18 22:36:23

Thanks again KyleK: v1.72 up and running .

KyleK · 2009-06-18 23:11:37

uyuni wrote:
I don't know when this was released but transmission-daemon now supports a watch-dir.
I tried adding a watch-dir setting to the settings.json file and it works (remember to shut down the transmission-daemon while you edit it!).
See some info on the settings.json file here: http://trac.transmissionbt.com/wiki/EditConfigFiles.
You need to add both watch-dir and watch-dir-enabled

You can also set the watch-dir via an option to transmission-daemon or transmission-remote, I'm not sure which :)

Please note that the DNS-323 and the CH3SNAS currently do not support inotify, which means Transmission uses a fallback method to provide watchdir functionality. This fallback scans the given folder every couple of seconds or so, checking if there are any new .torrent files.

So if this watchdir is located on one of your harddrives, it'll never go to sleep.

This is why I've never actively promoted that feature. I planned to bring inotify support to the NAS (because it's there, the official UPnP clients use it), but I just don't know how it's been hacked into the kernel.

I still hope that Conceptronic releases new sources for the next firmware update (Denis promised), then I should know more.

deltoid · 2009-06-19 19:47:57

Hi,

I've installed the latest version of Transmission as per the instruction in the first post. My downloads just don't seem to start though. They sit there at 0%.

Things I've checked:
+ Port is open in the router
+ Directory permissions are correct
+ There are plenty of seeds/peers (the torrent works fine in uTorrent)

I'm stumped, I've rebooted my router and the NAS a few times now.

Code:

Here is what the log file says:
[03:12:28.455] RPC Server: Adding address to whitelist: 127.0.0.1
[03:12:28.455] RPC Server: Adding address to whitelist: 192.168.*.*
[03:12:28.457] RPC Server: Serving RPC and Web requests on port 9091
[03:12:28.458] RPC Server: Whitelist enabled
[03:12:28.458] RPC Server: Password required
[03:12:28.459] Transmission 1.72 (8702) started
[03:12:29.892] transmission-daemon: requiring authentication
[03:12:30.014] Loaded 1 torrents
[03:12:30.021] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
[03:12:30.022] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
[03:12:34.611] Port Forwarding (UPnP): Found Internet Gateway Device "http://192.168.1.254:2800/EmWeb/UPnP/Control/4"
[03:12:34.611] Port Forwarding (UPnP): Local Address is "192.168.1.240"
[03:12:34.842] Port Forwarding (UPnP): Port forwarding through "http://192.168.1.254:2800/EmWeb/UPnP/Control/4", service "urn:schemas-upnp-org:service:WANPPPConnection:1".  (local address: 192.168.1.240:51413)
[03:12:34.842] Port Forwarding (UPnP): Port forwarding successful!
[03:12:34.843] Port Forwarding: State changed from "Not forwarded" to "Forwarded"
[03:15:57.224] Linux.iso: Couldn't read resume file
[03:15:57.261] Linux.iso: Queued for verification
[03:15:57.264] Linux.iso: Verifying torrent
[03:16:18.315] Linux.iso: Queued for verification
[03:16:18.317] Linux.iso: Verifying torrent

Last edited by deltoid (2009-06-19 20:09:10)

obveron · 2009-06-23 20:17:58

Any observations on how Transmission's new features effect CPU and Memory usage on the 323? I thinking about making the jump from 1.61 to 1.72 but I'm not sure how DHT and other new stuff will effect performance. My 323 can barely handle Transmission as it is.

Last edited by obveron (2009-06-23 20:21:49)

maxim_fr · 2009-06-24 15:55:02

On my experience it depends not on version, but the number of torrents.

Upgade, it's safe And you can always roll back, if anything will heappen...

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

Announcement

#626 2009-06-13 03:06:29

Re: [REL] Transmission 1.3

KyleK wrote:

#627 2009-06-13 03:11:29

Re: [REL] Transmission 1.3

#628 2009-06-13 03:13:15

Re: [REL] Transmission 1.3

KyleK wrote:

#629 2009-06-13 11:28:45

Re: [REL] Transmission 1.3

#630 2009-06-13 12:35:47

Re: [REL] Transmission 1.3

Code:

#631 2009-06-13 23:09:32

Re: [REL] Transmission 1.3

Soprano wrote:

#632 2009-06-13 23:43:46

Re: [REL] Transmission 1.3

#633 2009-06-14 01:03:31

Re: [REL] Transmission 1.3

KyleK wrote:

Code:

Code:

#634 2009-06-14 01:05:25

Re: [REL] Transmission 1.3

KyleK wrote:

#635 2009-06-14 13:16:27

Re: [REL] Transmission 1.3

#636 2009-06-14 13:30:29

Re: [REL] Transmission 1.3

mefmax wrote:

#637 2009-06-14 17:29:38

Re: [REL] Transmission 1.3

maxim_fr wrote:

#638 2009-06-15 09:43:05

Re: [REL] Transmission 1.3

Code:

#639 2009-06-15 09:59:08

Re: [REL] Transmission 1.3

#640 2009-06-17 16:07:45

Re: [REL] Transmission 1.3

#641 2009-06-17 17:17:05

Re: [REL] Transmission 1.3

#642 2009-06-17 17:55:10

Re: [REL] Transmission 1.3

#643 2009-06-17 18:34:50

Re: [REL] Transmission 1.3

#644 2009-06-17 18:36:18

Re: [REL] Transmission 1.3

KyleK wrote:

#645 2009-06-17 23:49:15

Re: [REL] Transmission 1.3

#646 2009-06-18 22:36:23

Re: [REL] Transmission 1.3

#647 2009-06-18 23:11:37

Re: [REL] Transmission 1.3

uyuni wrote:

#648 2009-06-19 19:47:57

Re: [REL] Transmission 1.3

Code:

#649 2009-06-23 20:17:58

Re: [REL] Transmission 1.3

#650 2009-06-24 15:55:02

Re: [REL] Transmission 1.3

Board footer