> I have in fact set up the BOINC Project Status ... to monitor the project's networking ability and the server status page is included.
>
> It basically shows whether the project is communicating with the outside
> world and whether the server status shows anything.
>
> This applies to all BOINC projects and I will add more as they are
> created.

Thank you for taking the time and trouble to do that work! I have bookmarked the page. :)

@cjmweb_uk

a thankyou as well for that link.

---

Click below for our Team Website

> Agreed -- server status report indicates everything is running just fine -- it
> isn't. No big deal, I have queues, and besides which, I can readily redirect
> workstations to Seti Classic, which is running properly.

Actually, the server status was correct.

According to the home page, campus now requires software firewalls on all machines. Then again, it's all explained on the home page.

Except for the fact that "up" and "unreachable" aren't necessarily the same.

---

@cjmweb_uk

a thankyou as well for that link.

---

Fred
BOINC Alpha, BOINC Beta, LHC Alpha, Einstein Alpha

> Except for the fact that "up" and "unreachable" aren't necessarily the same.

Precisely

---

Thanks for the link :-))
Bookmarked

---

"Hard work never killed anybody"
But why take the risk !
Proud member of Boinc Synergy.
Join our team

But what is described on the home page isn't accurate -- as according to it the connectivity was restored by pulling the second firewall (for now), yet connectivity IS NOT restored -- clearly -- the only success I've seen reported is some downloads, but NO uploads.

Something else isn't working the way folks in Berkeley think it is working -- of course since it is now the weekend, this won't get resolved until sometime next week, by which time the upload backlog will be large enough to cause persisting problems for at least one additional day.

This one appears to be firmly in the avoidable and unresolved column for now.

---

> But what is described on the home page isn't accurate -- as according to it
> the connectivity was restored by pulling the second firewall (for now), yet
> connectivity IS NOT restored -- clearly -- the only success I've seen
> reported is some downloads, but NO uploads.

I've managed to both ul and dl, as well as attempt to update my BOINC manager stats, intermittently (as required) for the past 8 hours.

> But what is described on the home page isn't accurate -- as according to it
> the connectivity was restored by pulling the second firewall (for now), yet
> connectivity IS NOT restored -- clearly -- the only success I've seen reported
> is some downloads, but NO uploads.

That would still likely be the effects of congestion. Not only does people tend to press Update, they also tend to press Retry

> Something else isn't working the way folks in Berkeley think it is working --

Not nessesarily. I see this all the time when seti is comming back from an outage. BOS begin to switch from Unreachable to Online and back very often, while reports come in at the message boards that either downloading or uploading was successful, one of those being most frequent at the beginning - but as congestion clears up, BOS begins to say Online more often than Unreachable, Upload and download as well as reporting wu's are successful more and more frequently.

The typical effects actually IS that either upload or download begins to be successful some time before the other.

By now things should be, at least close to, normal.

---

> This one appears to be firmly in the avoidable and unresolved column for now.

This one should also appear in the "tempest in a teapot" column.

100% reliability is not a requirement for BOINC projects. A little bit of downtime does no harm at all.

Maybe an analogy would help.

Auto racing:

Think about the Indy 500, and the Baja 1000.

At Indianapolis, the slightest bump would destroy the suspension on these highly tuned cars.

The Baja race is very different: the whole point is that the course is bumpy, and the race cars and trucks are designed to take the bumps without breaking, and to go very fast with only intermittent contact with the race course.

My only grumble is that I think there should be some changes to the BOINC client so that it doesn't aggressively try to reconnect when the servers have been unreachable -- and maybe some way to signal that "slow" timing is good. Slowing down would actually avoid the crunch after some downtime.

---

Yes, the problems from last night and early this morning appear to have been cleared as of later this morning.

Of course with the outage just having been cleared, for a while the pending results will climb as others are working through their upload backlog as well.



> I've managed to both ul and dl, as well as attempt to update my BOINC manager
> stats, intermittently (as required) for the past 8 hours.

---

> This one should also appear in the "tempest in a teapot" column.

All outages get this sort of response for sure -- for me, planned and announced outages cause no bother at all -- any inconvenience is modest -- especially if they are announced with some real lead time.

Unplanned outages tend to irritate me a bit more -- they carry a bit more inconvenience.

Unplanned extended outages (more than a day) bother me (more than some who don't care I suppose).

And unplanned extended outages where the status reporting mismatches what is going on are troublesome to me.

Does any of this matter in the larger scheme of things? Of course not.

Your response to these situations may well vary.

---

Sorry for the bump!

But, why is this thread still being posted in and why is it still sticky? Hmmmm????

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

> Sorry for the bump!

No bump... as you noted, it's sticky. :-)

> But, why is this thread still being posted in and why is it still sticky?

As near as I can tell, people are still having (or thinking they're having?) issues potentially related to the outage... and additionally, people may come to the boards wondering why their computer couldn't connect to SETI@Home a day or two ago.

So it'll stay sticky until Monday unless Rom or Jens un-stiky it. :-)

---

Rob

> > ....
> No bump... as you noted, it's sticky. :-)
> > ....
> As near as I can tell, people are still having (or thinking they're having?)
> issues potentially related to the outage... and additionally, people may come
> to the boards wondering why their computer couldn't connect to SETI@Home a day
> or two ago.
>
> So it'll stay sticky until Monday unless Rom or Jens un-stiky it. :-)
>

Ok, thanks Rob. Was just wondering.

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

> As near as I can tell, people are still having (or thinking they're having?)
> issues potentially related to the outage... and additionally, people may come
> to the boards wondering why their computer couldn't connect to SETI@Home

More like they can't connect to Einstein@home.

> > ....
> More like they can't connect to Einstein@home.
>

Hmmmm.... Just checked and it's all green over there [not that that really means a lot]. No messages about any problems. Must be mass quantities of users trying to up/download and such. I really don't like seeing red in my BOINC Manager messages tab. >:-(

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

> More like they can't connect to Einstein@home.
>

Siran and Misfit... i guess they made some changes to the scheduler that requires you to give it a little nudge. Oddly enough, if you update your general preferences for Einstein, then update the project, it all starts working again. :)

Thanks to Rockenstein for the tip!

Dig

---

yup, this time it was einstein that was hit by an outage that wasn't really an outage :D Things can happen, and as always it'll get solved one way or another ;)

---

Einstein fix confirmed. Just update your general prefs and the next time it'll work. Click General pref, then Update. Don't bother changing anything.

tony

---