After a restart of deluged (v1.06) all torrent reset

[yogib3ar]

After a restart of deluged, al the current downloads, some of them almost finished reset at 0, resulting in downloading the complete torrent again (with a lot of time wasted of course)

I'm using ubuntu for about two weeks now, all is working nicely, Deluge also, but this little thing bugs me.
(because testing ubuntu with other programs sometimes result in a reboot mostly because of my ignorance )

On windows I use utorrent which just resumes a torrent where it previously stopped.

Am I doing something wrong or is it impossible to realize this?

I'm realy pleased how Deluge works, but it's a big minus for me if the torrents restart everytime i reboot ubuntu.

By the way the download rate on utorrent is a lot better, like previous posters allready stated, downing the same torerents on my other machine (windows) using utorrent, creates downloads probably 10 times higher.
Is there a way to resolve this, or has Deluge just progress to a better state?
I've tested with wine and utorrent on the same ubuntu PC and downloading at the same time, deluge gives me a download speed of 13kB/s but wine with utorrent doing 190kB/s. Now thats a big difference!

Hoping for at least a solution for the download reset problem, what am i doing wrong?

The Bear

[barjac]

I don't know about 1.06 - was not aware it existed but I just upgraded to 1.05 and have just the same problem - all torrents show 0% after a re-boot when in fact they were all seeding. It is possible to sometimes force a re-check, but this is very hit and miss - I am going to go back to 1.04. Shame, I was beginning to like Deluge, it was rock solid but now it seems to be getting a bit buggy.

Mandriva Linux 2009.0 (2.6.27.5-desktop-2mnb)

[yogib3ar]

I don't know about 1.06 - was not aware it existed but I just upgraded to 1.05 and have just the same problem - all torrents show 0% after a re-boot when in fact they were all seeding. It is possible to sometimes force a re-check, but this is very hit and miss - I am going to go back to 1.04. Shame, I was beginning to like Deluge, it was rock solid but now it seems to be getting a bit buggy.

Mandriva Linux 2009.0 (2.6.27.5-desktop-2mnb)

