Summary: It seems the XML server status report is missing the V8 tasks. Therefore, BOINCstats shows wrong data for project status for SETI@home.

Details: Right now, http://boincstats.com/en/page/projectStatusInfo thinks that SETI@home has only less than a handful tasks ready to be sent out and 20x less tasks in progress, as opposed to what http://setiathome.berkeley.edu/sah_status.html shows. Turns out, BOINCstats reads http://setiathome.berkeley.edu/sah_status.xml and that XML doesn't seem to have the right numbers:

<sah_results_ready_to_send>2</sah_results_ready_to_send>
<ap_results_ready_to_send>0</ap_results_ready_to_send>
<sah_v8_results_ready_to_send>0</sah_v8_results_ready_to_send>
. . .
<sah_results_in_progress>38446</sah_results_in_progress>
<ap_results_in_progress>150109</ap_results_in_progress>
<sah_v8_results_in_progress>150109</sah_v8_results_in_progress>

compared to what the human readable page shows:

Data Distribution State     SETI@home v7 #     Astropulse #     SETI@home v8 #     As of*
Results ready to send               2                   0            540,576          0m
Results out in the field       38,446             150,109          4,089,293          0m

Notice how the two V8 lines simply repeat the data in the preceding AP lines. If you inspect the rest of the XML from the link above, you'll notice that is the pattern for EVERY V8 entry, so there is a much greater issue here than just those two numbers.

The original thread on BOINCstats: https://boincstats.com/en/forum/5/10756,1#140622

Thanks
Tuna

---

And, for SETI@Home Beta, assuming http://setiweb.ssl.berkeley.edu/sah_status.xml is supposed to match http://setiweb.ssl.berkeley.edu/beta/server_status.php, well, they don't, leading to a similar problem on BOINCstats for that project, also. Even if that is not the right XML I am looking at, BOINCstats has the same issue with SETI@Home Beta, so there must be an XML not matching the Server Status page.

Tuna

Despite having different URL Seti Main and Beta are actually served from the same web server. To reach Beta web pages you must always include /beta/ in the URL.

http://setiweb.ssl.berkeley.edu/sah_status.xml is actually status of the Main project since the URL lacks /beta/ .

Beta status web page is stock BOINC server status page. You can get the XML version by including xml=1 parameter in the URL.

http://setiweb.ssl.berkeley.edu/beta/server_status.php?xml=1

So,

Human readable forms are on http://setiathome.berkeley.edu/sah_status.html for main and on http://setiweb.ssl.berkeley.edu/beta/server_status.php for beta, by just following the links on the project sites.

For beta, your pointer to http://setiweb.ssl.berkeley.edu/beta/server_status.php?xml=1 seems to reflect the numbers on the human readable page. Thanks!

For main, however, BOINCstats is looking at http://setiathome.berkeley.edu/sah_status.xml and you say http://setiweb.ssl.berkeley.edu/sah_status.xml is that of main, and they both seem to be the same file anyways, and they are both NOT reflecting the human readable data. Doing something like http://setiweb.ssl.berkeley.edu/server_status.php?xml=1 returns 'Server Error 500'.

I sent a PM to Matt after posting here. I don't know if Matt reads PMs or if he's at the desk and even if he does read the PM when he'll have time to do something about the XML version. You'll just have to wait.

Thanks!

Bump. ClimatePrediction had a similar issue, which I had reported and they just fixed. I am hoping that SETI will be fixed, too, sooner than later... :)

Bump. Now that virtually all tasks pushed out are v8, the current XML file communicating the server status to external sites is essentially useless without this getting fixed.

Thanks
Tuna

You might want to see if email reaches the admins better than PMs.

I imagine that once the MB v7 data is removed that numbers will be accurate & that there will only be <sah_results_ready_to_send> & <ap_results_ready_to_send>. With the sah_v8 fields removed.

Also I'm not sure if the person that normally handles that kind of thing is in the lab. As Eric had mentioned at one point last year that they only knew they had funding the keep Matt around for the first half of the year. So they could be even more short staffed than normal.

Keep in mind that displaying the two versions of an app is only a temporary measure & something we deal with each time there is an app change.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[