I remember that a power outage was scheduled for last week to diagnose the wiring problems in the SSL building. Did that ever happen?

---

You will be assimilated...bunghole!

I was wondering the same thing and what the findings were.

Jim

---

> I remember that a power outage was scheduled for last week to diagnose the
> wiring problems in the SSL building. Did that ever happen?

I'm wondering, too. I haven't been able to upload any of my completed packets for a week or more. Just shifted over to BIONC from classic a few days before that, so I'm still trying to learn how it works.

---

> I'm wondering, too. I haven't been able to upload any of my completed packets
> for a week or more. Just shifted over to BIONC from classic a few days before
> that, so I'm still trying to learn how it works.

May want to dig into that, because I think everything is working for most everyone else....

---

> > I'm wondering, too. I haven't been able to upload any of my completed
> > packets for a week or more. Just shifted over to BIONC from classic a
> > few days before that, so I'm still trying to learn how it works.
>
> May want to dig into that, because I think everything is working for most
> everyone else....

Drat. I'm running 4.19 on Win 98SE, PIII at about 1.3G with 256M RAM, dialup connection.

--- - 2005-03-14 17:49:10 - Running CPU benchmarks
--- - 2005-03-14 17:49:10 - Suspending computation and network activity - running CPU benchmarks
--- - 2005-03-14 17:50:11 - Benchmark results:
--- - 2005-03-14 17:50:11 - Number of CPUs: 1
--- - 2005-03-14 17:50:11 - 1005 double precision MIPS (Whetstone) per CPU
--- - 2005-03-14 17:50:11 - 2527 integer MIPS (Dhrystone) per CPU
--- - 2005-03-14 17:50:11 - Finished CPU benchmarks
--- - 2005-03-14 17:50:12 - Resuming computation and network activity
--- - 2005-03-14 17:53:51 - Insufficient work; requesting more
--- - 2005-03-14 17:54:08 - Can't resolve hostname setiathome.berkeley.edu (host name not found)
SETI@home - 2005-03-14 17:54:08 - Couldn't read master page for SETI@home: error -113
SETI@home - 2005-03-14 17:54:08 - Master file fetch failed
SETI@home - 2005-03-14 17:54:08 - Deferring communication with project for 2 days, 5 hours, 26 minutes, and 18 seconds


Any ideas?

