Problem with Daemon 1.61 and FreeBSD

[paramount]

After upgrading to 1.61 my daemon doesn't work anymore. Including the web interface.

What is happening:

The daemon is not looking for my download directory.
In my settings.json, I have:
"download-dir": "\/inetpub\/bittorrents\/downloads",
Tried in the command line too:
transmission-daemon -f --download-dir /inetpub/bittorrents/downloads

But... nothing work.
When I start a new torrent, I get in the console (using the -f option):
[14:45:01.298] Port Forwarding: Port Forwarding
[14:45:15.189] MY_TORRENT: Got 18 peers from tracker
[14:45:24.409] Couldn't create "MY_TORRENT": parent folder "/root/Downloads" does not exist

It was working very well in the 1.60 version of Daemon.

And in the web interface, I can't add new torrents... as URL or upload file, nothing works. No error message, nothing. It simply not work.

To add a new torrent, I need to use the transmission-remote --add option.
So the file is added... and then it appers in the web interface. But It can't be downloaded because of the download directory.

So, I think that the two problems are related. Something with the paths.

What can be done? Or I'll need to came back to the 1.60 version ?

[paramount]

... after some work.

To get the download working, I made a symbolic link from /root/Downloads to /inetpub/bittorrents/downloads. And the downloads started ok.

But still can't add new torrents from the Web interface. Only from the transmission-remote.

And a new error appears when a download get completed:

Code: Select all

[16:54:12.871] MY_TORRENT: State changed from "State changed from "%s" to "%s"" to "State changed from "%s" to "%s""

I belive that there is some errors in the transmission-daemon.

[paramount]

Now I found a patch for the problem with Web GUI.

http://trac.transmissionbt.com/changeset/8400

I'll try to complie the new files and see what happens.

But what about the download directory problem? Someone got a clue for it?

[etlunatic]

Hi there,

I am using transmission Transmission 1.61 (8385) from ports in a jail on FreeBSD 7.2 without any problem.

I connect to the daemon with transmission-remote, www/transmission-web in ports and http://code.google.com/p/transmisson-remote-gui/.

Did you build from ports?

Under what user are you starting the daemon?

What are the rights of this user on /inetpub/bittorrents/downloads?

Regards

[paramount]

My Transmission 1.61 is from ports too.
The old 1.60 was from "ports" too... but I modified the ports (that was in 1.51) to compile the 1.60, because the port maintener was too late to make a working port for 1.60. It worked very good. Without problem.
When the 1.61 was release, the port maintener made a port for it. So I updated to 1.61.

And the transmission stopped.

I'm running it as root. Because I'm starting it at the boot using a rc.d script.

So I use the configuration "settings.json" to set the download directory. Which by default is "/root/Downloads", but in my configuration file is "/inetpub/bittorrents/downloads". It worked very fine until 1.61.

I really don't want to go back to 1.60, because it was slowing down my Firefox, in 1.61 is very fast. But I can't submit a torrent file using the upload. (this is documented and already corrected in the Transmission snapshot - I will try to generate a new port using this snapshot).

But I needed to make a symlink from /root/Downloads to /inetpub/bittorrents/downloads, to get it working.
The 1.61 is now accepting the Download Directory directive in the configuration file (and from command line too).

[etlunatic]

Running transmission under root is not a very good idea, especially since dht is around the corner.

Despite and against what has been said in this forum, the dht protocole is not very secured. I am using both rtorrent and transmission in a jail with sshd and ftpd disabled. With dht-enabled rtorrent, my logs showed frequent connection attempts to the same IP on ports 21 and 22. I had to cleanup the rtorrent dht cache several times as I suspected some bots there.

Anyway here is my rc.d script:

Code: Select all

#!/bin/sh
#
# PROVIDE: transmission-daemon
# REQUIRE: DAEMON
#
# Add the following lines to /etc/rc.conf to run transmission:
#
#transmission_enable="YES"

. /etc/rc.subr

name="transmission"
rcvar=${name}_enable

load_rc_config ${name}

: ${transmission_enable="NO"}
: ${transmission_user="nobody"}
: ${transmission_args=""}

command="/usr/local/bin/transmission-daemon"
command_args=$transmission_args

run_rc_command "$1"

Here is the pertaining part in my rc.conf ;

Code: Select all

# start transmission
transmission_enable="YES"
transmission_user="transmission"
transmission_args="-g /home/transmission/.config/transmission-daemon"

Where is your .config/transmission-daemon/settings.json?

[jch]

Despite and against what has been said in this forum, the dht protocole is not very secured.

If you know of any security flaws in the DHT implementation in Transmission, please file a bug. With the highest possible severity.

--Juliusz

[etlunatic]

As I said, I experienced some security problems when I used rtorrent with DHT enabled.

I am going to build transmission 1.70 on FreeBSD 7.2, I will change however my peer id to that of utorrent, I am going to run it with DHT enabled and I wll post pertaining excerpts of my pflogs and logs logs.

[etlunatic]

UPdate: 1.70 doesn't compile on FreeBSD 7.2. Many errors in dht.c.

[mezz]

It's already committed in SVN to get it builds on FreeBSD. Try 1.71.

Have you ever report to rtorrent author for security?

[etlunatic]

1.71 builds fine on FreeBSD 7.2.

I send a pm to rtorrent/libtorrent developer but I got no response. I don't think it is related to rtorrent.

Last note, my honey pot is up and running in dmz, come on bees (especially RBN bees) show me what you got.