Meaning 1.04 does not have this problem? (only tested 1.06 , it's the latest one, so brandnew!) if it doesn't let me know, Then I will downgrade to 1.04 too..., thanks..

[barjac]

"Meaning 1.04 does not have this problem? (only tested 1.06 , it's the latest one, so brandnew!) if it doesn't let me know, Then I will downgrade to 1.04 too..., thanks.."

OK not sure yet.
I have gone back to 1.0 as it was available as rpm in repo.
If Deluge is stopped by using right click QUIT from the tray before shutting down then it comes back with all seeds seeding on re-boot and starting the program. However if Deluge is running in the background and a system re-start is done then it comes back with all torrents "checking 0%" most of which then begin to download again from 0%. Right click "Force re-check " then does a full re-check and starts seeding again.
I will un-install 1.0 and re-build 1.4 from source to see if I get the same behaviour. I rarely shut down this machine so it's not normally a problem, maybe as a result of a lot of recent re-boots (long story!) this has shown up.
Will let you know.
EDIT OK So I removed 1.0.0 and made a fresh build of 1.0.4. On first run it picked up everything and started seeding. I then QUIT it and re-started. Same - no problem. I then re-started the machine with it running and on re-boot and starting Deluge all torrents were shown as checking 0.00%. Two (out of 21) re-checked fine and started seeding, but after five minutes now the rest are not doing anything. Right-click on a torrent and "Force recheck" does nothing. I quit Deluge and started it in a terminal. This time the two that were seeding were still there but two of the others that had been doing nothing started to download from scratch. (I have a limit of two concurrent downloads set) Right click "force recheck" causes these to check 100% and start to seed and immediately another two start to download and have to be manually forced to re-check until eventually all are back seeding. Mad !
The terminal output is interesting - it throws up lots of these:-

Code: Select all

[DEBUG   ] 13:27:54 signals:102 torrent_paused signal received..
[DEBUG   ] 13:27:54 torrentview:392 marking 89ad876756686811d381e173dc35ae58cfe8fbdc dirty
[DEBUG   ] 13:27:54 signals:102 torrent_paused signal received..
[DEBUG   ] 13:27:54 torrentview:392 marking e363da652e27cf31e6d64d1c1a458a7b8221bf3a dirty

So in a nutshell it is not just 1.0.6 - it looks like a bug in all versions under Linux.
The solution is to QUIT the program BEFORE closing down until it gets sorted properly.
I too always used uTorrent under WinXP and it works well under Linux with Wine, however I could never get port forwarding to work properly with it. Azureus/Vuse also works well but has some issues with KDE4 so I ended up here and other than this irritation and it's inability to seed re-named torrents it works pretty well.
Cheers, Barry

[yogib3ar]

OK not sure yet.
I have gone back to 1.0 as it was available as rpm in repo.
If Deluge is stopped by using right click QUIT from the tray before shutting down then it comes back with all seeds seeding on re-boot and starting the program. However if Deluge is running in the background and a system re-start is done then it comes back with all torrents "checking 0%" most of which then begin to download again from 0%. Right click "Force re-check " then does a full re-check and starts seeding again.
I will un-install 1.0 and re-build 1.4 from source to see if I get the same behaviour. I rarely shut down this machine so it's not normally a problem, maybe as a result of a lot of recent re-boots (long story!) this has shown up.
Will let you know.
EDIT OK So I removed 1.0.0 and made a fresh build of 1.0.4. On first run it picked up everything and started seeding. I then QUIT it and re-started. Same - no problem. I then re-started the machine with it running and on re-boot and starting Deluge all torrents were shown as checking 0.00%. Two (out of 21) re-checked fine and started seeding, but after five minutes now the rest are not doing anything. Right-click on a torrent and "Force recheck" does nothing. I quit Deluge and started it in a terminal. This time the two that were seeding were still there but two of the others that had been doing nothing started to download from scratch. (I have a limit of two concurrent downloads set) Right click "force recheck" causes these to check 100% and start to seed and immediately another two start to download and have to be manually forced to re-check until eventually all are back seeding. Mad !
The terminal output is interesting - it throws up lots of these:-

Code: Select all

[DEBUG   ] 13:27:54 signals:102 torrent_paused signal received..
[DEBUG   ] 13:27:54 torrentview:392 marking 89ad876756686811d381e173dc35ae58cfe8fbdc dirty
[DEBUG   ] 13:27:54 signals:102 torrent_paused signal received..
[DEBUG   ] 13:27:54 torrentview:392 marking e363da652e27cf31e6d64d1c1a458a7b8221bf3a dirty

So in a nutshell it is not just 1.0.6 - it looks like a bug in all versions under Linux.
The solution is to QUIT the program BEFORE closing down until it gets sorted properly.
I too always used uTorrent under WinXP and it works well under Linux with Wine, however I could never get port forwarding to work properly with it. Azureus/Vuse also works well but has some issues with KDE4 so I ended up here and other than this irritation and it's inability to seed re-named torrents it works pretty well.
Cheers, Barry

Well Barry it's a bummer, to quit Deluge is not quite that simple, i'm using a daemon, so it's not a click of a button, the seeding problem is the same on this side.
I also had problems with the download speed, but I found the problem, the incoming connections port was closed in my router. after changing the ports (which can be set in the web gui version at ports, setting them both (from and to) to the same port number and adjusting my router to this port, the incoming connections work and 'hey presto' there's the speed again, just like Utorrent.)
Perhaps this will help you with utorrent aswell because the same incoming port problem was true for me with utorrent under wine.
At the properties/connections of utorrent you will notice a port used for incoming connection, you change this to your liking as long you're going to enter this port in your firewall and router also.
Magically your incoming connections should work too, just like mine.

Take care and thanks for your testing, i'm staying with Deluge because i don't like to use wine, all those resouces gone and also bacause I'm trying to leave MS behind, moving to wine is not a choice I want to make.

Cheers to U 2, The Bear

[barjac]

I'm trying to leave MS behind, moving to wine is not a choice I want to make.

Yes that's my objective and it's working! Just a few applications that I can't replace yet but the list is shrinking.
You may want to look at the end of this thread :-
http://forum.deluge-torrent.org/viewtop ... =7&t=12805

Looks like a job for a shutdown script. Something that you can run from a desktop launcher that will stop the Deluge daemon and then call a shutdown.
I had to do a similar thing on startup with uTorrent. I had all the data files on an external drive which was sometimes disconnected. If I started uTorrent with the drive disconnected it messed up the torrent states, so I made a launch icon that called a script that would only launch uTorrent IF the drive was visible on the system. (it just looked for a file in the root).

Magically your incoming connections should work too, just like mine.

No, mine never did and all the port forwarding was set up correctly - another problem was the network traffic light was out of sync with the tooltip - quite often it was red yet the tooltip would display network OK - I did report that bug.
OK must go - have fun - I'm waiting for 1,1 when hopefully it will be possible to seed torrent files under different names.

[Die$el]

Deluge 1.1.3 (Ubuntu 8.10)
the same bug
after each restart of deluge with the service, he checks two torrents and stops, if you do it a few times, you can run all, two, then two more, and so on.
but after reboot, they all lose again.
sorry for my English. I use google translator.

[daniel3ub]

Same here, usingo 1.1.0-1 on Ubuntu 8.10.

I don't know how to compile programs or install from the source, so I use the version obtained from the repos.

[barjac]

Interesting to see that the problems I was having back in December are still persisting in 1.1.
I reluctantly gave up on Deluge on Jan 1st and installed Azureus/Vuze which thankfully does not suffer from any of the problems that Deluge had/has. It takes a few minutes to find the 'classic' user interface but after that, no problems.