I'm running the latest Transmission on my Mac and suddenly it gives a strange problem. I restarted Transmission after I transfered some files from my hard drive to my external drive (no files which had anything to do with my torrent downloads). The application starts and no connections are made. Based on my traffic monitor, it connects to the trackers from the torrent. But after that, no connections to peers at all and everything remains 9. When I looked at the log, it states:
2011-07-03 01:46:12 +0200 net.c:365 [Fout] Transmission: Couldn't bind port 49258 on 0.0.0.0: Address already in use (Is another copy of Transmission already running?)
2011-07-03 01:46:12 +0200 net.c:365 [Fout] Transmission: Couldn't bind port 49258 on ::: Address already in use (Is another copy of Transmission already running?)
2011-07-03 01:46:12 +0200 tr-udp.c:256 [Fout] UDP: Couldn't bind IPv4 socket
I checked the activity and only 1 Transmission is running, no other (included) processes. What's going wrong?
That doesn't help. The problem is caused when the app needs to be force closed, because the app is not responding for whatever reason. If you start the app after the force close, it will give this message in the log. I really think it's a bug in 2.32. I never had this problem after a force close before. When I reboot my Mac, it solves the issue.
Waiting for a bit works, thanks. But I hope this could be solved someway. IT makes the experience more seamless and rock solid, if the app works after such a force close.