• 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.

Anyone else getting errors sending WUs to Berkeley?

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
is it having problems downloading or just uploading, I can't flush my Q, Sorry to the users, if it's an upload only problem then pointing at a Q should work. If not you can send a user_info.sah to any of the Q owners and have them create a queue for for using that and you should be able to connect and continue getting Wu's. I have 954 Wu's cached in my Q and am using about 80-90 a day.

Were is that Backup Q list anyway?









SHUX
 
Yield - the "data acquisition" stuff being down has nothing to do with whatever's going on, but has everything to do with what the equipment over at Arecebo in Puerto Rico is doing. This has no immediate impact on the ability for Berkeley to be able to either split their current data tapes to create new WUs and/or dish out/receive WUs to/from clients. If anything, it'll mean that down the road, we'll have ALOT more "repeat" WUs than normal, but that's about it.

What is happening could be a network problem on their campus. It has happened many times before. I routinely send results from my queue to Berkeley from 3am - 4am EST. All of my results were uploaded okay at that time and my queue was topped off, so whatever probably occurred, happened after that time - usually 6am EST or 3am PST (a time when they'll often "change stuff" on campus). Alternately, perhaps a swap file filled up or something happened to their RAID array or other disks... These have been the most common excuses...

I am very glad that my queue has 218 WUs in it... I try to keep 10 - 14 days worth as I know that the longest outage they have had (eg., after a fiber cable cut) was ~5 - 7 days, with it taking a day or so more for me to connect to them due to the massive amount of traffic from others trying to do the same.

(After 2+ years in this project, I KNOW better... 😛)
 
You bring up some good points. I double-checked my SetiQ settings and found that I had only 1.2 days as the minimum # for WU caching, and 3 days as the max. I bumped that up to 5 and 7, respectively.

Now I have about 70+ completed WU's waiting to go home... 🙂
 
Whew! Glad to hear that it's Berkeley that's down, I thought it was from me mucking around with Seti that loused things up 🙂
Thanks for the updates.
 
The official word on the front page:

The data server is currently overloaded. Many users are unable to connect to send/receive data. We are working on it - sorry for the inconveneince.

As a student at the university, I can verify that the network here is fairly inadequate, although the public network may have little to do with SETI@Home's network connection.
 
This is what they have up now:

NOTE: Due to a sudden increase in outgoing bandwidth from the entire UC Berkeley campus, the traffic from our network has been capped at a level greatly below our normal operating levels. Because of this, we are dropping many connections to our data server until we can catch up. To help alleviate this problem, we shut off many web services to reduce our bandwidth (like user account/profile lookups, web searches, etc.). Please bear with us until campus bandwidth levels come back down to earth.

So I guess this answers whether the public network has an effect on Seti 🙁
 
Be thankful for wu caching once again!

Make sure you have a good buffer Indy! Last year someone cut their cable and we were without wu's for about 7 days! ....that was a tough time, some of my machines just sat there doing nothing for a few days...man, that kills me, LOL.
 


<< herm, looks like morpheous is at it again 😉 >>


No kidding. Right now is about the fastest the internet's been here in the past 24 hours. Things come to a screeching halt in the evenings until well past midnight. It's impossible to play CS except really late at night or during the day.
 
I hope this problem can be resolve soon. Do you think Berkeley will blame TeAm for the sudden increase in network connections?😱
 


<<

<< herm, looks like morpheous is at it again 😉 >>


No kidding. Right now is about the fastest the internet's been here in the past 24 hours. Things come to a screeching halt in the evenings until well past midnight. It's impossible to play CS except really late at night or during the day.
>>

Ouch! :disgust:
 


<< LOL... upon further thought, maybe I should logoff AT to free up some bandwidth here.

Nah! 😉
>>

LOL! 😀
 
🙁 I'm on the last WU for my laptop...just started crunching it. 6.5 hrs until it's idle (and it's one of my fastest crunchers 🙁 )
 
Conjur why don't you set them up for one of the proxies and pull down some more WUs?

There is a thread listing the proxies here
 
Hmmm....stuff is getting through as my home queue is submitting WUs. But OK's Proxy is having a problem as it has nearly 800 WU's results queued. It could take a while to get that backlog flushed once the problem is resolved!
 
Well, I keep a cache of 10 WUs on all of my PCs EXCEPT for my laptop so I'm usually pretty safe. And, there was some reason I never went the proxy route. There's some stat that no longer shows if you go thru a proxy but I forgot what that was......
 
Just got home and was able to send about 8-9 WUs and bring down several more new ones. Just keep retrying if you get timeout errors.
 
I only keep a 5 wu cache. The well is running dry. As soon as they're up, I gotta change it to a 10 wu cache. Yeah, badthad, I remember the infamous cable cut too. :Q
 
Back
Top