I have 20 or so work units that are stuck at "Ready to report", but won't.

However, I can upload units. The units I am crunching right now upload as soon as they are finished. It is just a pesky few that won't go home. What can I do?

In all due respect why won't you read the main page and some of the posts?

it explains everything that is going on or not hmmmm.....


Tim
[url=http://www.boinc.dk/index.php?page=user_statistics&project=sah&userid=147175]

---

Sit and wait, sadly. Large tracts of the system are down, being moved around bits of suspect hardware. The file upload handler seems to be up - hence you can upload the data. The schedulers (that manage the assignment of work) are not - hence you can't report.

Watch the news column on the right of the home page. There might be an update there. Otherwise, sit tight for a day or so and everything may just sort itself out.

Edit: Or of course, it may not...

Giskard - the first telepathic robot.

SETI@home - 2004-09-06 11:28:01 - Computation for result 04my04aa.14406.25872.690904.110 finished
SETI@home - 2004-09-06 11:28:01 - Starting result 04my04aa.14406.25872.690904.105_0 using setiathome version 4.03
SETI@home - 2004-09-06 11:28:01 - Started upload of 04my04aa.14406.25872.690904.110_2_0
SETI@home - 2004-09-06 11:28:06 - Finished upload of 04my04aa.14406.25872.690904.110_2_0
SETI@home - 2004-09-06 11:28:06 - Throughput 7125 bytes/sec
SETI@home - 2004-09-06 12:09:20 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2004-09-06 12:09:23 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2004-09-06 12:09:23 - No schedulers responded

The uploads work; you just cant report and cant download. I wonder with them moving the uldl data around if all these uploads will get lost and have to be redistributed.

In all fairness, I, as someone who has closely followed the ups-and-downs of this poject and all the news and all the posts over the past weeks and especialy days, don't undesrstand how uploads can be working properly with the admitted hardware failures. It's a bit unfair to criticise another participant who asks the obvious!


> In all due respect why won't you read the main page and some of the posts?
>
> it explains everything that is going on or not hmmmm.....
>
>
> Tim
> <a> href="http://www.boinc.dk/index.php?page=user_statistics&project=sah&userid=147175"> [/url]

Check your transfer tab. There are 2 "ifs" in the first part of this that must both be satisfied.

IF the "Disable Network Access" option is NOT checked and IF there are no units listed in the transfer tab, then your units have been uploaded. Regardless of what it says under the work tab. (Disabling network access prevents units from being listed to the transfer list as processing is completed.)

However, IF there are units listed on the transfer tab waiting to be uploaded, then there is indeed some problem sending units. As far as I know though, uploading shouldn't be a problem for you. So far I've been uploading just fine. But since the project is "technically" down, then I suppose that status could change at any time.

Like Mike though, I'm not entirely sure why the uploads are working right now either since they are dealing with the massive data transfers, but oh well. Seems to me things would at the very least be more efficient with uploads disabled (and with the BBs disabled).

> Like Mike though, I'm not entirely sure why the uploads are working right now
> either since they are dealing with the massive data transfers, but oh well.
> Seems to me things would at the very least be more efficient with uploads
> disabled (and with the BBs disabled).

I was looking for a diagram or protocol document, but I wasn't able to find it right away.

Basically, the upload/download function runs on the data server, and it appears that the data server just has a big directory full of files -- work units for us to download, and results that we've uploaded.

The BOINC client asks for work, and the scheduler checks the database and assigns a list of files. The client then downloads them from the data server, crunches them, and reports results to the scheduler (a file that is "ready to report" has been uploaded, but the scheduler has not been contacted).

Based on what we're seeing, it looks like the scheduler needs the databases (on the SNAP) and the upload function at least caches files when the SNAP isn't there.

Found it: Architecture


> I was looking for a diagram or protocol document, but I wasn't able to find it
> right away.
>

> Found it: <a> href="http://homepage.mac.com/pauldbuck/site-common/glossary/letter-b.html#boinc-system-architecture">
> Architecture[/url]
>
>
> > I was looking for a diagram or protocol document, but I wasn't able to
> find it
> > right away.

That is an expansion of the BOINC diagram that came off the "official" site, and Dr. Anderson was kind enough to verify that this does represent the basic architecture and data flows.

Just keep in mind, this is 40,000 foot level!