Work Unit Completed & Uploaded; Einstein Server Indicates Same WU In Progress
31 Jul 2005 20:45:47 UTC
Topic 189643
(moderation:
Result ID: 6911262
My Computer (14439) indicates that workunit 1644342 (w1_0675.5__0675.5_0.1_T13_S4hA_3) completed & uploaded at 2005-07-31 13:51 (GUT).
The Einstein results server indicates that this workunit is 'in progress' as of 2005-07-31 20:42 (GUT).
Is this discrepancy;
a) due to a backlog on the Einstein server or other timing discrepancy, or
b) indicative of a problem?
For the record:
1. the system was upgraded from 4.19 to boinc_4.43_i686-pc-linux-gnu on 2005-07-27 00:07 (GUT),
2. the workunit was sent to my system on 2005-07-27 00:08 (GUT),
3. the workunit was started on my system 2005-07-27 00:09 (GUT).
Work Unit Completed & Uploaded; Einstein Server Indicates Same W
)
The upload and reporting of a result is a 2 stage process. First the host uploads the result, then it reports the result to the scheduler. Do you know if the host actually has reported the result to the scheduler yet?
Then you're really interested in a subject, there is no way to avoid it. You have to read the Manual.
RE: The upload and
)
Do I know? No. How would I tell?
What I have to go on are the messages in the boinc.log. The 'start upload', 'finished upload' and 'throughput' messages appear normal for the workunit in question judging by previous successful completions.
The oddness is the discrepancy with the server's status report.
n.b.
There's a lot about the application I don't capiche. Would love to see a diagrammatic overview of the application; input files, output files, steps executed.
Uploading means to upload the
)
Uploading means to upload the result file to the upload server. Reporting means that the completion (and uploading) is reported to the scheduler. So the next message contacting the scheduler will look something like "Requesting xxx seconds of work, reporting 1 result" (if your client is new enough to write this message, the older ones don't log reporting). Only after that report the database will know of the Result being finished. You can manually initiate a scheduler contact by using the "update" function on the project.
BM
BM
RE: Uploading means to
)
Unfortunately my 'update' isn't working for me as 'boincmgr'
didn't configure properly from the self-install (I'll post that as a separate query). But with your explanation I was able to kludge it by stopping the app and fiddling the global_prefs.xml & client_state.xml and re-starting.
Thanks, got it done.