I get them too. Only at startup. The torrents usually switch to a normal state around the time they check in with the tracker. Since I have 1000+ torrents it takes a minute or two. But in the past, with earlier versions of the software, I would get some torrents that stuck around in state 7, sometim...

Fixed it. First off, the watermark warnings were mostly a red herring. I fixed them and it did not improve utilization. So I poked around the source code for libtorrent and noticed a function "session::high_performance_seed()" that set a bunch of variables designed to maximize seeding per...

I used to get that, but then I made it a habit to turn off "auto-managed mode" for all of my torrents and I don't see it any more.
I never really could figure out the point of "auto-managed mode" in the first place, all the docs were too vague.

I get those every once in a while on my ubuntu system, but there is no correlation with any other problems.

There are a couple of unresolved threads here reporting slow upload rates with 1.3.x - one of which I started myself.

You could try turning on logging with:

--loglevel=info --logfile=/tmp/deluge.log

You might find a clue in there.

If you specified loglevel "debug" and got nothing in the log file, then you did something wrong.
Just starting up deluge should log a bunch of messages for each torrent.

To follow up, I ran the daemon with debug logging turned on and I am seeing a ton of messages like the following: [DEBUG ] 20:14:29 alertmanager:123 performance_alert: Sita1080FLAC.mkv: performance warning: send buffer watermark too low (upload rate will suffer) By "a ton" I mean roughly 3...

This past weekend I upgraded my deluged system from Ubuntu 10.04 server with a custom kernel to Ubuntu 10.10 server with the official kernel. But things have become slow and I am out of ideas to check. I had been running deluged 1.2.3 and now am using the 1.3.0 packaged with Ubuntu 10.10. The OS upg...

I was seeding about 1200 torrents. Deluged 1.2.3 crashed with a segfault. When I restarted it, it only found about 700 torrents. I had to manually re-add the other 500 torrents, which was terribly painful for me because I rename the parent directory of each torrent to follow standardized naming sche...

Look inside core.conf in each config directory. Some of the variables include full paths, particularly the state_location entry which defines what torrents the client is working with. Just copying them like you did is not enough. You should also look at the torrents.state file, it specifies the path...