Note that there are some explanatory texts on larger screens.

plurals
  1. POProblems using BitTornado for file distribution
    primarykey
    data
    text
    <p>I'm experimenting with BitTornado-0.3.17 to distribute a file to several machines (*nix). I ran into couple of problems while doing so. Here is what I have done so far.</p> <ol> <li>Download BitTornado-0.3.17.tar.gz from <a href="http://download2.bittornado.com/download/BitTornado-0.3.17.tar.gz" rel="nofollow">http://download2.bittornado.com/download/BitTornado-0.3.17.tar.gz</a> and untar it.</li> <li>Created a torrent file and started tracker following instructions in the README file.</li> <li>Started a seeder </li> </ol> <blockquote> <pre><code>./btdownloadheadless.py ../BitTornado-0.3.17.tar.gz.torrent --saveas ../BitTornado-0.3.17.tar.gz </code></pre> <blockquote> <pre><code>saving: BitTornado-0.3.17.tar.gz (0.2 MB) percent done: 0.0 time left: Download Succeeded! download to: /home/srikanth/BitTornado-0.3.17.tar.gz download rate: upload rate: 0.0 kB/s share rating: 0.000 (0.0 MB up / 0.0 MB down) seed status: 0 seen recently, plus 0.000 distributed copies peer status: 0 seen now, 0.0% done at 0.0 kB/s </code></pre> </blockquote> </blockquote> <ol> <li><p>Now we have a seeder. I start a peer on another machine to download BitTornado-0.3.17.tar.gz.</p> <p>./btdownloadheadless.py BitTornado-0.3.17.tar.gz.torrent</p></li> </ol> <p>At this point I do not observer my peer to download data from seeder. However if I kill my seeder and start again, the peer immediately downloads from the seeder. Why is it happening this way? The first time seeder reports tracker, tracker should be aware of the seeder and share that information to newly joined peer. Its happening only when I start seeder after peer joins the network. </p> <p>Has anyone used BitTornado to distribute files programmatically (not using GUI tools at all.) ?</p> <p>Thanks :-)</p> <p><strong>EDIT:</strong> Here is what happened a few days later. I dig into tracker logs and figure that seeder is binding itself onto a private ip address interface and reporting it. It is causing other clients to not reach seeder. hence no download. So I passed --ip options to it, which made it to report the tracker the machine's public ip address to which it bound. Even then for some reason i couldn't get client to download from seeder. However I got it working by starting client first and seeder last. This worked for me consistently. I can't think of any reason why it shouldn't work the other way. So, I'm starting clients first and then starting seeder.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload