This PC, 4280432, is not receiving any Einstein WUs but is happily receiving Milkyway and Seti WUs. My other PC is receiving Einstein WUs.
I've tried resetting the project and resetting/setting other bits and pieces to no avail.
I have not modified, or even looked at, the various control files on disk.
Any suggestions welcome.
BobMALCS
Copyright © 2024 Einstein@Home. All rights reserved.
Why am I not getting any Work Units
)
The easiest possibility is that nothing is wrong--just your boincmgr thinks you have done enough Einstein for the moment and is not requesting any more until your other projects get into good enough share balance at it sees it.
Have you looked at the message log to see whether your PC is making requests of Einstein? You are running 7.0.28, so this would mean Advanced|Event Log, then scrolling through.
In that format, here is a successful Einstein work request as seen on one of my hosts, which happened to want GPU work at this time:
You can also ask the Einstein server what the most recent work request for you host looks like. Here is a link for that information for your host:
host 4280432 most recent work request
At the moment I am writing this, that links shows these in these three lines that just before the end of July 24 UTC, your host requested zero work.
Others here may be better able than I to help you see better the status of the competing projects on your host.
My own recommendation is patience and watchful waiting.
I am having the same problem.
)
I am having the same problem. I first noticed it with albert, and now einstein. The machines have only this project attached for GPU tasks. They were getting work just fine, and just now BOINC has stopped asking for more work, even when the queue is dry, and the GPUs are idle. I've never seen this "project is not highest priority" comment before.
I am not having this problem with other machines on other GPU projects. All running 7.0.31.
107096 Einstein@Home 7/24/2012 7:23:23 PM update requested by user
107097 Einstein@Home 7/24/2012 7:23:28 PM [sched_op] Starting scheduler request
107098 Einstein@Home 7/24/2012 7:23:28 PM Sending scheduler request: Requested by user.
107099 Einstein@Home 7/24/2012 7:23:28 PM Not requesting tasks: project is not highest priority
107100 Einstein@Home 7/24/2012 7:23:28 PM [sched_op] CPU work request: 0.00 seconds; 0.00 devices
107101 Einstein@Home 7/24/2012 7:23:28 PM [sched_op] ATI work request: 0.00 seconds; 0.00 devices
107102 Einstein@Home 7/24/2012 7:23:29 PM Scheduler request completed
107103 Einstein@Home 7/24/2012 7:23:29 PM [sched_op] Server version 611
107104 Einstein@Home 7/24/2012 7:23:29 PM Project requested delay of 60 seconds
107105 Einstein@Home 7/24/2012 7:23:29 PM [sched_op] Deferring communication for 1 min 0 sec
107106 Einstein@Home 7/24/2012 7:23:29 PM [sched_op] Reason: requested by project
Reno, NV Team: SETI.USA
I just attached my new HP 635
)
I just attached my new HP 635 laptop with its AMD E2-450 APU. SLES 11 Linux, to Einstein@home and got 2 tasks, a Lineveto and a binary pulsar search. They are running together, with graphics. BOINC client is good old 6.10.58.
Tullio
From the event
)
From the event log:
25/07/2012 00:29:39 | Einstein@Home | Sending scheduler request: Requested by user.
25/07/2012 00:29:39 | Einstein@Home | Not reporting or requesting tasks
25/07/2012 00:29:41 | Einstein@Home | Scheduler request completed
I have no Einstein WUs at all. Both SETI and Milkyway are working as expected.
On the projects tab I have Einstein/Milkyway/SETI with resource shares set as 105/5/5 with Average Work Done 5945/4779/1050 with the value for Einstein slowly decreasing each day.
For no apparent reason, the
)
For no apparent reason, the hosts started asking for tasks again last night, after sitting idle for hours. The BOINC scheduling code an enigma...sometimes to the developers too...
Reno, NV Team: SETI.USA
For no apparent reason I
)
For no apparent reason I started to get Einstein WUs again. So everything should get back to what passes for normal again.
Personally speaking, if a scheduler I wrote behaved in this fashion I would be concerned.