OK, is it clear on the front page of the website that the project needs a
continuously on network connection?
You can solve your problem by not marking the task as done until the final
communications with the server is completed. Then the report will be
guaranteed to arrive after the upload.
jm7
Rytis
Slatkevičius
<[email protected] To
m> [email protected]
Sent by: cc
boinc_dev-bounces BOINC Developers Mailing List
@ssl.berkeley.edu <[email protected]>,
[email protected]
Subject
09/14/2009 08:36 Re: [boinc_dev] Multiple sched
AM requests with no output files
The whole nature of the project is network based and non-cpu-intensive.
BOINC can't and won't do what we need on it's own.
2009/9/14 <[email protected]>
> Please, Please, Please, let BOINC do the network communication. BOINC
may
> have been told not to allow network communication, and you should respect
> that. The modem may be off, or the rates may be much higher during the
> early evening, or ...
>
> jm7
>
>
>
> Rytis
> Slatkevičius
> <[email protected] To
> m> BOINC Developers Mailing List
> Sent by: <[email protected]>
> boinc_dev-bounces cc
> @ssl.berkeley.edu
>
Subject
> [boinc_dev] Multiple sched requests
> 09/12/2009 04:19 with no output files
> AM
>
>
>
>
>
>
>
>
>
> Hello all,
> I'm working on a project which is non-cpu-intensive and does not have
> result
> files (instead, all network communication is done by the app itself).
This
> causes an interesting phenomenon when a workunit finishes:
>
> *20:29:27 AProject Computation for task pinger_15571_0 finished
> 20:29:27 AProject Sending scheduler request: To fetch work.
> 20:29:27 AProject Requesting new tasks
> 20:29:32 AProject Scheduler request completed: got 1 new tasks
> 20:29:35 AProject Starting pinger_15796_0
> 20:29:35 AProject Starting task pinger_15796_0 using pinger version 103
> 20:29:43 AProject Sending scheduler request: To report completed tasks.
> 20:29:43 AProject Reporting 1 completed tasks, not requesting new tasks
> 20:29:48 AProject Scheduler request completed*
>
> As you can see, a task finishes and immediately a scheduler request is
> done,
> because there is no more work in the queue, however, the WU that has
> finished hasn't yet reached ready_to_report state, so it is not reported.
> Instead, it is reported on a separate sched request, as soon as the first
> scheduler request (to fetch new work) is completed.
>
> This would be fine if we were doing file uploads, because then the
workunit
> would not be ready_to_report until the file upload was complete, but in
> this
> case there is no file upload.
>
> Tested with 6.2.19, 6.6.36, 5.10.45 - same issue, although it does not
> always manifest itself. Some users have it more often, some don't at all.
>
> --
> Rytis Slatkevičius
> +370 670 77777
> ICQ 270359185; MSN [email protected]; GTalk [email protected]; Skype
> rytis.s
> (text only)
> _______________________________________________
> boinc_dev mailing list
> [email protected]
> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.
>
>
--
Rytis Slatkevičius
+370 670 77777
ICQ 270359185; MSN [email protected]; GTalk [email protected]; Skype
rytis.s
(text only)
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
