Suddenly no work is being sent and I see the following message:
1/6/2016 6:27:04 PM | Einstein@Home | see scheduler log messages on http://einstein5.aei.uni-hannover.de/EinsteinAtHome/host_sched_logs/11547/11547884
The Page does not exist so not sure where to look about this.
Anyone else having this issue or a resolution?
Thanks!
Peter
Copyright © 2024 Einstein@Home. All rights reserved.
No Work Sent (see Scheuler Log) Error?
)
Go to your computers list on the website and click the link at the far right under the "Last contact" heading. This is a record of what happened during the last exchange with the scheduler. Here is an excerpt
From the above, your host is not requesting CPU work (0.00 seconds) but is requesting Intel GPU work (691200 seconds - rather a *lot*)
The last task you completed was an FGRP4 CPU task so if you're not requesting these any more it has to be due to you changing your preferences in some way to exclude that particular science run or perhaps CPU work in general? Have you made any preference changes recently?
Are you trying to get Intel GPU work? That's a bit of a can of worms unless you really know what you are doing :-).
There are several existing threads that go through the problems, particularly relating to driver versions that allow useful results that will validate when returned. You should research those threads if you intend to use your integrated GPU.
Cheers,
Gary.
RE: From the above, your
)
So do you have other BOINC project enabled on your machine? Work onboard for other(s) might have your copy of BOINC deciding you don't need more Einstein CPU work just now. It is your host that is not requesting--not Einstein that is denying it CPU work.
Yes indeed, maybe Einstein's
)
Yes indeed, maybe Einstein's resource share is low enough for BOINC not to be interested in requesting more Einstein CPU work yet.
I (sort of) discounted that because there is just one FGRP4 task still showing and it was sent and returned quite a while ago so no real evidence that Einstein was being overly favoured in the more recent past. Of course, if a lot of projects are active, resource share of each will be quite low anyway so it wouldn't take many tasks for one particular project for BOINC to ban that project for quite a while.
The other thing I should have pointed out in my initial response was that the large GPU task request indicated cache settings that seem inappropriate for the number of projects to which the machine is attached - 12 all told. This will exacerbate the situation where one project may end up supplying far too much work at one point, leading to high priority mode crunching and then an extended period of not being able to request more work for that project due to resource share constraints. Depending on how many of the 12 are actually active, a work cache setting of much more than a day or two is probably asking for trouble.
Cheers,
Gary.
Thanks Gary, I reduced by
)
Thanks Gary,
I reduced by work cache to 2 days and will see what happens (will reduce further if needed).
The other projects don't seem to be having issues but each is different I guess.