You mean all of the DB queries and such? I had that pop up for about 30 seconds. Possibly the connection to the DB was broken for a moment?

---

You mean all of the DB queries and such? I had that pop up for about 30 seconds. Possibly the connection to the DB was broken for a moment?

Dunno, but glad somebody else witnessed it.....
I was pretty sure it was not on my end.

---

"Time is simply the mechanism that keeps everything from happening all at once."

That was a close one! Almost fell onto the second page!

Yeah......
But there's something funky goin' about.
There has been AP data available to split for a while now, but the AP splitters seem to have had trouble picking up on that. Usually, bandwidth maxxes out as soon as AP can be split.
And the last server status update shows MB ready to send dropping, yet some MB splitters are no longer active.

So......something's afoot, and we may have more to talk about soon other than the dang cache limits.

The file sizes look suspiciously like they're again trying to clean up the scraps...

                                                                   Joe

That was a close one! Almost fell onto the second page!

Yeah......
But there's something funky goin' about.
There has been AP data available to split for a while now, but the AP splitters seem to have had trouble picking up on that. Usually, bandwidth maxxes out as soon as AP can be split.
And the last server status update shows MB ready to send dropping, yet some MB splitters are no longer active.

So......something's afoot, and we may have more to talk about soon other than the dang cache limits.

The file sizes look suspiciously like they're again trying to clean up the scraps...

                                                                   Joe

Ahh......see what you mean, Joe.

---

"Time is simply the mechanism that keeps everything from happening all at once."

So, did we have an early outage or was it another glitch?

---

Grant
Darwin NT

So, did we have an early outage or was it another glitch?

I'd say it was an early and short outage, and not a glitch.

A long time ago Matt mentioned in one of his posts that Jeff was an early riser. My guess is the early start of the outage indicates he's tending things alone again.

                                                                   Joe

Looking at the server stats page a few minutes ago (8am UK time, 26 October) I noticed the file sizes. Now I understood that the "tapes" were a standard 50GB, but this lot range from 0GB to 50GB. Are they clearing the shelves of all the odd bits or what??

01ap10ep 0.00 GB
01dc10ab 8.78 GB
01ja11ac 8.78 GB
02se10ad 8.53 GB
03ap10ak 7.91 GB
04mr11ae 8.78 GB
07ja10ae 8.53 GB
07no10aa 8.78 GB
08ap11ai 4.02 GB
08se11ab 50.20 GB
09mr11ab 8.78 GB
09se11ad 50.20 GB
09se11ae 50.20 GB
10mr11ad 8.03 GB
10se10ae 8.78 GB
14mr11ad 8.78 GB
14se10aa 8.53 GB
14se11ab 50.20 GB
15se11ad 50.20 GB
15se11ae 50.20 GB
17se11ab 41.66 GB
17se11ac 50.20 GB
19jl10aa 8.66 GB
19jl10ab 2.26 GB
20ap11ae 4.39 GB
20se11aa 50.20 GB
21au10ad 7.28 GB
21dc10ab 0.00 GB
22jl10ab 6.27 GB
23se11aa 50.20 GB
23se11ab 50.20 GB
25ap10ad 8.78 GB
25se11ab 50.20 GB
28mr10af 8.78 GB
29ap11af 4.77 GB
29au10ah 0.00 GB
30mr11ae 8.78 GB

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Looking at the server stats page a few minutes ago (8am UK time, 26 October) I noticed the file sizes. Now I understood that the "tapes" were a standard 50GB, but this lot range from 0GB to 50GB. Are they clearing the shelves of all the odd bits or what??

I believe they could be clearing out ends of left over tapes. I'm wondering how it will take to burn through the tapes

---

Looking at the server stats page a few minutes ago (8am UK time, 26 October) I noticed the file sizes. Now I understood that the "tapes" were a standard 50GB, but this lot range from 0GB to 50GB. Are they clearing the shelves of all the odd bits or what??

I believe they could be clearing out ends of left over tapes. I'm wondering how it will take to burn through the tapes

