BitTorrent service problems

[athomson]

I have a ReadyNAS NV+ with FW 4.01 release. It has a power on/off schedule to turn it off while I am at work during the week. Each day I come home I can never open the Download Manager and find I may have to stop and start the add-on two or more times. Even when the Download Manager window is open it may lose connection and I find myself going through the above again. I am using FireFox 2.0.0.12, how can I stop this happening and make the add-on behave?

Andy

[chirpa]

Were you running any betas in between the upgrade?

I have a NV+ powering off at night and back on in the morning download torrents and have not seen this issue come up with the download manager.

[athomson]

Yes I was running T68 and a few other betas, do the BT setting conflict with the release 4.01?

Edit: the early beta version (0.7) I think seemed to work fine. The release version (1.0) is causing the above problems.

Andy

[yooden]

I have a similar problem: Last night I used the add-on for the first time, it worked fine then. This morning I rebooted my workstation, but couldn't run the user interface. Brower just loads endlessly, telnet claims to connects and freezes, nmap reports the port as open.

The process seems to be running; netstat says

Code: Select all

tcp        0      0 0.0.0.0:8080            0.0.0.0:*               LISTEN      98         3020       2688/bt


Is there something analogous to

Code: Select all

# /etc/init.d/bt restart

[chirpa]

Is there something analogous to

Code: Select all

start: /usr/share/bittorrent/start_bt.sh
stop: start-stop-daemon -K -n btdog -R5;start-stop-daemon -K -n bt -R5

[yooden]

Chirpa, thanks for the info!

After I downloaded the most important torrents I took the plunge and enabled/disabled BT in Frontview. It came up again, but I lost all partial downloads. If the problem comes up again, I will try Chirpa's restart method.

[athomson]

Thats all well and good but I don't really want to delve into my NV+ with shell access. I just want to know why since the beta 0.6 and 0.7 the BT interface has not worked too well for me and how I make it better? I don't want to stop/start it several times each day and when I lose connection.

Andy

[yooden]

Thats all well and good but I don't really want to delve into my NV+ with shell access. I just want to know why since the beta 0.6 and 0.7 the BT interface has not worked too well for me and how I make it better? I don't want to stop/start it several times each day and when I lose connection.

Calm down, neither do I. Feel lucky that someone with shell access has the same problem, it might actually make diagnosis easier.

[athomson]

OK I'm calm. The BT interface was a good idea while it worked for me I just hope we can find an answer, BTW yooden did you you use any of the 4.01 betas like I did before upgrading to the 4.01 release?

Andy

[yooden]

BTW yooden did you you use any of the 4.01 betas like I did before upgrading to the 4.01 release?

Nope, straight from release to release.

[athomson]

It seems from the BT poll that there are a few people with a power off/on schedule that causes problems with the BT AddOn. So we may see a fix.

Andy

[mzjarvis]

stop: start-stop-daemon -K -n btdog -R5;start-stop-daemon -K -n bt -R5

Is this a stop or a restart ? The ";" in the middle makes ask.

I'd like to set up a cron so that bittorrent starts at 6am and stops at 4pm so that I don't fall fowl of my ISPs peak time bandwidth limits. I can't find any documentation on these bt and btdog commands.

Martin

[chirpa]

stop: start-stop-daemon -K -n btdog -R5;start-stop-daemon -K -n bt -R5

Both stop commands, two processes to stop.

[mzjarvis]

Ok Thanks. Is there a way to just pause the downloads from the command line instead of stopping the processes altogether ?

Martin

[chirpa]

Ok Thanks. Is there a way to just pause the downloads from the command line instead of stopping the processes altogether ?

Looks like most you can do right now is set the download rate to almost nothing.

This stops all my torrent downloads:

Code: Select all

wget -q -T 1 -O /dev/null http://localhost:8080/api/app-settings-set?max_dl_rate="1"

Then to start them again:

Code: Select all

wget -q -T 1 -O /dev/null http://localhost:8080/api/app-settings-set?max_dl_rate="-1"