Lost state, all torrents gone

[schwiftypickle]

Hi,

I just noticed that my deluge has lost its state and is now showing an empty torrent list.

I run the linuxserver.io docker container of deluge on a debian system.

My session.state looks like this:

Code: Select all

d3:dhtd18:aggressive_lookupsi1e15:block_ratelimiti5e13:block_timeouti300e15:enforce_node_idi0e22:extended_routing_tablei1e20:ignore_dark_interneti1e13:item_lifetimei0e13:max_dht_itemsi700e14:max_fail_counti20e9:max_peersi5000e15:max_peers_replyi100e24:max_torrent_search_replyi20e12:max_torrentsi2000e15:privacy_lookupsi0e9:read_onlyi0e20:restrict_routing_ipsi1e19:restrict_search_ipsi1e16:search_branchingi5ee5:feedsle8:settingsd16:active_downloadsi10e12:active_limiti200e12:active_seedsi190e10:alert_maski861e16:alert_queue_sizei10000e17:allowed_enc_leveli2e23:cache_buffer_chunk_sizei1e12:cache_expiryi60e10:cache_sizei512e16:connection_speedi20e17:connections_limiti300e10:enable_dhti0e13:enable_natpmpi0e11:enable_upnpi0e17:listen_interfaces12:0.0.0.0:501119:max_retry_port_bindi2e16:peer_fingerprint8:-DE13F0-8:peer_tosi256e10:prefer_rc4i1e10:proxy_porti8080e15:seed_time_limiti19200e17:share_ratio_limiti500e10:user_agent13:Deluge 1.3.15ee

Is there any way to recover my session?

[Cas]

The session.state file has nothing to do with torrents, it's just config. It's a long shot but check the state folder in your config for .bak backup files of torrents.state and torrents.fastresume however they might have already been overwritten

[schwiftypickle]

The torrents.state.bak file has the same content as the torrents.state file which is this:

Code: Select all

(ideluge.core.torrentmanager
TorrentManagerState
p1
(dp2
S'torrents'
p3
(lp4
sb.

torrents.fastresume and torrents.fastresume.bak also are identical.

So no chance of recovering, I guess?

[Cas]

Without any personal backups, I'm afraid not, the original torrent files that were loaded should be in the state folder but obviously without any renaming details.

If it's any consolation, I have been working on preventing this in development code.

[schwiftypickle]

Thanks for the ongoing work on deluge

[slvrdragn]

I came across this issue recently with dev 189 or possibly just after. I have a script that reloads the active torrents but it would sure be nice to be able to figure out why this is occuring, the logs aren't giving me any clues. I'm running dev200 now, see what happens.

[Alexey104]

I've been suffering from this issue since I started using Deluge in 2010, and it's still happening in 2020 with 2.0.4.dev38. I run a backup script at the background, but this problem is really annoying.

[ihateregistering]

Hey, just FYI, I enabled your plugin, changed the path, and it crashed deluge. Then when the server restarted, my whole list of torrents was gone. I had no clue this type of crap has been a thing with deluge since it was a baby, as per /viewtopic.php?t=26775&start=110 - so ... yeah. Good job I guess? Maybe one smart thing you could have done is check that the .bak file you're overwriting on startup is not BIGGER than the one you're about to write? But no... why be smart about it? Just wipe people's lists! It's all good. :facepalm:

[mhertz]

Patches accepted smartaa**...