Experiment: uninstall deluge on the host OS. reinstall deluge. deluge on host OS is aware of seeder running on VM and yet it doesn't connect. rebbot deluge. connection now works.
Conclusion: eventually it works, but the behavior is erratic and there is no feedback as to why it is like that. As far as I can see it is related to how it attempts to connect and the reboot probably made it reattempt the connection. Unofrtunalet there doesn't seem to be a way to force it to do that. On Thursday, June 12, 2014 4:01:13 PM UTC+1, Dan Cristian Octavian wrote: > > I am working on a fairly complex project which involves tampering with the > BitTorrent connection between 2 deluge clients. I wrote and RPC api for > deluge in the programming language of my project and a REncode > implementation, already investing quite a lot of effort in making it work > with deluge. > > However, when I'm just using basic deluge functionality (no tampering, no > fancy stuff) from the Deluge GUI on Ubuntu12.04, it has a very erratic > behaviour. sometimes it works and sometimes it refuses to do anything when > entasked to download a torrent (sometimes it hangs for minutes even though > the GUI says there are thousands of peers available - doesn't connect to > any of them displaying the stats: "seeds: 0 (4567) and peers: 0(678)" ). > > By running deluge on verbose mode it offers absolutely 0 information about > what connections its attempting. I'm guessing this is because it's all in > the libtorrent layer. > > The issue is that I am relying on deluge for my project to work and it's > behaving extremely erratically. > > === MY USE CASE === > For example I am running 2 deluge clients: 1 on a host OS and the other > on a guest OS inside of virtualbox, both running 12.04 ubuntu. the one > inside Virtual box seems to be quite responsive to "add peer" commands and > starting the download of a new torrent. The other one running on the guest > OS sometimes never starts a download of a file, no matter how many "add > peer" instructions i am issuing. > Ideally, the 2 deluge clients enter the same swarm to download the file. > It usually works when the seeder is on the host OS and the peer is on the > VM, but it never works when the seeder is on the host OS and the peer is on > the VM. There is no port overlap or anything. > > Also, whenever I am testing whether the active incoming port of the host > OS deluge client is working, it shows a red icon with an exclamation mark. > Once again, this gives me absolutely 0 information about what is happening > (even with a verbose flag, nothing is logged). Even though it shows this > red icon, the VM client seems to be connecting on that port just fine, most > of the times. > > TL;DR > i need good control over the Deluge through the RPC api, but even when > using the GUI basic functionality such as peer connections fails > erratically when 0 indications of why it is the case > > > What can I do about this? Did I mess up settings/configurations? could it > be an issue with my network connection? Is it the kind of behavior you > would expect from deluge? > > Many thanks! > -- You received this message because you are subscribed to the Google Groups "Deluge Dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/deluge-dev. For more options, visit https://groups.google.com/d/optout.
