![]() ![]() IE: I have set the log level to "Debug", here's what I get: can you post the first entries of the transmission logs upon startup? I perfectly understand your problem: even my Transmission sometime connects to http tracker with no problem but fails on udp. ![]() maybe a crashed instance of Transmission?Ĭ) I will try restarting the mac and see if it only happen with port 6998 or maybe with the port opened by transmission the first time it is launched. This may mean that in some way the 6998 port is still "bind for UDP" by some process. ![]() Premises: transmission open, with one port selected (ie 30000) and recognized as Open, one torrent running and announces working properly.ġ) in preferences change the port into one perviously used by transmission, in my case 6998.ģ) reopen transmission: the "Couldn't bind IPv4 socket" appears, no tracker activity:(ĥ) close and reopen transmission: everything works OKĪ) when transmission is in the "stuck tracker" mode and I change the port the tracker announces still fails: I have to restart it in order to make it "see" the new port settingī) the problem seems to affect only one port 6998, which is the one I usually use for transmission and is the one I forwarded on my router following the steps above with initial port 7000 and next port 8000 results in everything OK. In addition I managed to further simplify the procedure to reproduce the situation. I don't think about something related to ISP: following steps above, one time announces work, the next they don't. No other firewalls the situation is the same with or without Lion builtin firewall. Okay, so you don't use PG2, L'il Snitch, Norton Firewall, or the like? I wonder about your ISP? Lion firewall with the default settings and Transmission is already allowed to transmit. I hope someone can understand the reason of this odd behaviour. I imagine that the plist file would be useful to further debug the problem.ĮDIT: new plist file, the old one was the wrong one Of course this is only a workaround, by deleting the preference file I loose all the preferences as well as filters and so on. If I close transmission and delete preferences files then all the download start promptly and the trackers respond as usual. I managed to solve the problem by periodically remove the file. 16:40:59 +0000 tr-udp.c:260 UDP: Couldn't bind IPv4 socketĪll the other messages are just the retry in connecting to the trackers. The only meaningful error I get in the log is this: I get: Connection failed for all 3 trackers. Sometimes when I add some new torrent to download, transmission seems not to be able to start them becouse it gets tracker errors.įor example, using a torrent of a popular tv shows that uses: I have a recurring problem with transmission. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |