changed id in transmission-remote after restart of daemon

[deadeyes]

Hi all,

I am sometimes experiencing the following issue:

I am writing a webapp which is using rpc calls to communicate with transmission-daemon.
I use transmission-remote to test/check things.

I noticed that when I did a listing and retrieved the correct id, and then tried to start the torrent it returned "success".
HOwever when I listed the torrents again the targeted torrent was still "stopped".
Trying to stop and start this torrent again had no effect.

When I restarted transmission-daemon, all IDs seem to be different but the start/stop seemed to work again.

Someone else is also experiencing this issue? What could be the cause?
It seems that the data returned from the call was not up to date. However I need the correct ID to start a torrent (maybe using the hashString would be more appropriate as this is always unique but this is not possible).

[rb07]

The torrent's "ID"s change every time you start/restart the daemon, that's well known and there is nothing to make those IDs fixed.

Yes, the remote applications become confused if you restart the daemon, the Web client at least shows first that the connection failed, then all bogus information (just as you describe, the IDs are used to index the torrents but when they change...) The Qt application used to do the same, but with the last version it recovers... of course I haven't tested this extensively, my comments are from just a few observations.

[deadeyes]

I can live with the IDs being changed by a restart of the transmission-daemon binary.
Each time my webapp does request all the info so that is no problem.

THe only strange thing is that I sometimes cannot start a torrent were I am clearly using the correct command line and ID. It seems like the ID is not responding anymore
I think this happens when I delete some torrents.

At that moment the only fix was restarting the daemon.

[rb07]

The only strange thing is that I sometimes cannot start a torrent were I am clearly using the correct command line and ID. It seems like the ID is not responding anymore. I think this happens when I delete some torrents.

I've never seen that, perhaps you should open a bug report with all the details (for both local and remote: versions used, operating system) and some test case (i.e. running transmission-remote show the torrent is stopped, try to start it, show the exit code at this point to make sure transmission-remote did not, silently, report an error, then show that its still stopped).