#3044: Restarting deluged via systemd causes errornous torrents
-----------------------+------------------------------------
Reporter: krichter | Owner:
Type: bug | Status: new
Priority: minor | Milestone: needs verified
Component: Unknown | Version: other (please specify)
Resolution: | Keywords:
-----------------------+------------------------------------
Comment (by krichter):
> Did you see the stop timer on the wiki page:
>
> http://dev.deluge-
torrent.org/wiki/UserGuide/Service/systemd#DelugeDaemondelugedService
I added it now (I always forget that `deluge` doesn't maintain the
`systemd` unit in its package), but that doesn't change the issue.
> Also you have not provided any logs so no idea what is occurring on
stop.
Right, the log reveals
{{{
15:09:54.830 [ERROR ][deluge.core.torrentmanager :1158]
on_alert_fastresume_rejected: manjaro-xfce-17.0.1-stable-i686.iso fast
resume rejected. stat(/var/lib/deluge/complete/manjaro-
xfce-17.0.1-stable-i686.iso): mismatching file timestamp
15:09:58.231 [ERROR ][deluge.core.torrentmanager :1158]
on_alert_fastresume_rejected: manjaro-gnome-17.0.1-stable-i686.iso fast
resume rejected. stat(/var/lib/deluge/complete/manjaro-
gnome-17.0.1-stable-i686.iso): mismatching file timestamp
}}}
which I naively assume is the reason for failure. The file with
mismatching timestamp correspond to the errornous files I see in `deluge-
gtk`. I'm using different ZFS datasets for the incomplete/download and
complete directory (0.6.5.9-5ubuntu4 on Ubuntu 17.04).
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/3044#comment:2>
Deluge <http://deluge-torrent.org/>
Deluge Project
--
You received this message because you are subscribed to the Google Groups
"Deluge Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/deluge-dev.
For more options, visit https://groups.google.com/d/optout.