Might just be some housekeeping clearing out the offline storage...dunno.
V7 is gonna be rolled out at some point, but I am not sure that is really reliant on the datasets available to process, but rather the way in which they will be processed.

I have seen no news indicating that current data collection from Arecibo is not proceeding as usual.

---

"Time is simply the mechanism that keeps everything from happening all at once."

If v7 is as big a step as some suggest it would certainly make sense to clear the decks of the odds an sods.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Perhaps data what wasn't able to be pulled off before is getting a run though.

---

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

Replica DB is falling badly behind all of a sudden. As of now it's 2,406 seconds behind, and it increases fast.

Nobody dares mention the yellow one please.....

It's only 14 seconds behind now. Main DB is 648/sec as of 20:50:06

---

Replica DB is falling badly behind all of a sudden. As of now it's 2,406 seconds behind, and it increases fast.

Nobody dares mention the yellow one please.....

It's only 14 seconds behind now. Main DB is 648/sec as of 20:50:06

Generation of daily stats dump files, anyone? Those timestamps are in local time, i.e. about 2 hours ago.

You can usually see those daily spikes in queries and replica backlog on Scarecrow's graphs, but he seems to be a bit busy right now.

I'm getting quite a few MD5 errors recently, my 3G connection might be part of the problem, but I can't change that... and everything else works, just some downloads from SETI don't. Anyway, is there any way to tell BOINC to retry to download the file on such error? I couldn't find any cc_config option for that...

---

I'm getting quite a few MD5 errors recently, my 3G connection might be part of the problem, but I can't change that... and everything else works, just some downloads from SETI don't. Anyway, is there any way to tell BOINC to retry to download the file on such error? I couldn't find any cc_config option for that...

No, But as long as you don't report the failed task, you can shut down Boinc, edit your client_state.xml and reset it back to downloading, first of all delete the failed download from your project folder,
then make the <file_info> section look like this (the status will need to be 0, and you'll need to delete the MD5_FAILED message):

<file_info>
    <name>17jl11ac.2358.153186.13.10.196</name>
    <nbytes>375345.000000</nbytes>
    <max_nbytes>0.000000</max_nbytes>
    <md5_cksum>3626d3dc15ec5ff72f49f892f8493bb3</md5_cksum>
    <status>0</status>
    <url>http://boinc2.ssl.berkeley.edu/sah/download_fanout/1e/17jl11ac.2358.153186.13.10.196</url>
</file_info>

The result section will need to be edited until it looks like this:

<result>
    <name>17jl11ac.2358.153186.13.10.196_2</name>
    <final_cpu_time>0.000000</final_cpu_time>
    <final_elapsed_time>0.000000</final_elapsed_time>
    <exit_status>0</exit_status>
    <state>2</state>
    <platform>windows_intelx86</platform>
    <version_num>610</version_num>
    <plan_class>cuda_fermi</plan_class>
    <wu_name>17jl11ac.2358.153186.13.10.196</wu_name>
    <report_deadline>1321982214.000000</report_deadline>
    <received_time>1319028235.992689</received_time>
    <file_ref>
        <file_name>17jl11ac.2358.153186.13.10.196_2_0</file_name>
        <open_name>result.sah</open_name>
    </file_ref>
</result>

Edit: Advanced Users Only.

Claggy

Have the Crickets run out of green pixels?

I was thinking the same thing! My ups and downs are still going through just fine, but the cricket is just, blank!

---

Have the Crickets run out of green pixels?

Seems to be a problem of the Cricket software or the connection to the webinterface and gladly not a problem of the routers. At all monitored routers Cricket comes to a stop at the same time.

__W__

---

_______________________________________________________________________________

I've done that few times like that, but in normally BOINC asks for new tasks after such failed download ASAP, so you have just five minutes (actually less, specially if there was a HTTP error) to catch that... so not really possible for people who do not watch BOINC Manager all the time.

Well, I'll have to live with that I guess...

---

Have the Crickets run out of green pixels?

The blue pixels are missing as well. ;-)