Checking resume data

General support for problems installing or using Deluge
Post Reply
steve096
New User
New User
Posts: 9
Joined: Fri Mar 26, 2010 7:16 pm

Checking resume data

Post by steve096 »

I've been using deluge for a few years now and just recently started having problems with this message after migrating my torrent server to a new OS. I recently made the switch from an old version of Ubuntu to Debian (testing) for a few reasons. Anyway, I had been running deluge 1.3.6 on my Ubuntu installation, so I just copied my state folder to use on the Debian installation. After installing 1.3.6 from source, copying over my state folder, changing the save path for all of them (~5000 torrents, took a couple hours), and rechecking them, the program was working beautifully, from seeding to downloading newly added torrents. Until my first reboot.

I had to reboot the computer last night (for unrelated reasons) and after starting deluge back up again and waiting for the program to load up (which takes a while with so many torrents), all except about 500 torrents were showing the status "Checking resume data". I thought this was something new to 1.3.6 because I have never seen this message before, but after some poking around on the internet, I found it wasn't. I tried pausing and resuming one to see if it switched back over to seeding, which it did, so i went through the very slow process of doing this for all of my torrents. I then went to bed and slept it off (it was 4am at that point). Upon checking the program again this morning, I figured my troubles had been over and I would just need to figure out why it did this on a reboot. Everything was seeding just fine. I then tried to add another new torrent, which caused the program to partially lock up (the interface still works, but the current usage numbers froze and the program is no longer down/uploading). The new torrent started with the "Checking resume data" status and no amount of pausing or unpausing it changes it. Adding a new torrent before the reboot worked just fine, it never showed this status.

So I guess I have 2 questions really. Why did the program restart with all but 500 of my torrents showing this status, and why did adding a new torrent after my reboot cause this error to show up on the new torrent and make the program partially freeze?

Thank you!
Post Reply