• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Update: Seems to be back up! SETI: Berkeley down notice....

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
Back up, but experience tells me it will be a couple of days before everythings back to normal. They will be swamped with requests.

Damn, it always happens at a bad time for me. I did some upgrades/tweeks to my herd last night to improve output and I won't be able to see the fruits of my labor for a few days now. 🙁
 
Unfortunately, I have less than 24 hours of workunits cache for my home fleet.🙁 If things doesnt cleared by tonight, my home fleet will stop:disgust:
 
Looks like 11 results have just managed to escape from my Q over the past 1/2hr😉

Isos
Why not use 1 of the team Q's?
 
Originally posted by: Assimilator1
Looks like 11 results have just managed to escape from my Q over the past 1/2hr😉

Isos
Why not use 1 of the team Q's?
Click to expand...

anyone wanna post up the list of SETI Q addresses?
 
Craig, either see the stickied thread up the top, or check here

Mine has plenty of WUs queued 🙂 (teamanandtech.d2g.com:5001)


Garry
 
Originally posted by: Assimilator1
Looks like 11 results have just managed to escape from my Q over the past 1/2hr😉

Isos
Why not use 1 of the team Q's?
Click to expand...

I might have to do just that. I've trying not to burden anyone's Q so I usually submit and download workunits directly. If things doesn't get better, somebody's Q might get some pounding from my home fleet.😎 For that, I would like to say "SORRY" and "Mahalo Nui Loa" in advance🙂

Not the difficult part is deciding who's public Q should suffer😉
 
I don't think anyone will mind. However the server is up, maybe you could start up a queue of your own, it tends to do better at pulling WUs than driver does. I think it checks more often.
 
Originally posted by: TofBnT
I don't think anyone will mind. However the server is up, maybe you could start up a queue of your own, it tends to do better at pulling WUs than driver does. I think it checks more often.
Click to expand...

I think you can set a max of 10 mins, so it does sporadically at lesser intervals than that usually


12:08pm: Waiting 10m00s before trying again
12:08pm: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
12:04pm: Waiting 3m31s before trying again
12:01pm: Waiting 5m51s before trying again
12:01pm: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
11:58am: Waiting 2m55s before trying again
11:58am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
11:56am: Waiting 1m27s before trying again
11:56am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
11:56am: Sending result 29au03aa.16861.2145.348594.152
11:55am: Waiting 43s before trying again
11:55am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
11:54am: Waiting 21s before trying again
11:54am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
11:54am: Sending result 29au03aa.16861.2145.348594.152
11:54am: Waiting 10s before trying again
11:54am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
11:53am: Sending result 12au03aa.21858.753.579808.41
11:43am: Waiting 10m00s before trying again
11:43am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
11:33am: Waiting 8m08s before trying again
11:31am: Waiting 10m00s before trying again
11:31am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
11:31am: Sending result 12au03aa.21858.753.579808.41
11:31am: Waiting 12s before trying again
11:26am: Waiting 4m26s before trying again
11:21am: Waiting 10m00s before trying again
11:21am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
11:15am: Waiting 5m51s before trying again
11:15am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
11:13am: Sending result 12au03aa.21858.753.579808.41
11:12am: Waiting 48s before trying again
11:10am: Waiting 2m55s before trying again
11:10am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
11:07am: Waiting 1m27s before trying again
11:07am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
11:05am: Sending result 12au03aa.21858.753.579808.41
11:05am: Waiting 43s before trying again
11:05am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
11:03am: Waiting 21s before trying again
11:03am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Bad gateway response
11:03am: Sending result 12au03aa.21858.753.579808.41
11:03am: Waiting 10s before trying again
11:03am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Bad gateway response
11:01am: Sending result 12au03aa.21858.753.579808.41
10:55am: Waiting 5m50s before trying again
10:50am: Waiting 10m00s before trying again
10:50am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Bad gateway response
10:50am: Sending result 12au03aa.21858.753.579808.41
10:45am: Waiting 5m51s before trying again
10:45am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
10:40am: Waiting 2m55s before trying again
10:40am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
10:38am: Sending result 12au03aa.21858.753.579808.41
10:37am: Waiting 1m27s before trying again
10:37am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
10:34am: Waiting 43s before trying again
10:34am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
10:32am: Sending result 12au03aa.21858.753.579808.41
10:31am: Waiting 21s before trying again
10:31am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Bad gateway response
10:31am: Waiting 10s before trying again
10:31am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
10:29am: Sending result 12au03aa.21858.753.579808.41
10:27am: Waiting 10m00s before trying again
10:27am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
10:26am: Sending result 12au03aa.21858.753.579808.41
10:26am: Waiting 29s before trying again
10:16am: Waiting 10m00s before trying again
10:16am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
10:06am: Waiting 10m00s before trying again
10:06am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
10:05am: Sending result 12au03aa.21858.753.579808.41
9:56am: Waiting 8m57s before trying again
9:55am: Waiting 9m57s before trying again
9:55am: Waiting 10m00s before trying again
9:55am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
9:45am: Waiting 10m00s before trying again
9:45am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
9:45am: Sending result 12au03aa.21858.753.579808.41
9:41am: Waiting 3m28s before trying again
9:38am: Waiting 6m16s before trying again
9:35am: Waiting 10m00s before trying again
9:35am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
9:31am: Waiting 3m12s before trying again
9:24am: Waiting 10m00s before trying again
9:24am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
9:24am: Sending result 12au03aa.21858.753.579808.41
9:23am: Waiting 57s before trying again
9:14am: Waiting 9m39s before trying again
9:14am: Waiting 10m00s before trying again
9:14am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
9:12am: Waiting 1m05s before trying again
9:11am: Waiting 2m36s before trying again
9:11am: Waiting 2m43s before trying again
9:11am: Waiting 2m44s before trying again
9:10am: Waiting 3m08s before trying again
9:10am: Waiting 3m31s before trying again
9:09am: Waiting 4m11s before trying again
9:08am: Waiting 5m26s before trying again
9:06am: Waiting 7m29s before trying again
9:04am: Waiting 10m00s before trying again
9:04am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
9:03am: Sending result 12au03aa.21858.753.579808.41
9:01am: Waiting 1m56s before trying again
9:01am: Waiting 2m04s before trying again
9:00am: Waiting 2m58s before trying again
8:59am: Waiting 4m00s before trying again
8:54am: Waiting 9m03s before trying again
8:53am: Waiting 10m00s before trying again
8:53am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
8:51am: Waiting 1m29s before trying again
8:49am: Waiting 3m25s before trying again
8:48am: Waiting 4m19s before trying again
8:46am: Waiting 7m13s before trying again
8:44am: Waiting 8m51s before trying again
8:43am: Waiting 10m00s before trying again
8:43am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
8:42am: Sending result 12au03aa.21858.753.579808.41
8:41am: Waiting 1m30s before trying again
8:33am: Waiting 9m26s before trying again
8:32am: Waiting 10m00s before trying again
8:32am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
8:32am: Waiting 2s before trying again
8:29am: Waiting 2m48s before trying again
8:29am: Waiting 2m51s before trying again
8:27am: Waiting 5m23s before trying again
8:26am: Waiting 5m51s before trying again
8:26am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
8:26am: Sending result 12au03aa.21858.753.579808.41
8:26am: Waiting 10s before trying again
8:23am: Waiting 2m44s before trying again
8:23am: Waiting 2m55s before trying again
8:23am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
8:21am: Waiting 1m27s before trying again
8:21am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
8:21am: Sending result 12au03aa.21858.753.579808.41
8:20am: Waiting 43s before trying again
8:20am: Download WU: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
8:19am: Waiting 21s before trying again
8:19am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
8:19am: Sending result 12au03aa.21858.753.579808.41
8:19am: Waiting 10s before trying again
8:19am: Sending Result: Failed to send to server shserver2.ssl.berkeley.edu - Gateway timed out
8:18am: Sending result 12au03aa.21858.753.579808.41
 
