Well I hope they estimated the hour correctly, because I have two computers out of work already.

---

Red Bull Air Racing

Gas price by zip at Seti

Give or take an order of magnitude, everything will be just fine!

---

1 hour = optimism.

But, then again if they weren't optimists..the BOINC project would probably have never been released ;)

I only have one thats out right now but others are sure to follow if it stays down long.

Scott

---

" "

What time was the message posted on the main page? (there's a date but not time - be it UTC or PT).

Are we still in the "hour" or are we now in the 4th hour?

I got CP on all machines, so there's lots of work for them to do if it takes a few hours.

Just curious....

---

> 1 hour = optimism.
!!

23h00(today) - 22h00 = 1 Hour.

23h00(next day)- 22h00 = 1 Hour.

berkeley scientific based time calculations.

:(

remember:
1 Hour (berkeley based) = 1 night
6 Hours (berkeley based) = more than 24 Hours
1 Day (berkeley based) = probaly the week off


curiousity kills the cat

> remember:
> 1 Hour (berkeley based) = 1 night
> ...
>

You're so right... :/

---

Aloha, Uli

> What time was the message posted on the main page? (there's a date but not
> time - be it UTC or PT).
>
> Are we still in the "hour" or are we now in the 4th hour?
>
> I got CP on all machines, so there's lots of work for them to do if it takes a
> few hours.
>
> Just curious....
>
The last download I got was Jan3, 2005 at 21:07:04 UTC. I think the servers were shutdown about one hour afterwards so that puts it at about 22:07:00 UTC.
That last server update shows [As of 4 Jan 2005 3:10:05 UTC].

So it is already about 6 hours.

---

Red Bull Air Racing

Gas price by zip at Seti

So far, since my laptop has been trying to connect from when I got into work today, it's been 6hrs. Not that I'm arguing either as I also have cp running away, but 1hr Berkeley time sure ain't 1hr real time!

---

Paul
(S@H1 8888)
And proud of it!

A New York minute lasts at least an hour and a half... so if you want that for comparison, it'll take a while longer yet. ;)

---

> remember:
> 1 Hour (berkeley based) = 1 night
> 6 Hours (berkeley based) = more than 24 Hours
> 1 Day (berkeley based) = probaly the week off
>

Not completly true,

December 6, 2004
The project will be down for roughly the next 24 hours while make some changes to the database structure. [ Good news - changes are all done, and it only took 2 hours ].

It appears when they think something is going to go bad, it goes good, and vice versa seems to be true as well.

Also just noticed they removed the 1 hour time estimate from the front page.

Servers have been down for way longer then 1 hour

"data-driven web pages klaatu Running
scheduler kryten Not running
feeder kryten Not running
file_deleter koloth Not running
transitioner1 klaatu Not running
transitioner2 klaatu Not running
transitioner3 kryten Not running
transitioner4 kryten Not running
sah_validate klaatu Not running
sah_assimilator galileo Not running
sah_splitter galileo Running
sah_splitter2 milkyway Running
sah_splitter3 philmor Running"

I tried to upload a work unit about 3:14 pm this afternoon and it was down then. It's now 8:52 PM, and see below:

"SETI@home - 2005-01-03 14:49:12 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 14:49:15 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 14:49:15 - No schedulers responded
SETI@home - 2005-01-03 14:49:15 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2005-01-03 14:49:33 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 14:49:36 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 14:49:36 - No schedulers responded
SETI@home - 2005-01-03 14:49:36 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2005-01-03 14:50:05 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 14:50:08 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 14:50:08 - No schedulers responded
SETI@home - 2005-01-03 14:50:08 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2005-01-03 14:50:17 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 14:50:20 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 14:50:20 - No schedulers responded
SETI@home - 2005-01-03 14:50:20 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2005-01-03 14:50:34 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 14:50:37 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 14:50:37 - No schedulers responded
SETI@home - 2005-01-03 14:50:37 - Deferring communication with project for 2 minutes and 9 seconds
SETI@home - 2005-01-03 14:50:49 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 14:50:52 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 14:50:52 - No schedulers responded
SETI@home - 2005-01-03 14:50:52 - Deferring communication with project for 2 minutes and 7 seconds
SETI@home - 2005-01-03 14:51:04 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 14:51:07 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 14:51:07 - No schedulers responded
SETI@home - 2005-01-03 14:51:07 - Deferring communication with project for 18 minutes and 12 seconds
SETI@home - 2005-01-03 15:09:19 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 15:09:22 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 15:09:22 - No schedulers responded
SETI@home - 2005-01-03 15:09:22 - Deferring communication with project for 39 minutes and 50 seconds
SETI@home - 2005-01-03 15:22:51 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 15:22:54 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 15:22:54 - No schedulers responded
SETI@home - 2005-01-03 15:22:54 - Deferring communication with project for 59 minutes and 41 seconds
SETI@home - 2005-01-03 15:38:33 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 15:38:36 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 15:38:36 - No schedulers responded
SETI@home - 2005-01-03 15:38:36 - Deferring communication with project for 3 hours, 45 minutes, and 44 seconds
SETI@home - 2005-01-03 16:06:57 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 16:07:00 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 16:07:00 - No schedulers responded
SETI@home - 2005-01-03 16:07:00 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2005-01-03 16:08:03 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 16:08:06 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 16:08:06 - No schedulers responded
SETI@home - 2005-01-03 16:08:06 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2005-01-03 16:09:06 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 16:09:09 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 16:09:09 - No schedulers responded
SETI@home - 2005-01-03 16:09:09 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2005-01-03 16:10:09 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 16:10:12 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 16:10:12 - No schedulers responded
SETI@home - 2005-01-03 16:10:12 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2005-01-03 16:11:12 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 16:11:15 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 16:11:15 - No schedulers responded
SETI@home - 2005-01-03 16:11:15 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2005-01-03 16:12:15 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 16:12:18 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 16:12:18 - No schedulers responded
SETI@home - 2005-01-03 16:12:18 - Deferring communication with project for 2 minutes and 26 seconds
SETI@home - 2005-01-03 16:14:44 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 16:14:47 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 16:14:47 - No schedulers responded
SETI@home - 2005-01-03 16:14:47 - Deferring communication with project for 2 minutes and 37 seconds
SETI@home - 2005-01-03 16:17:24 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 16:17:27 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 16:17:27 - No schedulers responded
SETI@home - 2005-01-03 16:17:27 - Deferring communication with project for 8 minutes and 23 seconds
SETI@home - 2005-01-03 16:25:50 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 16:25:53 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 16:25:53 - No schedulers responded
SETI@home - 2005-01-03 16:25:53 - Deferring communication with project for 17 minutes and 12 seconds
SETI@home - 2005-01-03 16:43:05 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 16:43:08 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 16:43:08 - No schedulers responded
SETI@home - 2005-01-03 16:43:08 - Deferring communication with project for 1 hours, 14 minutes, and 34 seconds
SETI@home - 2005-01-03 17:43:08 - Deferring communication with project for 14 minutes and 34 seconds
SETI@home - 2005-01-03 17:45:01 - Computation for result 05dc03aa.19759.1744.1009650.212 finished
SETI@home - 2005-01-03 17:45:01 - Starting result 10dc03aa.8502.497.286082.116_2 using setiathome version 4.08
SETI@home - 2005-01-03 17:45:01 - Started upload of 05dc03aa.19759.1744.1009650.212_1_0
SETI@home - 2005-01-03 17:45:07 - Finished upload of 05dc03aa.19759.1744.1009650.212_1_0
SETI@home - 2005-01-03 17:45:07 - Throughput 5287 bytes/sec
SETI@home - 2005-01-03 17:49:44 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 17:49:47 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 17:49:47 - No schedulers responded
SETI@home - 2005-01-03 17:49:47 - Deferring communication with project for 2 hours, 35 minutes, and 33 seconds
SETI@home - 2005-01-03 18:49:47 - Deferring communication with project for 1 hours, 35 minutes, and 33 seconds
SETI@home - 2005-01-03 19:49:47 - Deferring communication with project for 35 minutes and 33 seconds
SETI@home - 2005-01-03 20:25:20 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 20:25:23 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 20:25:23 - No schedulers responded
SETI@home - 2005-01-03 20:25:23 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2005-01-03 20:26:27 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 20:26:30 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 20:26:30 - No schedulers responded
SETI@home - 2005-01-03 20:26:30 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2005-01-03 20:27:30 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 20:27:33 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 20:27:33 - No schedulers responded
SETI@home - 2005-01-03 20:27:33 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2005-01-03 20:28:33 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 20:28:36 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 20:28:36 - No schedulers responded
SETI@home - 2005-01-03 20:28:36 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2005-01-03 20:29:36 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 20:29:39 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 20:29:39 - No schedulers responded
SETI@home - 2005-01-03 20:29:39 - Deferring communication with project for 1 minutes and 0 seconds
SETI@home - 2005-01-03 20:30:39 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 20:33:22 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 20:33:22 - No schedulers responded
SETI@home - 2005-01-03 20:33:22 - Deferring communication with project for 1 minutes and 54 seconds
SETI@home - 2005-01-03 20:35:16 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 20:35:19 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 20:35:19 - No schedulers responded
SETI@home - 2005-01-03 20:35:19 - Deferring communication with project for 5 minutes and 20 seconds
SETI@home - 2005-01-03 20:40:39 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 20:40:42 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 20:40:42 - No schedulers responded
SETI@home - 2005-01-03 20:40:42 - Deferring communication with project for 8 minutes and 14 seconds
SETI@home - 2005-01-03 20:48:56 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 20:48:59 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 20:48:59 - No schedulers responded
SETI@home - 2005-01-03 20:48:59 - Deferring communication with project for 48 minutes and 39 seconds
SETI@home - 2005-01-03 20:50:55 - Sending request to scheduler: http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
SETI@home - 2005-01-03 20:50:58 - Scheduler RPC to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
SETI@home - 2005-01-03 20:50:58 - No schedulers responded
SETI@home - 2005-01-03 20:50:58 - Deferring communication with project for 1 hours, 39 minutes, and 29 seconds"

---

Actually I've noticed they've changed their announcment slightly - now it just says:

January 3, 2005
The project is currently down for database updates.

note - no mention of the famed berkeley hour anymore :)

---

<img border="0" src="http://boinc.mundayweb.com/one/stats.php?userID=268&amp;prj=1&amp;trans=off" /><img border="0" src="http://boinc.mundayweb.com/one/stats.php?userID=268&amp;prj=4&amp;trans=off" />

They have updated the page now.

January 3, 2005
The database update is taking longer than expected. We should be back up tomorrow morning.

Oh well. Is this going to be a Berkeley day?

> They have updated the page now.
>
> January 3, 2005
> The database update is taking longer than expected. We should be back up
> tomorrow morning.
>
> Oh well. Is this going to be a Berkeley day?
>

But if we're experiencing a Berkely hour here...then is a Berkely day the same as a day on Earth, or a day on Jupiter? Our clients would really be idle by then...

---

Still the question, whose tomorrow morning? Berkeley time? Or sometime around 10am UTC/GMT?

---

> Still the question, whose tomorrow morning? Berkeley time? Or sometime around
> 10am UTC/GMT?
>

I would say they meant berkeley time (PST)...

But then, i've seen one of the 'brief' outages take days before... The unforseen has a way of happening at berkeley.

BTW, the server status page says everything's up, and the notice is off the front page. However my BOINC client still can't get a responce from a scheduler and gets the connection deferred...

---

The scheduler is still down....

---

GHz
BOINC.Italy

It could be that they trying to clear the backlog of completed units first, thats about 4-5 days worth of work