The servers have been screwed up for what 4 days now? I know you guys are working hard to fix the problem but as im sure you are aware:

1) New users are totally hating Boinc and blaming it for the problems. They think the world is ending cuz they cant send work back.Im afraid their just gonna give up on it.
2) If the servers crashed how can they be expected to handle the tidal wave of results that are going to be sent to them once there fixed?

So does anyone have any clue as to how this issue is going to be resolved?

---

Nice, original idea, Ace. We haven't read this in a dozen other threads. Thanks for the contribution.

---

-----

So does anyone have any clue as to how this issue is going to be resolved?

I don't think they've applied anywhere near enough beer to the equation to hope that a resolution is at hand. So, in an effort to help the cause, I and the others here in the shop, are now heading across the street to do our part to help.

Since the servers at Berkeley are not keeping up with demand, currently at least 4 days behind I see the following.

Bring out the new "enhanced" seti client immediately. Begin Upload and download work for this client only.

The previous 5 days work will have to figured out but is probably lost. The servers just cannot keep up and they are too far behind.

That's how I see it. Too bad for the last 5 days work but let's get on with the program science.

---

Boinc....Boinc....Boinc....Boinc....

Band the optimised app's.

---

lets face the truth
this whole boinc thing sucks
why the hell they close classic seti

lets face the truth
this whole boinc thing sucks
why the hell they close classic seti

Waah Waah. Crybaby. $hit happens. Deal with it. So BOINC is having issues with uploads right now. Big deal. Get on with your life.

---

You will be assimilated...bunghole!

lets face the truth
this whole boinc thing sucks
why the hell they close classic seti

Why? Because there are more people signing up and because BOINC can host more than one project at a time. BOINC does NOT suck. here is a link for other projects:
Active Distributed Computing Projects There are several that operate with BOINC and several that do not.

---

"By faith we understand that the universe was formed at God's command, so that what is seen was not made out of what was visible". Hebrews 11.3

lets face the truth
this whole boinc thing sucks
why the hell they close classic seti

Because Classic sucked even worse. It just wasn't visible to the crunchers.

---

The previous 5 days work will have to figured out but is probably lost. The servers just cannot keep up and they are too far behind.

@Geek,

We've seen problems like this many times before. You've been here.

Each time, there is a problem on the servers. They work on the problem, find the bottleneck, and then the servers are able to stay a little bit ahead, but it took a while for the proverbial hole to be dug, so it takes a while for it to fill back in.

... but all the work has been collected and credited.

I think we should wait until work is actually lost before we start obsessing about work being lost.

---

The servers have been screwed up for what 4 days now? I know you guys are working hard to fix the problem but as im sure you are aware:

1) New users are totally hating Boinc and blaming it for the problems. They think the world is ending cuz they cant send work back.Im afraid their just gonna give up on it.
2) If the servers crashed how can they be expected to handle the tidal wave of results that are going to be sent to them once there fixed?

So does anyone have any clue as to how this issue is going to be resolved?

Former Classic users hate BOINC because it isn't Classic. I don't think there is a way to fix that without just plain keeping Classic going.

The servers didn't crash. They are getting many many more connection attempts than they can actually handle, so most requests ultimately go unserviced.

As mentioned in the Technical News, there are enough successful requests that the backlog is slowly decreasing. Each successful transfer reduces the load a tiny bit, and each tiny reduction speeds up the process a tiny bit more, which clears traffic a tiny bit faster, until everything gets back to normal.

---

not visible to the crunchers.

what you mean
i had a bunch of old unix machines doing the grunt work
for seti clasic unattendend
they finished and i got the workunit counted
that was really visible

switching to bonic on 2nd december
i faced more troubles in about 6 days
than in 6 years seti classic before

thanks to the visibility

---

If you want to help, then take your SETI@BOINC offline until you run out off UW´s, and give the servers some time to recover.

Part of the problem is that everybody is fighting to do more SETI-work, while doing the opposit is the solution.

Regards
Anders

not visible to the crunchers.

