All seeds pausing intermittently

[Marc31]

Transmission happily seeds a hundred or so torrents for days on end (vs 2.82, OS 10.9.1), most of which remain stalled of course, only to every now and then keep all of them waiting to seed, somehow slipped as they have within mere seconds apart according to the message log. Unchanged for years now without any such hiccup ever [edit](vs 2.4x, OS 10.6.x)[/edit], queue is set to 8 active max, 4 minutes of inactivity before stalling, with connections at 32 peers each, 128 globally, and bandwidth as per Help instructions.
But for the Resume All Waiting menu bar command, they’d just sit there and linger on and defeat their purpose altogether.

How does one avert this casual status of apathy coming about?

cheers,

PS one open ticket seems to sort of describe that behaviour reversed.

[Marc31]

Narrowing down the issue I found that a single torrent pausing as it should suffices to trigger all of them to sink into a slack, like so …

Code: Select all

2014-02-18 09:47:30 +0000 torrent.c:499 [Info] 1st torrent: Seed ratio reached; pausing torrent
2014-02-18 09:47:30 +0000 torrent.c:1859 [Info] 1st torrent: Pausing
2014-02-18 09:47:32 +0000 torrent.c:1859 [Info] 2nd torrent: Pausing
2014-02-18 09:47:32 +0000 torrent.c:1859 [Info] 3rd torrent: Pausing
[etc etc (times a hundred or so), up till …]
2014-02-18 09:47:32 +0000 torrent.c:1859 [Info] the very last torrent: Pausing

[edit]
2014-02-18 14:48:42 +0000 Torrent.m:363 [Info] 2nd torrent: restarting because of wakeUp
2014-02-18 14:48:42 +0000 Torrent.m:363 [Info] 3rd torrent: restarting because of wakeUp
[etc etc (times a hundred or so), up till …]
2014-02-18 14:48:42 +0000 Torrent.m:363 [Info] the very last torrent: restarting because of wakeUp
[/edit]

2014-02-18 14:49:08 +0000 torrent.c:1909 [Info] 1st torrent: Removing torrent
2014-02-18 14:49:08 +0000 torrent.c:1859 [Info] 1st torrent: Pausing
2014-02-18 15:07:11 +0000 torrent.c:1859 [Info] 2nd torrent: Pausing
2014-02-18 15:07:12 +0000 torrent.c:1859 [Info] 3rd torrent: Pausing
[etc etc (times a hundred or so), up till …]
2014-02-18 15:07:12 +0000 torrent.c:1859 [Info] the very last torrent: Pausing

[edit]
2014-02-18 16:26:13 +0000 Torrent.m:363 [Info] 2nd torrent: restarting because of wakeUp
2014-02-18 16:26:13 +0000 Torrent.m:363 [Info] 3rd torrent: restarting because of wakeUp
[etc etc (times a hundred or so), up till …]
2014-02-18 16:26:13 +0000 Torrent.m:363 [Info] the very last torrent: restarting because of wakeUp
[/edit]

Does this message log excerpt [edited!] warrant a bug report in addition to the one mentioned earlier? If not, the support request sadly stands.

,

[Marc31]

As an afterthought on this grief I checked other relevant settings, which read (likewise ever since forever):

• -> Transfers - Management -> stop seeding when inactive for: … minutes = unchecked
  -> Network -> prevent system sleep with active transfers = checked

Moreover, seed ratio aside, once all transfers stall every single one of them slips away into the dreaded Waiting-To-Seed state, remaining so until system wakeup as indicated above, quite defeating their purpose on an unattended computer. The in-your-face remedies comprise:

1. -> Transfers - Management -> transfer is stalled when inactive for: … minutes = uncheck, defeating the Queue routine's purpose altogether
2. OS X -> System Preferences -> Energy Saver -> Computer Sleep = never, defeating the purpose of Transmission's corresponding Network setting altogether

Whether to rest my case as is or to hunt up whatever logs for more particulars to open a ticket with, please do advise.

cheers,

PS just yours clueless truly's conundrum? no fellow-sufferers?

[Marc31]

To start off with x190’s second question, as I meant to state previously, 2.42 or thereabouts on OS X 10.6.8 never dozed off like that. As for the first one, 2.82 (having enjoyed as I did a two-year sort of offline sabbatical ) grinds to a halt after system sleep on both OS X 10.9.1 and today's .2 update eventually despite its relevant setting, moreover, regardless of either torrent state change reported (the other being a removal).
Jumping to a conclusion perhaps, by now I must infer that …

prevent system sleep with active transfers

… no longer delivers.

awaiting his or hers input to get this fixed, or anyone’s for that matter
cheers,

[Marc31]

Have you tried a longer "inactivity" period?

I have, to no avail. Apparently the present array of seeds is not quite as impressive and this post comes down to my misconception about the different states of a transfer, active vs inactive = either stalled, waiting to seed, or paused.
Still, a stalled one keeps announcing itself to the tracker, a kind of active inactivity so to speak, yet Transmission chooses not to interfere with system sleep, which puts of all them on hold (thus bypassing the wake-for-network-access Energy Saver setting too). A request to alter this would be asking for the impossible, I suppose.

anyway, cheers, + kudos to the dev(s) ,