ruTorrent 5.3.10 with rtorrent 0.16.18 - Moving a Completed Download

[Gosokan]

Newly added torrent or magnet files using ruTorrent 5.3.10 with rtorrent 0.16.18 do not start imediatelly. The added torrent is in a stopped state. The same applies when I added torrent and specify new label or select an existing label. Where the torrent should be moved to the /mnt/sdb/rtorrent/completed/<label-name> directory, once the download process is complete.

The rtorrent terminal interface (cli) will display the following message:

Download event action failed: Command "execute2" does not exist.

rtorrent.rc configuration:

method.insert = d.get_finished_dir, simple, "cat=/mnt/sdb/rtorrent/completed/,$d.custom1="
method.insert = d.get_data_full_path, simple, "branch=((d.is_multi_file)),((cat,(d.directory))),((cat,(d.directory),/,(d.name)))"
method.insert = d.move_to_complete, simple, "d.directory.set=$argument.1=; execute=mkdir,-p,$argument.1=; execute=mv,-u,$argument.0=,$argument.1=; d.save_full_session="
method.set_key = event.download.finished,move_complete,"d.move_to_complete=$d.get_data_full_path=,$d.get_finished_dir="

When I manually press the start button, the download process will begin. However, after it was finished, he rtorrent terminal interface (cli) will display the following message:

Event 'event.download.finished' failed: Command "d.custom1=" does not exist

So, torrents that have finished downloading will remain in the /mnt/sdb/rtorrent/downloading directory. How can this problem be resolved?

[xirvik]

Easiest thing to try first, in this order:

1. In ruTorrent, do a hard refresh of the page (Ctrl-Shift-R, or Cmd-Shift-R on a Mac). Then add a test torrent and see whether the execute2 message still appears.
2. If it does, restart rtorrent and then hard-refresh ruTorrent again. That's usually enough to make ruTorrent re-read the version and switch to the modern command names.

If it's still happening after that, could you open Help → About in ruTorrent and tell us which rtorrent and libtorrent versions it lists? If that shows anything other than 0.16.18, it confirms the cached-version theory and the fix is straightforward from there.

[Gosokan]

Okay, the issue is resolved now. Moving completed torrent function is working as expected. Here is what I did:

1. restarted php-fpm
2. restarted nginx
3. cleared the browser cache

I'm not sure which of the three was the most effective. But previously, cleared the browser cache or simply using a new browser profile hadn't worked, even though the rtorrent version and library version displayed in ruTorrent were correct.