what you mean
i had a bunch of old unix machines doing the grunt work
for seti clasic unattendend
they finished and i got the workunit counted
that was really visible

switching to bonic on 2nd december
i faced more troubles in about 6 days
than in 6 years seti classic before

thanks to the visibility

With classic the WU's you finished are not recognized by BOINC. When you sign up for BOINC to run SETI@home your credits from classic are DISPLAYED as the amoount of WU's you completed. But when you start with BOINC your credits start at 0.00, which many people do not like. The problems you are experiencing are the same EVERYONE is having. As soon as classic is switched to BOINC all will be well. Also more and more people sign up with projects everyday using BOINC. so with more using BOINC, why should SETI NOT do the switch? Technology advances therefore SETI has to adapt to that technology in order to NOT lose people. I am being patient and am watching the progress from the site. I will NOT quit working with SETI@home. I just have to wait. Just like everyone else. Be patint :)

---

"By faith we understand that the universe was formed at God's command, so that what is seen was not made out of what was visible". Hebrews 11.3

not visible to the crunchers.

what you mean
i had a bunch of old unix machines doing the grunt work
for seti clasic unattendend
they finished and i got the workunit counted
that was really visible

switching to bonic on 2nd december
i faced more troubles in about 6 days
than in 6 years seti classic before

thanks to the visibility

There are two parts to this:

The cruncher on your machine, and the data collection at Berkeley.

I understand from this post that there are deep problems with Classic.

Note that none of these are anything you'd see as a cruncher because they're all in the back end -- all on machines that only the folks at Berkeley can see.

---

not visible to the crunchers.

what you mean
i had a bunch of old unix machines doing the grunt work
for seti clasic unattendend
they finished and i got the workunit counted
that was really visible

switching to bonic on 2nd december
i faced more troubles in about 6 days
than in 6 years seti classic before

thanks to the visibility

There are two parts to this:

The cruncher on your machine, and the data collection at Berkeley.

I understand from this post that there are deep problems with Classic.

Note that none of these are anything you'd see as a cruncher because they're all in the back end -- all on machines that only the folks at Berkeley can see.

I agree. The problems are NOT with OUR computers. Its the problems the hardware and servers are having. But its not soo much a problem as it is a process. It takes a lot of time to transfer all that data, accounts, files, and WU's...etc.

---

"By faith we understand that the universe was formed at God's command, so that what is seen was not made out of what was visible". Hebrews 11.3

not visible to the crunchers.

what you mean
i had a bunch of old unix machines doing the grunt work
for seti clasic unattendend
they finished and i got the workunit counted
that was really visible

switching to bonic on 2nd december
i faced more troubles in about 6 days
than in 6 years seti classic before

thanks to the visibility

There are two parts to this:

The cruncher on your machine, and the data collection at Berkeley.

I understand from this post that there are deep problems with Classic.

Note that none of these are anything you'd see as a cruncher because they're all in the back end -- all on machines that only the folks at Berkeley can see.

I agree. The problems are NOT with OUR computers. Its the problems the hardware and servers are having. But its not soo much a problem as it is a process. It takes a lot of time to transfer all that data, accounts, files, and WU's...etc.

My post is about problems with Classic not with SETI/BOINC.

---

My post is about problems with Classic not with SETI/BOINC.

Classic or BOINC...does not matter. The issues are with Berkeley, not us. Classic is shuttig down. So its not a problem its a process. Classic will not exist at all in a short while. So if you would like to continue with SETI@Home you will HAVE to use BOINC.

---

"By faith we understand that the universe was formed at God's command, so that what is seen was not made out of what was visible". Hebrews 11.3

lets face the truth
this whole boinc thing sucks
why the hell they close classic seti

Waah Waah. Crybaby. $hit happens. Deal with it. So BOINC is having issues with uploads right now. Big deal. Get on with your life.

Bonic is not having the issue, Seti is having the issue. COme on guys, lets get it right

---

what problems with seti claasic
the only problem with seti classic
was forced switching to boinc

seti classic was working
while boinc is not

thats the fact

---