Here:

http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html

Several of the Berkeley traffic graphs - including errors have just maxed-out.

Could this be the start of another typical week-end?
I only looked because downloads are stalling here.

---

My guess is that a lot of people are trying to download extra work for the weekend, "just in case". I see the errors, but if you notice, traffic is also higher. So, with a bunch of people grabbing extra WU, it's giving a few errors.

---

My movie https://vimeo.com/manage/videos/502242

<blockquote>Here:

http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html

Several of the Berkeley traffic graphs - including errors have just maxed-out.

Could this be the start of another typical week-end?
I only looked because downloads are stalling here.
</blockquote>

If you check the error rate it is very low. With a rate of 0.06 errors per second, there is one error every 16.6 seconds.

---

Red Bull Air Racing

Gas price by zip at Seti

<blockquote><blockquote>Here:

http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html

Several of the Berkeley traffic graphs - including errors have just maxed-out.

Could this be the start of another typical week-end?
I only looked because downloads are stalling here.
</blockquote>

If you check the error rate it is very low. With a rate of 0.06 errors per second, there is one error every 16.6 seconds.</blockquote>

I think this discussion has already been had.
But looging at the graph here:
http://www.net.berkeley.edu:8885/~cricket/cricket/grapher.cgi?target=/router-interfaces/inr-668-interfaces/gigabitethernet0_1&ranges=d%3Aw&view=Errors

We have a graph where presumably the bottom is insignificant errors and the top is the maximum allowed/possible error rate. The spike (as it seems now) approaches the maximum allowed rate.
Regardless of the units, period etc., the graph is designed to convey a condition or state of affairs.
If 60 somethings is not significant, then the graph should have a y-origin of 60 somethings, not zero, and a maximum of who knows what.

---

As suggested in an earlier message about the weekend, I have increased my cache just in case...... I have 10wu in the pipe for now as I can do about 6 to 8/day.
SteveH (NZ)

---

<blockquote><blockquote><blockquote>Here:

http://fragment1.berkeley.edu/~cricket/inr-668-interfaces.html

Several of the Berkeley traffic graphs - including errors have just maxed-out.

Could this be the start of another typical week-end?
I only looked because downloads are stalling here.
</blockquote>

If you check the error rate it is very low. With a rate of 0.06 errors per second, there is one error every 16.6 seconds.</blockquote>

I think this discussion has already been had.
But looging at the graph here:
http://www.net.berkeley.edu:8885/~cricket/cricket/grapher.cgi?target=/router-interfaces/inr-668-interfaces/gigabitethernet0_1&ranges=d%3Aw&view=Errors

We have a graph where presumably the bottom is insignificant errors and the top is the maximum allowed/possible error rate. The spike (as it seems now) approaches the maximum allowed rate.
Regardless of the units, period etc., the graph is designed to convey a condition or state of affairs.
If 60 somethings is not significant, then the graph should have a y-origin of 60 somethings, not zero, and a maximum of who knows what.

</blockquote>
The graph has autoscaling. It will always show the maximum over the graph time frame towards the top. It doesn't mean the the top of the grpah is the maximum allowed error rate. It is the maximum that ocurred in the time of the graph. If you check now there was an error rate that reached 200 millierrors per second or about 1 error every 5 seconds. It is still very low.

---

Red Bull Air Racing

Gas price by zip at Seti

I would have thought that people increasing their cache for the weekend 'just in case' will result in a self proving prophecy. Everyone tries to download extra work, and the servers stall at the sudden increase in traffic. As this happened at the weekend when S@H bods are off.....

I run the same sized cache all the time. I don't make extra work for the servers 'just coz it's Friday'.

I think the suggestion to 'increase cache size for the weekend' is at best pointless, and at worst will result in the sort of problems people are trying to avoid..

If you are worried about running out of work in 2 days set your cache to 4 days, and leave it there.

I have a 10 day setting that lasts about 6-8 days (depending on the number of noisy WU's). It's topped up every 3rd day by Boinc (or sooner for the same reason). So I tend to have 4 days work or more at all times.

I currently have 7 days, as Boinc re-filled on friday 13th, just by chance. Had it not done so i would not have taken any action, as I would still have had plenty to last me the weekend, and then some.

IMHO.

---

Foamy is "Lord and Master".
(Oh, + some Classic WUs too.)

Anyone know whats up with the server status?

http://setiweb.ssl.berkeley.edu/sah_status.html

when u click on server status nothing is there......

---

BOINC SYNERGY is an International Team and We Welcome All BOINC Participants!
BOINC Synergy Click to Join BOINC Synergy

<blockquote>Anyone know whats up with the server status?

http://setiweb.ssl.berkeley.edu/sah_status.html

when u click on server status nothing is there......</blockquote>

i noticed this before,i think that is only a Script Error...

and for the Weekend, in Germany we have an Extra Day here, hope all is going good...

Greetings from Germany NRW
Ulli S@h Berkeley's Staff Friends Club m7 ©

I don't know what is wrong exactly. But it is already like this for several hours. One of my PC's downloaded some work, so it isn't that bad. :-)

<blockquote>I don't know what is wrong exactly. But it is already like this for several hours. One of my PC's downloaded some work, so it isn't that bad. :-)
</blockquote>

Plenty of work here -- the only 'weekend special' I see is that the XML feed didn't process for the stats sites today.

---

I couldn't see Server Status screen 10 hrs ago but its back up now, first splitter is down though.

Andy

It's only the usual "HTTP 500 Internal server error"-weekend :/
Keep calm, sometime it gets fixed...

---

Aloha, Uli