And I just noticed that all my packets are past deadline (yesterday). :(

---

> > > I'm wondering, too. I haven't been able to upload any of my
> completed
> > > packets for a week or more. Just shifted over to BIONC from classic
> a
> > > few days before that, so I'm still trying to learn how it works.
> >
> > May want to dig into that, because I think everything is working for
> most
> > everyone else....
>
> Drat. I'm running 4.19 on Win 98SE, PIII at about 1.3G with 256M RAM, dialup
> connection.
>
> --- - 2005-03-14 17:49:10 - Running CPU benchmarks
> --- - 2005-03-14 17:49:10 - Suspending computation and network activity -
> running CPU benchmarks
> --- - 2005-03-14 17:50:11 - Benchmark results:
> --- - 2005-03-14 17:50:11 - Number of CPUs: 1
> --- - 2005-03-14 17:50:11 - 1005 double precision MIPS (Whetstone) per CPU
> --- - 2005-03-14 17:50:11 - 2527 integer MIPS (Dhrystone) per CPU
> --- - 2005-03-14 17:50:11 - Finished CPU benchmarks
> --- - 2005-03-14 17:50:12 - Resuming computation and network activity
> --- - 2005-03-14 17:53:51 - Insufficient work; requesting more
> --- - 2005-03-14 17:54:08 - Can't resolve hostname setiathome.berkeley.edu
> (host name not found)
> SETI@home - 2005-03-14 17:54:08 - Couldn't read master page for SETI@home:
> error -113
> SETI@home - 2005-03-14 17:54:08 - Master file fetch failed
> SETI@home - 2005-03-14 17:54:08 - Deferring communication with project for 2
> days, 5 hours, 26 minutes, and 18 seconds
>
>
> Any ideas?
>
> And I just noticed that all my packets are past deadline (yesterday). :(
>

Are you sure BOINC is getting through your firewall. Double check you settings.

---

The outage to diagnose the problem is a week from tomorrow (early morning on Tuesday, March 22nd).

- Matt

---

-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

> The outage to diagnose the problem is a week from tomorrow (early morning on
> Tuesday, March 22nd).
>
> - Matt
>
=========================



Matt ___ thanks Very Much For: ___ That info.




My Very Best wishes to everyone ......... and keep on crunching :)

friendly and respectful
byron ... [/url] _ Earth Flag

<B>S@h _ Berkeley's Staff Friends Club member m2 ©[/b]

> --- - 2005-03-14 17:53:51 - Insufficient work; requesting more
> --- - 2005-03-14 17:54:08 - Can't resolve hostname setiathome.berkeley.edu
> (host name not found)

"Can't resolve hostname" suggests a problem with network connectivity. Is this machine on dial-up?

---

> The outage to diagnose the problem is a week from tomorrow (early morning on
> Tuesday, March 22nd).
>
> - Matt
>

Cool, thx for the update. You said awhile back that the problem affected the entire building, right? How big is the SSL building?

---

You will be assimilated...bunghole!

> --- - 2005-03-14 17:54:08 - Can't resolve hostname setiathome.berkeley.edu host name not found)
> SETI@home - 2005-03-14 17:54:08 - Couldn't read master page for SETI@home: error -113

As others have said- error 113 indicates a connection problem.
Modem not plugged in, not connecting, DNS server not serving, or firewall is blocking the connection.

---

Grant
Darwin NT

> May want to dig into that, because I think everything is working for most
> everyone else....
>

Yes, it works fine here too. Can be some connection problems sometimes but both upload and download works fime for me!

---

Happy crunching

[snip]
> > I'm running 4.19 on Win 98SE, PIII at about 1.3G with 256M RAM, dialup
> > connection.
[snip]
> > --- - 2005-03-14 17:54:08 - Can't resolve hostname setiathome.berkeley.edu
> > (host name not found)
> > SETI@home - 2005-03-14 17:54:08 - Couldn't read master page for SETI@home:
> > error -113
> > SETI@home - 2005-03-14 17:54:08 - Master file fetch failed
> > SETI@home - 2005-03-14 17:54:08 - Deferring communication with project for 2
> > days, 5 hours, 26 minutes, and 18 seconds
[snip]
> Are you sure BOINC is getting through your firewall. Double check you
> settings.

I just checked ZoneAlarm, and all permissions are set. I added passlock and tried again:
--- - 2005-03-17 17:24:09 - Insufficient work; requesting more
--- - 2005-03-17 17:24:26 - Can't resolve hostname setiathome.berkeley.edu (host name not found)
SETI@home - 2005-03-17 17:24:26 - Couldn't read master page for SETI@home: error -113
SETI@home - 2005-03-17 17:24:26 - Master file fetch failed
SETI@home - 2005-03-17 17:24:26 - Deferring communication with project for 1 days, 17 hours, 45 minutes, and 41 seconds

Tracert results:
Microsoft(R) Windows 98
(C)Copyright Microsoft Corp 1981-1999.

C:WINDOWS>tracert setiathome.berkeley.edu

Tracing route to setiathome.SSL.berkeley.edu [128.32.18.152]
over a maximum of 30 hops:

1 307 ms 312 ms 313 ms ca3.pcisys.net [216.229.32.149]
2 313 ms 313 ms 312 ms moe.pcisys.net [216.229.32.145]
3 308 ms 299 ms 312 ms cartman-S3-0.pcisys.net [216.229.32.161]
4 310 ms 312 ms 312 ms border10.s6-4.pcisys-1.den.pnap.net [216.52.42.13]
5 312 ms 313 ms 309 ms core3.ge2-0-bbnet1.den.pnap.net [216.52.40.3]
6 314 ms 313 ms 313 ms p1-0-2-0.a00.dnvrco02.us.ra.verio.net [198.173.159.253]
7 322 ms 339 ms 326 ms p4-1-0-0.r00.mlpsca01.us.bb.verio.net [129.250.16.53]
8 331 ms 339 ms 338 ms p16-0-1-2.r20.mlpsca01.us.bb.verio.net [129.250.2.225]
9 340 ms * 341 ms p64-0-0-0.r21.snjsca04.us.bb.verio.net [129.250.5.3]
10 321 ms 338 ms 338 ms p16-3-0-0.r01.snjsca04.us.bb.verio.net [129.250.2.183]
11 335 ms 325 ms 339 ms sjo-ix.he.net [206.223.116.37]
12 339 ms 339 ms 338 ms pos2-3.gsr12416.pao.he.net [66.220.13.42]
13 348 ms 336 ms 337 ms paix-px1--hurricane-ge.cenic.net [198.32.251.69]

14 334 ms 351 ms 339 ms dc-oak-dc2--oakk-dc1-p2p-1.cenic.net [137.164.22.193]
15 349 ms 339 ms 352 ms ucb--oak-dc2-ge.cenic.net [137.164.23.30]
16 335 ms 352 ms 339 ms vlan190.inr-202-doecev.Berkeley.EDU [128.32.0.39]
17 350 ms 904 ms 338 ms g1-2.inr-203-eva.Berkeley.EDU [128.32.255.10]
18 347 ms 339 ms 348 ms fast1-1-0.inr-60-ssl.Berkeley.EDU [169.229.0.202]
19 335 ms 350 ms 337 ms setiathome.SSL.berkeley.edu [128.32.18.152]
20 342 ms 351 ms 351 ms setiathome.SSL.berkeley.edu [128.32.18.152]

Trace complete.

After I first asked here, I un- and re-installed BOINC 4.19. I forced upload of all the completed work units. It then DLed one work unit (instead of the normal 4-6), ran it, uploaded it, then went back to the same "can't resolve" problem as before. >:(

Actually, it went back to that problem after DLing that one work unit. :p

---

> > > --- - 2005-03-14 17:54:08 - Can't resolve hostname setiathome.berkeley.edu
> > > (host name not found)

This message says that BOINC asked Windows to look up "setiathome.berkeley.edu" and it didn't get an answer.

The rest of the errors follow from the fact that it couldn't find setiathome.berkeley.edu.

Is this dialup? Was the machine dialed in at the time??

Solve the DNS problem and you've got it.

---

Looks like preparations are underway for the sparkies to do their thing.

---

Grant
Darwin NT

>
> Looks like preparations are underway for the sparkies to do their thing.

Looks like they've done it.
But months to order & fit new breakers???

---

Grant
Darwin NT

> But months to order & fit new breakers???

Look.. these aren't the kind of breakers you buy at the corner store. One of them is the main breaker for the building. Something like $20,000. And remember this is a university environment. Issues about who's coughing up the dough have yet to be discussed, which will lead to all kinds of bureaucratic finagling.

Anyway, this is, and has always been, completely out of our hands. They said the power should be stable at this point, and so we are happy.

- Matt

---

-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

> > But months to order & fit new breakers???
>
> Look.. these aren't the kind of breakers you buy at the corner store. One of
> them is the main breaker for the building. Something like $20,000. And
> remember this is a university environment. Issues about who's coughing up the
> dough have yet to be discussed, which will lead to all kinds of bureaucratic
> finagling.
>
> Anyway, this is, and has always been, completely out of our hands. They said
> the power should be stable at this point, and so we are happy.
>
> - Matt
>

$20 grand? Yikes! Although I suppose for an entire building, you'd need something pretty robust. What was the problem that they were able to fix immediately?

---

You will be assimilated...bunghole!

> And remember this is a university environment. Issues about who's coughing up the dough have yet to be discussed, which will lead to all kinds of bureaucratic finagling.

That makes more sense.

While not a commonly available item a breaker is a breaker.
High load 3 phase devices while excruciatingly expensive are generally available with in a week or 2 from the time of ordering. Unless of course they're very old & different from the current standard in which case the entire switch board requires probably replacing & rewiring just to replace the breakers with newer ones.
That's always fun.


> They said the power should be stable at this point, and so we are happy.

That's the main thing.
Very good to hear.

---

Grant
Darwin NT

> > But months to order & fit new breakers???
>
> Look.. these aren't the kind of breakers you buy at the corner store. One of
> them is the main breaker for the building. Something like $20,000. And
> remember this is a university environment. Issues about who's coughing up the
> dough have yet to be discussed, which will lead to all kinds of bureaucratic
> finagling.

When I was on the ship we had to stock fuses for our UPS, $25 each ... held on with 1/2 inch bolts ... I think they were 250A, one for each of the three phases ...

---