Re: 0.5.8.3 locks up occasionally
Posted: Sat Feb 09, 2008 9:13 pm
OK, today I ended up deleting ~/.config/Deluge and recreating (after I was getting boost::filesystem::create_directory messages for some reason).
Torrents could then start up fine (no more libboost messages)
I loaded up (at the moment) a total of 84 torrents. Of those 3 are downloads and 81 are seeds (of which currently about 3 are active, including 1 of the downloads which is also actively seeding). The active numbers are, obviously, subject to change.
I haven't minimized this at all, but have just been watching resource utilization and I see a pattern that runs roughly:
1 minute of minimal cpu, followed by about 20 seconds of peak cpu (on 1 of the 2 cpus), followed by 1 minute of minimal, followed by 20 seconds of peak . . .
When it locked up last night there was no drop back down to minimal levels (or at least the drops were few and far between).
As I've been watching the peak time has been extending somewhat (last cycle it extended for 30 seconds rather than 20). The 1 minute low usage portion is, so far, appearing to remain constant.
Occasionally I'll get a dip (giving a short valley) during the peak portion, but that's not the norm. Usually it's a steep climb, folllowed by continuous peak, followed by steep drop.
the peak is now up to about a 40 second duration. The 1 minte low usage is still there.
Now trying to pause a bunch of torrents and see if that impacts things. I selected about 60 torrents (maybe a bit more) and clicked on "pause". This resulted in a delay, followed by which almost all the torrents came back with a tracker status of "announce sent" and a "time to next announce" of 0:00
Finally worked my way through and paused the torrents - this didn't help. Times were still getting longer, separated by a 1 minute low usage gap.
I then removed almost all the torrents, leaving 4 seeding and 2 downloading. This impacted things tremendously.
The cpu peaks dropped to a duration of under 5 seconds, still separated by 1 minute intervals.
So it looks like a tight loop processing some internal torrent table may be the culprit. Why it increases as time passes is another issue, unless the queue is somehow increasing and never getting emptied (unless the torrent is removed).
Hope this helps somehow. Anything I can do just let me know.
Torrents could then start up fine (no more libboost messages)
I loaded up (at the moment) a total of 84 torrents. Of those 3 are downloads and 81 are seeds (of which currently about 3 are active, including 1 of the downloads which is also actively seeding). The active numbers are, obviously, subject to change.
I haven't minimized this at all, but have just been watching resource utilization and I see a pattern that runs roughly:
1 minute of minimal cpu, followed by about 20 seconds of peak cpu (on 1 of the 2 cpus), followed by 1 minute of minimal, followed by 20 seconds of peak . . .
When it locked up last night there was no drop back down to minimal levels (or at least the drops were few and far between).
As I've been watching the peak time has been extending somewhat (last cycle it extended for 30 seconds rather than 20). The 1 minute low usage portion is, so far, appearing to remain constant.
Occasionally I'll get a dip (giving a short valley) during the peak portion, but that's not the norm. Usually it's a steep climb, folllowed by continuous peak, followed by steep drop.
the peak is now up to about a 40 second duration. The 1 minte low usage is still there.
Now trying to pause a bunch of torrents and see if that impacts things. I selected about 60 torrents (maybe a bit more) and clicked on "pause". This resulted in a delay, followed by which almost all the torrents came back with a tracker status of "announce sent" and a "time to next announce" of 0:00
Finally worked my way through and paused the torrents - this didn't help. Times were still getting longer, separated by a 1 minute low usage gap.
I then removed almost all the torrents, leaving 4 seeding and 2 downloading. This impacted things tremendously.
The cpu peaks dropped to a duration of under 5 seconds, still separated by 1 minute intervals.
So it looks like a tight loop processing some internal torrent table may be the culprit. Why it increases as time passes is another issue, unless the queue is somehow increasing and never getting emptied (unless the torrent is removed).
Hope this helps somehow. Anything I can do just let me know.
if this is happening to you, try removing deluge, completely removing ~/.config/deluge, then reinstalling deluge and seeing if it happens again. i have no idea what's going on here.
As mentioned earlier I already had deleted the config folder. I'll try a purge and re-install tomorrow (or maybe later tonight). Although I really would be surprised if that helps long term (short term anything is possible, if it gets better it could well be co-incidence based on what happened to you)