ISOS, Check with MucMan. I use his Q, and would be willing to donate 50WUs from my wait Q, that would still give me 5 days worth of WUs. 🙂
 
Last updated: 21:10:00 (UTC) on 2003-12-03


This web page gets updated automatically every five minutes.

--------------------------------------------------------------------------------
Data Server Status
The data server is up and running, but dropping connections
Right now the data server machine is up, but not all clients are able to connect. This is due to our server being swamped with requests, and usually happens right after a server outage, or if there are greater network/database problems we are currently trying to fix. Please try connecting later.

For more information about previous outages, please check our Technical News page.






--------------------------------------------------------------------------------
Data Acquisition Status
Enabled: The receiver at Arecibo Observatory is on and we are acquiring data for both SERENDIP and SETI@home projects.





--------------------------------------------------------------------------------
Current Splitter Tapes
We are currently splitting data taken from the days below into work units:
03 August 2003 (aa)
10 August 2003 (aa)
10 August 2003 (ab)
11 August 2003 (aa)
21 August 2003 (aa)
25 August 2003 (ab)
29 August 2003 (aa)
29 August 2003 (ab)
04 September 2003 (aa)


The parathentical letters reflect order of data collection. Since we frequently fill more than one tape per day, we tag tapes with a set of two characters reflecting its sequence. We start with "aa," then "ab," and so on.
Click to expand...

This is from Seti status page.. seems they are up again...
 
yep all wu have beamed up and que is full

but i think i'll increase it just a tad lol

woot i found a Diamond😀:beer:
 
Originally posted by: lobadobadingdong
Originally posted by: Wolfsraider
yep all wu have beamed up and que is full

but i think i'll increase it just a tad lol

woot i found a Diamond😀:beer:
Click to expand...
congrats on diamond status, another month or so and I'll join you.
Click to expand...

thanks look forward to seeing you there:beer:
 
Originally posted by: TofBnT
no sh!!🙂
Click to expand...

Uh....isn't that what he posted above? 😛

Originally posted by: jliechty
Yay, how good it feels to not be constipated any more... 😀
Click to expand...

No more sh#@##!!!!! :Q

Buwhahahahahahahaha! 😀

Oh, TeAm lead around 71k 🙂

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top