Transmission 0.8x

[fatsu]

I upgraded to Transmission 0.8x last week (from 0.7x). Since then there seems to be a problem:




Sep 16 22:05:09 transmissiond[10132]: Transmission daemon 0.82 (r) started - http://transmission.m0k.org/
Sep 16 22:05:09 transmission_watchdog: Transmission daemon restarted!
Sep 16 22:05:10 transmissiond[10132]: Starting torrent /opt/torrents/work/XYZ/XYZ.torrent
Sep 16 23:05:32 transmission_watchdog: Moving files to: /opt/torrents/target/XYZ
Sep 16 23:35:02 transmissiond[10132]: /opt/torrents/work/XYZ/.status - No such file or directory
Sep 17 00:05:02 transmissiond[10132]: /opt/torrents/work/XYZ/.status - No such file or directory
Sep 17 00:35:02 transmissiond[10132]: /opt/torrents/work/XYZ/.status - No such file or directory
Sep 17 01:05:02 transmissiond[10132]: /opt/torrents/work/XYZ/.status - No such file or directory
Sep 17 01:35:02 transmissiond[10132]: /opt/torrents/work/XYZ/.status - No such file or directory
Sep 17 02:05:02 transmissiond[10132]: /opt/torrents/work/XYZ/.status - No such file or directory
Sep 17 02:35:03 transmissiond[10132]: /opt/torrents/work/XYZ/.status - No such file or directory
Sep 17 03:05:02 transmissiond[10132]: /opt/torrents/work/XYZ/.status - No such file or directory
Sep 17 03:35:02 transmissiond[10132]: /opt/torrents/work/XYZ/.status - No such file or directory
Sep 17 04:05:02 transmissiond[10132]: /opt/torrents/work/XYZ/.status - No such file or directory
Sep 17 04:35:02 transmissiond[10132]: /opt/torrents/work/XYZ/.status - No such file or directory
Sep 17 05:05:02 transmissiond[10132]: /opt/torrents/work/XYZ/.status - No such file or directory
Sep 17 05:35:02 transmissiond[10132]: /opt/torrents/work/XYZ/.status - No such file or directory
Sep 17 06:05:02 transmissiond[10132]: /opt/torrents/work/XYZ/.status - No such file or directory
Sep 17 06:17:24 transmissiond[10132]: Stopping torrent /opt/torrents/work/XYZ/XYZ.torrent
Sep 17 06:17:24 transmissiond[10132]: All torrents stopped
Sep 17 06:35:02 transmission_watchdog: Torrents paused


everything goes well until the move (work to target)...
In my case, transmission kept on sending data from 23:05 until 6:35 even though the download was complete, and the auto_seed flag was set to false.

anyone has had similar experiences or even better: has a solution?

[oleo]

Unusual situation where damon was started, watchdog moved files from work and daemon did not get the signal I suggest that you turn on autoseeding.

[fatsu]

Hi Oleo,
thank you for replying so quickly.

I don't see what enabling auto-seeding will change to the problem. Also, that is not what I want to achieve.

I guess i'm alone with this problem? I'll try to do some debugging later this week.

[fatsu]

This behaviour has nothing to do with the new version. I only noticed it now because of circumstances (no downloads in progress when upgrading, and nothing much to download anyway).

here it goes:
The "XYZ.torrent" in the log-extract above is ofcourse not the real name of the torrent. The real name includes a lot of dots (.) and square brackets([])...

The (inverted) grep in transmission_watchdog on line 218 (r6363) treats the torrent name as a regexp instead of a fixed string, preventing the finished torrent (with square brackets in its name) from being removed from the active-torrents file.

The fix for this problem should be a simple as adding the "-F" option to that grep.

[oleo]

Changeset #6866 (http://trac.nslu2-linux.org/optware/changeset/6877) includes this fix.
Thanks.