Tue Dec 15 12:42:41 2009 Einstein@Home Sending scheduler request: To fetch work.
Tue Dec 15 12:42:41 2009 Einstein@Home Reporting 1 completed tasks, requesting new tasks
Tue Dec 15 12:42:42 2009 SETI@home Computation for task 07mr07ab.9040.2936.14.10.37_1 finished
Tue Dec 15 12:42:44 2009 SETI@home Started upload of 07mr07ab.9040.2936.14.10.37_1_0
Tue Dec 15 12:42:46 2009 Einstein@Home Scheduler request completed: got 1 new tasks
Tue Dec 15 12:42:46 2009 Einstein@Home Message from server: No work can be sent for the applications you have selected
Tue Dec 15 12:42:46 2009 Einstein@Home Message from server: You have selected to receive work from other applications if no work is available for the applications you selected
Tue Dec 15 12:42:46 2009 Einstein@Home Message from server: Sending work from other applications
Tue Dec 15 12:42:48 2009 Einstein@Home Starting h1_1112.15_S5R4__866_S5R6a_0
Tue Dec 15 12:42:49 2009 Einstein@Home Starting task h1_1112.15_S5R4__866_S5R6a_0 using einstein_S5R6 version 501
Not sure why I am getting this. Doesn't seem to affect downloads.
Jim
Copyright © 2024 Einstein@Home. All rights reserved.
Why am I getting this message?
)
Same here.
Maybe some server (mis-)configuration.
Michael
Team Linux Users Everywhere
RE: Not sure why I am
)
As a general comment to anyone reading this, if you ever see a message like this that seems a bit odd and for which you would like more info, the scheduler logs are your friend. Take a look at the sticky thread in this very forum that Bruce posted a long time ago about the scheduler logs.
One thing that makes this quite easy is that the time of last contact shown on your computers list is a clickable link to the appropriate scheduler log so you don't even have to work out how to find the correct log - if you're quick and there is no subsequent contact to spoil the party. Since this was the case here, below is the relevant log snippet that I found with a single click and a search for 712103. The hostID for Jim's computer is 712103. This snippet reveals the 'thinking' of the server concerning the request it received from Jim's host.
I don't claim to be any great shakes at interpreting scheduler logs so I'll just give a rough outline of what it means to me. I invite anyone with a more detailed interpretation to please join in.
To me it looks like the scheduler thought it might be able to send some old S5R5 work but in the end it concluded that the best option was to just send an S5R6 task (taskID #151245075) which you now have in your cache. The messages at the end of the snippet are to tell the client that the request for S5R5 work couldn't be honoured and that S5R6 work was sent instead. I don't really know why it felt the necessity to tell this to the client. I also don't understand why it talked about removing the l1_1112.xx files while confirming the h1_1112.xx files near the start of the snippet. Maybe there's a bit of a bug in the current locality scheduling algorithm.
PS: I've just noticed that the host has made further (later) contact and by checking the newer log, the same type of exchange has occurred. It wasn't just a once off.
Cheers,
Gary.
RE: To me it looks like the
)
There probably is, but not visible here ;-)
I recently switched on a bit more debugging output to find things that need to be fixed in the locality scheduling.
Since the launch of the Radio Pulsar search Einstein@home is actually calling two different scheduler codes to serve both types of work:
The Radio Pulsar search (ABP1) is an ordinary ('non-locality') BOINC type of work, where one data file is downloaded for every task, and after processing the task it is deleted from the client (and even from the server when the workunit is done).
The Gravitational Wave search (S5R6) is 'locality work': The same set of data files is used for multiple workunits. So the whole server (locality scheduler, workunit generator and even transitioner) tries to generate, find and assign tasks to the client that minimizes its download volume.
At each scheduler contact one scheduler part gets called first to handle the client request, then the other one gets called to fill up if more work is requested than the first scheduler part could send. Which scheduler part gets the first chance to send work is chosen at random at each contact, the current setting is 70% locality, 30% non-locality. We call this 'mixed' scheduling.
From the cited log you can see that locality work was sent first ("[mixed] sending locality work first").
The locality scheduler removes everything that is not a 'trigger' (i.e. the beginning of a workunit name) from an internal structure named 'file_infos' list. As far as I can see, the behavior of the 'locality scheduler' is correct.
The message apparently comes from the 'non-locality scheduler' that is called second ("[mixed] sending non-locality work second").
Honestly I don't know yet where it comes from, but I'll look into that. It's definitely a problem on the server side.
BM
BM
Thanks, Bernd, for taking the
)
Thanks, Bernd, for taking the time to explain it all. The things I didn't understand make sense now.
Cheers,
Gary.
RE: The message apparently
)
Possibly having a non-CUDA GPU in the system? I see similar messages on the GPU work request that my ATI GPU does once in a blue moon, on different projects.
I just did an update and got this:
16-Dec-09 08:00:58 Einstein@Home update requested by user
16-Dec-09 08:01:01 Einstein@Home [sched_op_debug] Starting scheduler request
16-Dec-09 08:01:01 Einstein@Home Sending scheduler request: Requested by user.
16-Dec-09 08:01:01 Einstein@Home Requesting new tasks for GPU
16-Dec-09 08:01:01 Einstein@Home [sched_op_debug] CPU work request: 0.00 seconds; 0 idle CPUs
16-Dec-09 08:01:01 Einstein@Home [sched_op_debug] ATI GPU work request: 864.86 seconds; 1 idle GPUs
16-Dec-09 08:01:06 Einstein@Home Scheduler request completed: got 0 new tasks
16-Dec-09 08:01:06 Einstein@Home [sched_op_debug] Server version 611
16-Dec-09 08:01:06 Einstein@Home Message from server: No work sent
16-Dec-09 08:01:06 Einstein@Home Message from server: No work is available for Hierarchical S5 all-sky GW search #5
16-Dec-09 08:01:06 Einstein@Home Message from server: No work available for the applications you have selected. Please check your settings on the web site.
16-Dec-09 08:01:06 Einstein@Home Project requested delay of 60 seconds
16-Dec-09 08:01:06 Einstein@Home [sched_op_debug] Deferring communication for 1 min 0 sec
16-Dec-09 08:01:06 Einstein@Home [sched_op_debug] Reason: requested by project
Looks familiar? ;-)
RE: Looks familiar?
)
Vaguely ;-)
But I get exactly the same, even without GPU (of any kind):
16/12/2009 06:58:48|Einstein@Home|[sched_op_debug] Starting scheduler request
16/12/2009 06:58:48|Einstein@Home|Sending scheduler request: To fetch work. Requesting 7 seconds of work, reporting 0 completed tasks
16/12/2009 06:58:53||[unparsed_xml] APP_VERSION::parse(): unrecognized: 1.000000
16/12/2009 06:58:53||[unparsed_xml] APP_VERSION::parse(): unrecognized: 1.000000
16/12/2009 06:58:53||[unparsed_xml] APP_VERSION::parse(): unrecognized: 1355697238.732052
16/12/2009 06:58:53||[unparsed_xml] RESULT::parse(): unrecognized:
16/12/2009 06:58:54|Einstein@Home|Scheduler request succeeded: got 1 new tasks
16/12/2009 06:58:54|Einstein@Home|[sched_ops_debug] Server version 611
16/12/2009 06:58:54|Einstein@Home|Message from server: No work can be sent for the applications you have selected
16/12/2009 06:58:54|Einstein@Home|Message from server: You have selected to receive work from other applications if no work is available for the applications you selected
16/12/2009 06:58:54|Einstein@Home|Message from server: Sending work from other applications
16/12/2009 06:58:54|Einstein@Home|Project requested delay of 60.000000 seconds
16/12/2009 06:58:54|Einstein@Home|[sched_op_debug] Deferring communication for 1 min 0 sec
16/12/2009 06:58:54|Einstein@Home|[sched_op_debug] Reason: requested by project
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
RE: But I get exactly the
)
You just need to update your BOINC, so it recognizes what an app_plan is. :-)
Should be fixed now. If you
)
Should be fixed now. If you still get this message, please post here.
BM
BM
RE: 2009-12-17
)
I would expect it to say "You don't have an NVIDIA GPU", but alas, it doesn't.
RE: I would expect it to
)
Hm. I could see that the message is a bit too general. It means that though you have selected to get GPU work (too) the project has no GPU work that could be sent to your machine.
But anyway - that's a (slightly) different message and a different problem than what I was addressing.
BM
BM