Deluge Forum

Hi

I'm on the svn-r 3727 right now and I still face this problem. After a period of time (which is relatively short, say an hour or much less), deluge will suddenly went blank, showing none of my seeds nor downloads. Then there is a "Not connected" display at the status bar. What caused this? I have been having this problem for more than a week already, and I almost do an update on the SVN every night. If I try to use the webui to get in, I get an error message saying that deluge is not connected to the deluge. From my system monitor, I can see that deluged became a zombie. Anyway to work around this? I cannot be restarting my deluge every hour, right?

I take it that the compilation method is still the same?
python setup.py build
python setup.py install

I am on debian sid. Anything else I need to provide to give a more helpful scenario?

Thanks.

I get the exact same thing, except at times it has happened every 2 minutes! Almost like clockwork, even. The torrent list goes blank and it says "Not Connected" in the status bar. Restarting Deluge brings them back, but I lose progress (in other words, I suspect the daemon simply crashed). And then two minutes later, it happens again.

It seems to depend on the torrent, or possibly the tracker for the torrent. For example, every torrent I've downloaded from nyaatorrents.org in the last week or so has caused this issue. But as I learned today, it isn't specific to nyaatorrents.org. Something I was downloading today caused Deluge to go blank every 10 minutes or so, and I wasn't running any torrents tracked by nyaatorrents.org.

I'm running 0.9.08 on Ubuntu Hardy, in Classic mode. I never noticed this issue until just a week or two ago.

bishamon wrote:Hi

I'm on the svn-r 3727 right now and I still face this problem. After a period of time (which is relatively short, say an hour or much less), deluge will suddenly went blank, showing none of my seeds nor downloads. Then there is a "Not connected" display at the status bar. What caused this? I have been having this problem for more than a week already, and I almost do an update on the SVN every night. If I try to use the webui to get in, I get an error message saying that deluge is not connected to the deluge. From my system monitor, I can see that deluged became a zombie. Anyway to work around this? I cannot be restarting my deluge every hour, right?

I take it that the compilation method is still the same?
python setup.py build
python setup.py install

I am on debian sid. Anything else I need to provide to give a more helpful scenario?

Thanks.

you need to `python setup.py clean` and `rm -rf build` before running build. otherwise you'll get a bunch of weird behavior

I've been using the RC 8 package linked to from the front page, and I still get this issue. Nothing relevant seems to be in the log (sometimes the last thing in the log is from a couple of minutes before the crash).

Here's the information I provided in the IRC channel:

(05:55:19) Nanobot: Well, overnight, the torrent list blanking thing happened again
(05:56:19) Nanobot: [DEBUG ] 01:01:48 torrentmanager:551 Saving torrent state file.
(05:56:19) Nanobot: [DEBUG ] 01:01:51 alertmanager:97 tracker_announce_alert: [Mendoi]_Amaenaideyo_Katsu_1-13_[DVD][complete] (http://bt.nanashi-fansubs.com:2710/announce) sending announce (none)
(05:56:19) Nanobot: [DEBUG ] 01:01:51 torrentmanager:678 on_alert_tracker_announce
(05:56:30) Nanobot: Those are the last lines of the log
(05:56:43) Nanobot: markybob
(05:58:25) Nanobot: And I apparently lost all the download progress since the last time I manually restarted Deluge
(05:58:43) Nanobot: *sigh*
(06:00:03) Nanobot: And it went blank again
(06:00:40) Nanobot: Restarting again..
(06:02:40) Nanobot: Blank again
(06:03:03) Nanobot: Last lines in the log file:
(06:03:04) Nanobot: [DEBUG ] 06:01:22 torrentmanager:716 on_alert_tracker_error
(06:03:04) Nanobot: [DEBUG ] 06:01:22 torrentmanager:678 on_alert_tracker_announce
(06:03:04) Nanobot: [DEBUG ] 06:01:22 alertmanager:97 tracker_reply_alert: [Mendoi]_Amaenaideyo_Katsu_1-13_[DVD][complete] (http://tracker.scarywater.net:443/announce) received peers: 40
(06:03:04) Nanobot: [DEBUG ] 06:01:22 torrentmanager:661 on_alert_tracker_reply
(06:03:10) Nanobot: I'm restarting it again
(06:04:04) Nanobot: BTW, the Amaenaideyo torrent was running for a few hours yesterday without incident
(06:05:35) Nanobot: Blank
(06:05:46) Nanobot: Restarting :/
(06:05:52) Nanobot: It's pretty predictable at this point
(06:06:42) Nanobot: I'll try pausing that torrent
(06:07:40) Nanobot: It went blank
(06:08:16) Nanobot: This time I got a weird thing in the log:
(06:08:17) Nanobot: [DEBUG ] 06:06:44 alertmanager:97 hash_failed_alert: Space Pirate Sara uchuu kaizoku sara 宇x87;x87;宙x99;x99;海賊x8a;x8a;ã‚x82;x82;µãƒx83;x83;© vol.01 ã‚x82;x82;®ãƒx83;x83;¼ãƒx83;x83;¬ãƒx83;x83;³ãx81;x81;®åx8f;x8f;Œx8c;x8c;子x90;x90;(DL 704x396 WMV9)[CRC BE86] .avi hash for piece 562 failed
(06:08:17) Nanobot: [DEBUG ] 06:06:58 alertmanager:97 hash_failed_alert: Space Pirate Sara uchuu kaizoku sara 宇x87;x87;宙x99;x99;海賊x8a;x8a;ã‚x82;x82;µãƒx83;x83;© vol.01 ã‚x82;x82;®ãƒx83;x83;¼ãƒx83;x83;¬ãƒx83;x83;³ãx81;x81;®åx8f;x8f;Œx8c;x8c;子x90;x90;(DL 704x396 WMV9)[CRC BE86] .avi hash for piece 432 failed
(06:08:17) Nanobot: [DEBUG ] 06:07:14 alertmanager:97 hash_failed_alert: Space Pirate Sara uchuu kaizoku sara 宇x87;x87;宙x99;x99;海賊x8a;x8a;ã‚x82;x82;µãƒx83;x83;© vol.01 ã‚x82;x82;®ãƒx83;x83;¼ãƒx83;x83;¬ãƒx83;x83;³ãx81;x81;®åx8f;x8f;Œx8c;x8c;子x90;x90;(DL 704x396 WMV9)[CRC BE86] .avi hash for piece 599 failed
(06:08:52) Nanobot: I'll restart and pause that one too
(06:10:37) Nanobot: Went blank
(06:10:53) Nanobot: Uhhh
(06:10:54) Nanobot: [DEBUG ] 06:09:57 alertmanager:97 tracker_reply_alert: [Mendoi]_Amaenaideyo_Katsu_1-13_[DVD][complete] (http://tracker.scarywater.net:443/announce) received peers: 38
(06:10:54) Nanobot: [DEBUG ] 06:09:57 torrentmanager:661 on_alert_tracker_reply
(06:10:59) Nanobot: I had that torrent paused...
(06:11:07) Nanobot: Oh
(06:11:12) Nanobot: That's from a full minute ago
(06:11:36) Nanobot: So basically it didn't log anything between like two seconds after startup and when it crashed
(06:12:05) Nanobot: I'll try removing the seeding torrents and see if it has an effect.
(06:12:42) Nanobot: I have to go to work soon
(06:13:40) Nanobot: It went blank
(06:14:28) Nanobot: Restarting again, this time also pausing everything tracked by nyaatorrents.org
(06:17:39) Nanobot: It's been over 3 minutes and isn't blank yet
(06:17:57) Nanobot: Looks like nyaatorrents is causing problems again. It wasn't causing problems yesterday afternoon
(06:18:17) Nanobot: markybob: Hope this is enough info to help track down the problem

After that point, the blanking issue didn't occur again until almost a full day later, after I added another torrent from nyaatorrents.org.

This problems seems to have appeared in the last couple of RC releases (I think it first appeared in RC 8), and torrents tracked by nyaatorrents.org seem particularly prone to causing this issue. This is a major major showstopper for me, and I hope it gets fixed quickly.