transmission-deamon does not respond on commands

[Xake]

With version 2.22 for me even with smaller torrents on a system with currently nearly no other load, even a 6GB torrent gives the respons shown below. I had this problem with earlier version, but mostly only when >10GB torrents finished and was moved from my "incomplete" folder residing on a raid0 to my "completed" folder residing on a raid5, cannot remember having it for moving a torrent on the same volume.

$ transmission-remote -l <works fine, and shows status of an currently very un-busy transmission> $ transmission-remote -t 27 --move /srv/<bla> [17:41:23.148] transmission-remote: (​http://localhost:9091/transmission/rpc/) Timeout was reached

The problem here seems to be that transmission-daemon does not tell transmission-remote that it recieved the command, because it has to much IO blocking it. So with other words, I have no way of knowing if the command was recieved and -daemon has a hard time crunching the IO, or if there was something other happening blocking my command (like that raid0->raid5 move described above).

I suggest that transmission-daemon takes care at least to see that tm-remote got an a respons before crunching away.

The ultimate fix would probably be to have transmission-daemon doing some basic checks (enough space? write permissions? it currently does not seem to make any of those), then respond "success/failure", then start to move for real if possible.

[jordan]

The problem here seems to be that transmission-daemon does not tell transmission-remote that it recieved the command, because it has to much IO blocking it.

This issue will be solved by #1753. Closing this ticket as a duplicate.