results with success, but 0.00 credit?!
11 May 2007 17:46:06 UTC
Topic 192728
(moderation:
please look at the following results, as they are finished, in time, but 0 credit:
about 500 credits earned but not received
these are not the only ones I had,
but i started to be annoyed about this
(I'm sure I had past 2-3 weeks at least one result in this situation, about 160-190 credits,
but it's a good probability there were more)
thank you
results with success, but 0.00 credit?!
)
These results were run with an earlier version of the Linux app, which was known to have problems when validating with other OS platforms.
I also noticed your hosts have been having some Signal 11 issues as well. You might want to do a project reset to clear out all the old stuff and have them start 'clean' with the latest app (4.21) and a fresh batch of results.
You should have to do anything else besides the reset, since I read earlier today that Bernd has moved 4.21 from Beta status to being the production Linux app.
HTH,
Alinator
RE: You should have to do
)
I never reset anything :P (linux fan)
but I have a lot of servers running,
i'll let them do whatever they do (with or without credit :( )
I'm still angry that exactly the hosts I trust (and give more credits) had those SIG11 bugs: 2 dual Xeons! (2x2.66 and 2x3.06 HT procs)
that's why I've set project to Resource share 1 (1-2 days ago to 3)
when I won't see any problems I'll move back to 34 as it was before the "not quite beta, but neither quite final" (!?!@#$) version
You don't have to reset the
)
You don't have to reset the computer, just reset EAH from BOINC Manager so it will DL all new stuff from the project. You should do that even though you've reduced the resource share.
I do understand your being upset the problems on S5R2 though. If you hadn't been following along the Fora regularly, it definitely came as a somewhat rude surprise, especially for Linux users.
In any event, I hope you don't hold against EAH, and come back to help searching for those gravity waves when the app is more mature.
Alinator
I also like to explain to
)
I also like to explain to people that Success Valid.
Success is: downloaded, crunched, uploaded, reported. Everything BEFORE validation.
RE: You don't have to reset
)
It was a joke.
I didn't ever think about resetting a linux server,
any company where these are installed will go crazy!
you mean probably: ./boinc_cmd --project http://einstein.phys.uwm.edu reset
I won't do that, as some hosts may produce good results
I'll let them move to 4.21 by themselves
as I wrote here and here
you can see, I won't detach E@H, and I don't "hold against" them
otherwise, I'd detached it 2-3 weeks ago, not posting here ;)
thanks again for answering
RE: I also like to explain
)
well, those 2 WUs weren't dld, crunched, uld and rep?
if not, what means "success"? only dld :D ?
do you mean it wasn't reported? that's not my fault :)
thank you too
@ Adi: LOL... OK, no
)
@ Adi:
LOL...
OK, no problemo! Sometimes humor doesn't come across well if you aren't writing in your native language. ;-)
Letting BOINC take care of things on its own is certainly an option. The only thing to watch for would be a cascade failure. I had one of my WinBoxes malfunction on an early Win app, and it ended up buring up a full quota days worth of results before I caught it. The only way to stop it from erroring them out in about minute was to reset the project.
Alinator
Success means: A client
)
Success means: A client completed the result successfully.
That's all. :)
RE: Success means: A client
)
That's all well and good and stuff :) , but perhaps a general "reason for rejection" should be implemented on the server side. All this "because success in uploading doesn't mean the result is valid" is exactly that, stating "just because", which can be somewhat irritating. Just glancing at a result generally doesn't give you any idea why it was marked invalid ("rejected"). Having the reason for marking a result invalid in the result report would make it easier to understand why what happened happened...if not by the individual user themself, at least by someone who may come along to help them...
RE: That's all well and
)
thank you, that's what I was trying to ask
lets see:
there are 4 steps: dld, crunch, uld, report
on short:
if dld fails -> dld err
if crunch fails -> compute err
if uld fails -> uld err
if report fails -> unknown
if validate err -> client err or valid err
so, if I see "success", I expect the credits, nothing else
that's my point of view