A seeding client refuses to seed

Looks like I’ve hit a new issue. The seeding client refuses to seed one of the auto generated torrents. There’s no errors generating it nor adding it, and the tracker works fine. The peer connects to the seed, but the seed closes the connection immediately (tested both in a monotorrent client and uTorrent 2.2.1, in monotorrent the seed gets removed from the peers list immediately after it’s added while uTorrent periodically tries to connect but the seed closes the connection immediately).

The torrent contains a very large amount of small files, it’s 163KB with only V1 hashes. I’m guessing it’s something about that. Other torrents generated in the same way seed fine. There’s nothing in the log outside of this:

Client log:

[18:56:37] INFO: ConnectionManager:ipv4://xx.xx.xxx.xxx:15847/: Connection opened
[18:56:37] INFO: ConnectionManager:ipv4://xx.xx.xxx.xxx:15847/: [outgoing] Sending handshake message with peer id '-MO3000-374654087375'

Server log:

INFO: ListenManager:ipv4://yyy.yyy.yy.yyy:51952/: ConnectionReceived

Packet dump: stuck.zip

[ManlyMarco]

It looks like no exceptions are thrown when this happens.

It seems that after restarting the server side app, the seed always works fine, but it stops working after either restarting the client and starting the download over a few times, or after letting the seed idle for a while, not sure which one. It could also just be luck, but once it stops working it stops working for good, maybe it’s something related to open connections?

If you have any test builds I could try to find the issue, let me know.

Edit: This issue is constrained to a particular torrent - with multiple torrents being seeded if I manage to get the bug to happen it only happens for a single torrent (unless I manage to trigger it again with another torrent). When the bug is active, it looks like no one can download the bugged torrent from the seed, even if it’s their first time connecting (they can download other non-bugged torrents just fine).

Edit2: Could this be related to the max open file limit? I just noticed I had it set to 200 while the torrents easily surpassed that. I’ll try bumping the value up and see what happens. When testing I was using only one client, downloading one torrent (but I had all torrents added to the client and started to seed them, so the seed shouldn’t be affected by that).

[ManlyMarco]

Everything works fine in my app now on the latest master builds, so I’ll close this issue.

@rjclarkewp007 If it never connects then maybe ports it tries to use are closed on both sides. If you still have this issue I think you should open a new issue since this one got a bit off topic.