What's printed in the 5 lines after the last log line you posted?

--//--

Problem is continuing,
I understand that DDDT2 will not be available for months.
If I were to post the last lines currently they would be as above with a later time stamp.

Usually these lines are followed by notes saying that there is no work for the projects selected and a few more comment lines, to visit the website etc. If there are not, that's a first puzzle.

You are suggesting also in your OP that you did *not* select the top 2 of 6 lines (or 1 if you folded DDDT-2 and DDDT2-A type together)

6/29/2012 8:25:17 AM World Community Grid Message from server: No tasks are available for Computing for Sustainable Water
6/29/2012 8:25:17 AM World Community Grid Message from server: No tasks are available for Say No to Schistosoma

Which is even stranger. Think this is just a temp glitch or feeders having backlog. My clients are properly back-filling with DSFL/CFSW/GFAM/SN2S

--//--

edit: Ah, the self solution... this is which is why we like a fuller set of lines but the few a member is homing in on. In this case GPU work is presently not allowing specifying specific projects, it will ask all project you've selected., but still would not have queried queues for work you have not for CPU computing, AFAIK.

Mind if I join you over a cup of coffee Cappuccino?

"No CPU tasks..." or "No GPU tasks..." would have clarified things so much better than the plain "No tasks..." just like a Cappuccino is so much tastier than plain coffee.
;
; edit1_2012.06.30Sa.2034.utc > spell-check
;

<comment>One thing is, the reliance on context gives rise to a potential for ambiguity when either the context is removed from the message or the message is removed out of the context. Given that all sorts of events happen near-simultaneous, the log is thus populated by messages with different context multiplexed together sometimes in no particular pattern. Finding which context belong to which message in this 'noisy' environment may be not as straightforward as we would like to guarantee the connection between the dependent-message and the parent-context. Inserting qualifying words reduces-, if not removes-, the reliance of messages on context and thereby makes any message able to tolerate the 'noise' much better.

Awareness need to come first, and the pros and cons debated, before the appropriate changes can be coded in.