Search results

Thanks Wonslung I have 7 downloading from 3 different trackers and i have a screen shot of them during download and ill take another shot in a few hours and see if it gives any hints to my problems. Ill post my rtorrent.rc file then aswell.

Thank you Wonslung and Novik65 I know the basics of how trackers and swarms work and ive used Flux for a while so i have a good idea of what to expect but i prefer Rutorrent. I'm new to rtorrent and rutorrent but i wont give up so thanks for all the help so far @ Stubs - Thanks for the...

Quote If it's not seeding back there are 3 possible reasons. 1) Sounds right 2) It happens on all trackers and ive tried a few so i ruled that out 3) Shouldnt be any but ill check Quote You are probably in the state the call "unconnectable" I thought that but i tested on a private tracker...

After many more hours searching ive found someone with the exact same error as me in a support ticket at libtorrent http://libtorrent.rakshasa.no/ticket/2170 To save anyone clicking and reading it says this : Quote hope rakshasa would add in the next realeases the option to scrape a tracker...

@ Novik65 - If the port was closed wouldnt it stay closed ? The downloads work fine during download showing the swarm and tracker info but once completed they stop connecting and show 0 seeds 0 peers and no tracker announce or status listed. @ Wonslung - The show peers like WTorrent plugin has...

I dont have it installed but i can if you think itll help ?

Changing max open files to 128 has fixed the second problem Thanks But the 1st problem still exists , I cant see the swarms even though they are healthy and the tracker announce(s) and status still show blank info Any help would be great because im lost and its all i need to finish the...

Cheers Wonslung I'll edit the max open files to 128 When you say my shit may be setup wrong could i have a clue ? They work fine when downloading but after they finish and show as completed they just ignore the swarm and sit there doing nothing, Thinking it could be the swarm i tried the...

sorry, i was sleeping yesterday

Hello I did search and read every post here but im stuck at fixing 1 or 2 small issues i have and would love to get them fixed. My setup is a VPS server running on debian - RuTorrent is version 3.1 - Rtorrent is version 0.8.6 - Libtorrent-0.12.6 My first problem is the swarms dont seem to...

I think it's more a php issue. Wich version of php are you using? (type php --version in console)

A long shot but possible is , the path you have specified for autostarting using the RSS manager, is it the same as any watch paths you have in your rtorrent.rc file for rtorrent, IF you have any?

In Firefox, make sure you check View > Page Style > Basic Page Style. Make sure it's not set to "No Style" or you may end up with a page looking like what you posted.

isit possible you have javascript disabled in the other browsers?

I'm using this Chef cookbook to set up my Ubuntu 10.04 box, works flawlessly: http://github.com/gerhard/rtorrent-cookbook I don't have time to do a write-up now, but I'll follow up on this. If you want to find out more about automating server setups with Chef, this is a good place to start...

A search could probably help you. Try restarting your web server. Try using the latest version of PHP.

I was looking at doing the script way and that's how I had it setup for Rutorrent 2.8 and Rtorrent 0.8.4 Ubuntu 9.04 I'll take a look at your script and get back to you... Thanks for the help.

For some reason Cron doesn't start rtorrent with boot. Anyone know why? From Crontab: @reboot /usr/bin/screen -dm rtorrent -n -o import=/home/lotus22/.rtorrent.rc I can run that on a terminal screen and it runs fine. I don't know why it's not working with boot.

i'm not familar with your nas but if you could install a more user freiendly brand of linux on it you shoud have no problems. go with ubuntu, debian or arch.

Quote I've never had access to a gbit line but there are a few things that you may take into consideration. 1 - Not many people have a line as fast as you. You need many peers to max out a line like yours 2 - Routing may not be very good to all peers 3 - Your disk configuration may not be able...