#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 krzaku):
Same issue, same log line:
{{{
[ERROR ] 02:00:53 torrentmanager:1147 on_alert_fastresume_rejected:
Star.Trek.The.Next.Generation.S01-07.COMPLETE.1080p.BluRay.x264-MULTiGRP
fast resume rejected: mismatching file timestamp
}}}
This only happens for torrents that aren't fully downloaded yet. I'd
provide a log but it contains a lot of private data that I wouldn't want
posted online.
I noticed that when the error occurs, in logs there is no information
about specific torrents saving resume data:
{{{
[DEBUG ] 11:10:43 torrentmanager:1117 on_alert_save_resume_data
[DEBUG ] 11:10:43 torrentmanager:769 Opening torrents fastresume file
for load.
[INFO ] 11:10:43 torrentmanager:780 Successfully loaded fastresume
file: /config/state/torrents.fastresume
[DEBUG ] 11:10:43 torrentmanager:821 Creating backup of fastresume at:
/config/state/torrents.fastresume.bak
[INFO ] 11:10:43 torrentmanager:826 Saving the fastresume at:
/config/state/torrents.fastresume
[DEBUG ] 11:10:43 alertmanager:124 portmap_log_alert: NAT-PMP: ==> port
map [ mapping: 2 action: add proto: udp local: 58946 external: 58946 ttl:
3600 ]
[DEBUG ] 11:10:44 alertmanager:124 portmap_log_alert: UPnP: broadcasting
search for rootdevice
[DEBUG ] 11:10:44 alertmanager:124 portmap_log_alert: UPnP: HTTP method
m-search from 192.168.1.10:52336
[DEBUG ] 11:10:44 alertmanager:124 portmap_log_alert: UPnP: HTTP method
m-search from 192.168.1.10:1900
[DEBUG ] 11:10:44 alertmanager:124 portmap_log_alert: UPnP: HTTP method
m-search from 192.168.1.10:1900
[INFO ] 11:10:45 daemon:196 Waiting for components to shutdown..
[DEBUG ] 11:10:45 core:163 Core stopping...
[DEBUG ] 11:10:45 torrentmanager:732 Creating backup of state at:
/config/state/torrents.state.bak
[INFO ] 11:10:45 torrentmanager:737 Saving the state at:
/config/state/torrents.state
}}}
Notice how after on_alert_save_resume_data there are no torrents, while I
usually have a line like that for every running torrent:
{{{
[DEBUG ] 11:04:35 alertmanager:124 save_resume_data_alert: nnn resume
data generated
[DEBUG ] 11:04:35 torrentmanager:1117 on_alert_save_resume_data
}}}
--
Ticket URL: <http://dev.deluge-torrent.org/ticket/3044#comment:5>
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.
