The last 2 hours I've uploaded at least 5 WU's which I cannot find in my total credit nor my pending.
They've just disappeared.
Naturally I've stopped E@H immediately.
Where have these WU's gone ?
Indeed; let it be known that HenkM is not representative of all DPC members. I also don't see what he's trying to prove by being so dismissive; I'm not convinced there isn't or wasn't an actual problem here, even if I don't understand it.
Task ID 170531150
Name p2030_53770_58751_0066_G60.92-00.38.C_0.dm_484_2
Workunit 71652024
Created 12 Apr 2010 10:37:33 UTC
Sent 13 Apr 2010 7:08:01 UTC
Received 13 Apr 2010 7:53:40 UTC
Server state Over Outcome Client detached
Client state New
Exit status 0 (0x0)
Computer ID 2596550
Report deadline 27 Apr 2010 7:08:01 UTC
CPU time 0
stderr out
Validate state Initial
Claimed credit 0
Granted credit 0
application version ---
Why should my machine crunch for several hours and give this output?
The line I highlighted contains the reason.
Gruß,
Gundolf
And the only thing I did was an update-request.
Ands that doesn't explain the detaching.
So the WU/machine was detached but still the cpu crunched for several hours, I checked it with the manager, and after it finished the only thing I did was an update-request.
On our forum it is already said that I've uploaded a WU and finished it afterwards by using that same request.
I stopped crunching AFTER I noticed nothing changed on my account and not before. No reason to do that.
Did a reset and it's running again but I still do not know what has happened.
If you can distill from what I've stated that I made a mistake let me know.
The scheduler marks a task "Client detached" when it has indications that the task is reported by a different host from which the task was sent to.
For some time now I suspect that there is a bug in BOINC that sporadically causes this to happen accidentally. Could you reconstruct what happened between you getting the task and reporting it? Is the machine attached to other projects and where there contacts to other schedulers? It could be that this changed the CPID (cross-project ID) of your hosts...
Task ID 170531150
Name p2030_53770_58751_0066_G60.92-00.38.C_0.dm_484_2
Workunit 71652024
Created 12 Apr 2010 10:37:33 UTC
Sent 13 Apr 2010 7:08:01 UTC
Received 13 Apr 2010 7:53:40 UTC
Server state Over Outcome Client detached
Client state New
Exit status 0 (0x0)
Computer ID 2596550
Report deadline 27 Apr 2010 7:08:01 UTC
CPU time 0
stderr out
Validate state Initial
Claimed credit 0
Granted credit 0
application version ---
Why should my machine crunch for several hours and give this output?
The line I highlighted contains the reason.
Gruß,
Gundolf
And the only thing I did was an update-request.
Ands that doesn't explain the detaching.
So the WU/machine was detached but still the cpu crunched for several hours, I checked it with the manager, and after it finished the only thing I did was an update-request.
On our forum it is already said that I've uploaded a WU and finished it afterwards by using that same request.
I stopped crunching AFTER I noticed nothing changed on my account and not before. No reason to do that.
Did a reset and it's running again but I still do not know what has happened.
If you can distill from what I've stated that I made a mistake let me know.
The scheduler marks a task "Client detached" when it has indications that the task is reported by a different host from which the task was sent to.
For some time now I suspect that there is a bug in BOINC that sporadically causes this to happen accidentally. Could you reconstruct what happened between you getting the task and reporting it? Is the machine attached to other projects and where there contacts to other schedulers? It could be that this changed the CPID (cross-project ID) of your hosts...
BM
The machines were only doing E@H.
As stated before the only thing I sometimes have done is a update-request when the WU's were ready to report. Sometimes when I check some Wu's weren't reported for some time so I thought let's do it myself.
So I haven't doen anything diffrerent from other occasions.
As for now : they seem to be running as they should but I still curious about the reason why I had problems.
RE: The last 2 hours I've
)
Alsof ik de Dutch Power Cows
)
Alsof ik de Dutch Power Cows niet ken.
Donder toch gauw op druiloor.
Stel je zooi goed in.
RE: Alsof ik de Dutch Power
)
Why do you always need two posts for one answer?
Computer sind nicht alles im Leben. (Kleiner Scherz)
Goeie reclame voor DPC!
)
Goeie reclame voor DPC!
Indeed; let it be known that
)
Indeed; let it be known that HenkM is not representative of all DPC members. I also don't see what he's trying to prove by being so dismissive; I'm not convinced there isn't or wasn't an actual problem here, even if I don't understand it.
RE: RE: RE: UPDATE
)
The scheduler marks a task "Client detached" when it has indications that the task is reported by a different host from which the task was sent to.
For some time now I suspect that there is a bug in BOINC that sporadically causes this to happen accidentally. Could you reconstruct what happened between you getting the task and reporting it? Is the machine attached to other projects and where there contacts to other schedulers? It could be that this changed the CPID (cross-project ID) of your hosts...
BM
BM
RE: RE: RE: RE: UPDAT
)
The machines were only doing E@H.
As stated before the only thing I sometimes have done is a update-request when the WU's were ready to report. Sometimes when I check some Wu's weren't reported for some time so I thought let's do it myself.
So I haven't doen anything diffrerent from other occasions.
As for now : they seem to be running as they should but I still curious about the reason why I had problems.