Thanks Matt, I'll stop fiddling further then.

Isn't it an idea to put that up as a news item, though?

Edit: BOINC domain popped up, just in time for me to fall into a big fight in the making over there. What is it with you people?

---

Thank you Matt for the update.
I could connect to the server finally and it's been OK for last 2 hours.
I keep my fingers crossed ;)

---

So looks like resolved? Nope, I guess I just got lucky once and was able to report the 300+ tasks and fill the cache once. For now, I guess that will have to do ...
BTW, the replica DB is offline again ...

---

183 WUs were acknowledged at 14:27 UTC and I have work coming in again. Life is good.

I had to go and call a no-hitter didn't I. Will I ever learn? Now 32 are waiting to be acknowledged and no new work.

This is life, la laa laa li la,,,

lala la laa li la, la laa laa li la,

la la la, la life.

[opus5]

262+ not reported,

problems stil.
- master file download successful
- ,,, error.


la 3. lokakuuta 2015 00.15.40 | SETI@home | Scheduler request failed: Couldn't connect to server
la 3. lokakuuta 2015 00.15.41 | SETI@home | update requested by user
la 3. lokakuuta 2015 00.15.42 | | Internet access OK - project servers may be temporarily down.
la 3. lokakuuta 2015 00.15.45 | SETI@home | Fetching scheduler list
la 3. lokakuuta 2015 00.15.47 | SETI@home | Master file download succeeded
la 3. lokakuuta 2015 00.15.52 | SETI@home | Sending scheduler request: Requested by user.
la 3. lokakuuta 2015 00.15.52 | SETI@home | Reporting 262 completed tasks
la 3. lokakuuta 2015 00.15.52 | SETI@home | Requesting new tasks for CPU and NVIDIA
la 3. lokakuuta 2015 00.15.55 | | Project communication failed: attempting access to reference site
la 3. lokakuuta 2015 00.15.55 | SETI@home | Scheduler request failed: Couldn't connect to server
la 3. lokakuuta 2015 00.15.56 | | Internet access OK - project servers may be temporarily down.
la 3. lokakuuta 2015 00.15.56 | SETI@home | update requested by user

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones

OK, it lasted only for another half an hour. Now I can't connect for last 3 hours....mmmm

---

I know I made a long post yesterday explaining that engineering a network isn't trivial and straight-forward, and I still think that it is a routing table problem. I remember in the Cisco labs, the whole class got together and we each divided and conquered and configured a router and had it connected to a second NIC in each of our workstations (there were 24 of us in the class), and we were using a variety of routing table protocols (RIP, RIPv2, IGRP, EIGRP, OSPF, and BGP) to see how each of those propagates and to see the pros and cons of them all.

I don't remember the specifics of which ones did what, but I do remember BGP (which is what the Internet at large uses) taking the longest to propagate and to have the complete map of the network, and it is also one that worked as expected for a few minutes, until most of the workstations were unreachable, and it was because one person's finger slipped when typing in a string of characters or numbers and ended up doing a 3 instead of a 2 or something akin to that. Basically, everything was fine until their misconfigured router tried syncing up with everything else.

It happens, and it took the whole class a while to figure it out. We even went so far as to go into the admin console and do 'clear nvram; restart' and started over with a blank router.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

So much for the sound of knuckles rapping loudly on wood........[edit](and now it is Friday).

---

"Sour Grapes make a bitter Whine." <(0)>

2 days work now all reported ok and new work downloaded. Thank you to whoever fixed it.

It's still broken.

Still taking multiple attempts to report & get new work.
Still getting sticky downloads.


EDIT- it doesn't appear to be taking as many attempts as it was before finally getting through.

---

Grant
Darwin NT

It appears the problem came back for me at about 18:00 UTC. But at least I have full cache. So good for 12 hours on my big box, 24 on others.

Herb

.aa

Works pretty good here now. No need for manual updates. My computers are well fed with work, and new work keeps getting in when needed.

But they continue to not split APs.

---

Can't get new credit here at all. It seems to have uploaded my work, just not getting new ones.

Campus is aware of the issues. It's out of our control.

Is it a fair question to ask if this situation affects any other sectors of Campus IT or just SETI?

---

"Sour Grapes make a bitter Whine." <(0)>

... and it's not working again...

Campus is aware of the issues. It's out of our control.

Is it a fair question to ask if this situation affects any other sectors of Campus IT or just SETI?

I am willing to bet it isn't affecting chancellor Dirks and his staff. :)

Ah, we're back.
For a while there I could get the home page, but nothing else. Then I couldn't even get the home page.
Lets see how long this lasts.

---

Grant
Darwin NT

Ah, we're back.
For a while there I could get the home page, but nothing else. Then I couldn't even get the home page.
Lets see how long this lasts.

Not for everyone. Still seeing "Internet access OK - project servers may be temporarily down." with every connection. 102 times in a row now. The last good connection was at 18:00:17 UTC.

Along with posting here, might I suggest that people send a "problem with service" email to:

itcsshelp@berkeley.edu

A few dozen (or hundred or thousand) emails might help Berkeley IST grasp the scope of the problem.

(Be polite!)

---

Member of the 20 Year Club

Along with posting here, might I suggest that people send a "problem with service" email to:

itcsshelp@berkeley.edu

A few dozen (or hundred or thousand) emails might help Berkeley IST grasp the scope of the problem.

(Be polite!)

And I would suggest NOT doing that.

Matt said they are aware of the problem and are working on it.
Flooding the Help Desk with Trouble reports about a problem they are already working on may serve only to piss-off the folks on the help-desk, and possibly IT management.

---

Donald
Infernal Optimist / Submariner, retired