Upload Queued ?

[TheBard]

Im new to this game, but I have an odd situation that I cant find an answer to, having browsed around for a while.

How is it that I can have an upload item queued, when it is the only item I have in my library and the only item I even have in my Vuze Download folder on my hard disk?
When first seeded, it checks out ok and then says: "Seeding" but within a minute or so, it reverts to "Queued" and sticks there!

Im using a Mac btw.

Im clearly missing something obvious, but as a noob, Im stumped !
all help gratefully accepted!

[parg]

By default if there are no peers for an upload it enters a queued state to save resources - could that be it?

[TheBard]

By default if there are no peers for an upload it enters a queued state to save resources - could that be it?

 

ah - it might be.

that means is will not show up as seeding unless and until someone starts to download on the other end?
the person who originally requested the seed is not currently online, so when he comes back on and hits download on his end, it will automatically start seeding?

Thank you for your swift reply.

[parg]

right, there's a queueing rule (Tools->Options->Queue->Seeding->First Priority: Ignore torrents with 0 peers that can disable this behaviour, but once peers appear the download should automatically start seeding)

[TheBard]

right, there's a queueing rule (Tools->Options->Queue->Seeding->First Priority: Ignore torrents with 0 peers that can disable this behaviour, but once peers appear the download should automatically start seeding)

 

Thank you - Ill try that. My time zone means that Im often uploading at times when others are not online to grab, and then, by the time that they do come online and are looking to download, Im asleep and my system is queuing files, rather than seeding! We get stuck in a Kafka-esque spiral :)

[billyboy999]

Apologies for resurrecting from the dead, but I was encountering a similar problem after reinstalling Vuze. I re-added a bunch of torrents but most of them would stayed Queued instead of Seeding. Only a few would seed, and it was always the ones that were marked "1st priority". Setting a torrent to "force start" would work but it wasn't idea.

The problem was this setting: Queued->Maximum 'stalled'". This was set to 5 (by default). When I set it to 0, all my torrents instantly started up at once. Some of them found peers and started uploading too, so it wasn't that Vuze detected there were no peers and left it queued like hypothesized above. 

I currently have about 25 torrents seeding, and most of them don't have any activity at any given time, so it would trigger this condition very easily.

[ekstasee]

Read and do the following and I'm certain you will be happy.

Since Spiggot sacked their main developer, these forums seem to rely on the goodwill of ONLY other users.  I suggest you UPGRADE to BiglyBT and enjoy what is essentially the same client with more features, without the bullshit and is in constant development by one of the original Azureus developers.  Plus, there are dedicated support chat channels built into the client and during the install process, you can easily migrate all of your Vuze/Azureus settings/statistics and torrents to the BiglyBT client.

I run over 3,000 torrents, so don't worry, the client will handle your torrents with ease and I had no problems with the migration of settings and torrents. It was all seamless. BBT looks the same as Vuze and it is legal because they (BiglyBT, Vuze, Bit-Tyrant, OneSwarm) are all based on Azureus under a GPL License.