Can anyone help diagnose my issue.
At some point I have done a migration, everything is working except...
When I reboot my machine (Ubuntu 20.04) Deluged starts and starts trying to DL some old torrents, as if there is some old configuration stored somewhere else.
It errors out most of the torrents but sometimes it downloads those old torrents.
When I stop the deluged service and restart Deluge, Deluged restarts with all of the corrects torrents, everything working perfectly again.
So there is something different between reboot machine and starting automatically and restarting deluged manually.
there is some cached config and something pointing at that config causing this issue.
thanks heaps in advance.
2 different start configs
Re: 2 different start configs
The torrents.state file has the right torrents in it.
is there another "torrents.state" file that could be being accessed at reboot time?
is there another "torrents.state" file that could be being accessed at reboot time?
Re: 2 different start configs
In the state directory, I had 57 torrent files, with a #hash#.torrent as their name, so I deleted 21 that were not in my list of 36 working torrents
i have deleted the torrents.fastresume.bak and the torrents.state.bak
still only 32 torrents start after a reboot, all good torrents but with an entirely different added date.
4 torrents are missing, so i still have to restart deluged.
i have deleted the torrents.fastresume.bak and the torrents.state.bak
still only 32 torrents start after a reboot, all good torrents but with an entirely different added date.
4 torrents are missing, so i still have to restart deluged.
Re: 2 different start configs
Hello QWIKAG,
There is maybe the possibility that deluged doesn't correctly shutdown before rebooting the OS.
Can backup your old configurations files (so the settings and such), while deluged is stopped. Then start deluged again (this way it will create new config files again. And then reboot your system to see how it goes.
There is maybe the possibility that deluged doesn't correctly shutdown before rebooting the OS.
Can backup your old configurations files (so the settings and such), while deluged is stopped. Then start deluged again (this way it will create new config files again. And then reboot your system to see how it goes.
===============================================================
Server: Rock 5B 8 Cores (ARM), 16 GB RAM, 2 TB 970 Evo +
OS: Linux Ubuntu 24.04 LTS
Deluge: v2.1.2
Plugins: Blocklist, LabelPlus, ItConfig, MyScheduler, Stats, Notifications, YaRSS2
Server: Rock 5B 8 Cores (ARM), 16 GB RAM, 2 TB 970 Evo +
OS: Linux Ubuntu 24.04 LTS
Deluge: v2.1.2
Plugins: Blocklist, LabelPlus, ItConfig, MyScheduler, Stats, Notifications, YaRSS2