I have three boxes crunching for E@H. One of which, for the last week, can only download a single task.
Unfortunately, the normal duration of a task is around 15 hours so I can only crunch one task a day and the box is then idle for up to 9 hours.
Has anyone a similar experience?
My other two boxes have no problems at all and yesterday my dual core obtained twelve new tasks so it is clearly not a shortage of work.
Any comments or advice gratefully received.
Copyright © 2024 Einstein@Home. All rights reserved.
pc is being drip fed with one task/day
)
You could check the Long Term Debts for that machine. If there seems to be something amiss, try the clause in cc_config.xml. (Don't forget to remove it again, afterwards.)
Or else the section from client_state.xml could give hints.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Won't be anything to do with
)
Won't be anything to do with debt, Gundolf, if the box is idle.
At first I thought it sounded more like a continual error which had brought quota down to 1, but looking at host 1943707, that doesn't seem to be the case.
Ashj, if you have a careful look at that list - and watch out, they aren't in chronological order - you'll see that you're actually being sent a new task at the same time at the previous one is reported - you should only be losing a few seconds while they're uploaded/downloaded.
But even so, it shouldn't be happening, and it makes sense to try and sort it out. Have a look at the bottom of the computer details (you can see much more on that page than we can). What are the four figures at the bottom, and how do they compare with -
Post your figures here, and we can advise further.
Hi Richard, These are my
)
Hi Richard,
These are my figures:
% of time BOINC client is running 98.9988 %
While BOINC running, % of time host has an Internet connection 3.7519 %
While BOINC running, % of time work is allowed 99.9071 %
Task duration correction factor 1.721775
I do not leave the box online until I need a connection.
Unfortunatly I do need some shut eye so the nine hours lost is always past midnight (GMT +1).
With Regards
ashj
Hi, taken from scheduler
)
Hi,
taken from scheduler logs:
HTH
Michael
Team Linux Users Everywhere
The time fractions are OK
)
The time fractions are OK (except for internet connection, and you've explained that).
It'll be
(0.35 days) - probably 0.1 days connect interval, 0.25 days additional cache.
If you're only seeing this for one out of three hosts, maybe you accidentally set those as local preferences? Check 'Preferences' both on your account pages and in BOINC Manager.
I have reset preferences
)
I have reset preferences to:
Internet connection to every one day and enough work for an additional 3 days.
I updated on line with E@H and then requested more work but do far without any joy.
Will try again at the next submission.
Thanks for the input from all contributors.
RE: I updated on line with
)
You didn't say anything about local preferences. Did you try the "Clear" button?
What about the different venues (home, school, work, default)?
Computer sind nicht alles im Leben. (Kleiner Scherz)
Hi, are you getting "won't
)
Hi,
are you getting "won't finish in time" messages? There seems to be a problem with BOINC 6.6.36, consider upgrading, see SETI thread too.
HTH
Michael
Team Linux Users Everywhere
RE: Hi, are you getting
)
That would need v6.6.38, only compiled yesterday evening: I wouldn't upgrade to that until some of the people moaning on the BOINC message boards about 'High Priority' running get their debugger logs out and post some metrics.
I think that your server log about work request, plus the fact that he's been getting a new task at each manual connection, is enough of an answer for this thread.
RE: [I wouldn't upgrade to
)
That's just a side effect of the fix, since the bug wrecked the long running estimate of deadlines (one that's stored on the server, no less!). I noticed it goes away after either running halfway through a task, or running at least one task.
But moaning is correct, people expect a bug to be fixed and their BOINC to magically reset all numbers to pre-bug time.