The server tries to fill the most efficient first which would be your GPU. Once filled it will then start asking for CPU work. You can go into your Account page, Seti@Home preferences and check the don't use GPU. This won't hurt any work you already have but then it will just ask for CPU work. Just remember to go back in and uncheck it when you get enough CPU stuff.

---

PROUD MEMBER OF Team Starfire World BOINC

Can someone tell me how to get this machine back in the loop!! here are the messages:
Sending scheduler request: to report completed tasks.
Reporting 342 completed tasks, requesting new tasks for CPU and NVIDIA
Scheduler request failed: HTTP internal server error.


What do I need to do??

Thanks John Ellwood Burtscher-- over 12,554,221 SETI credits.

---

Can someone tell me how to get this machine back in the loop!! here are the messages:
Sending scheduler request: to report completed tasks.
Reporting 342 completed tasks, requesting new tasks for CPU and NVIDIA
Scheduler request failed: HTTP internal server error.


What do I need to do??

Thanks John Ellwood Burtscher-- over 12,554,221 SETI credits.

See this post and thread in the Number Crunching forum.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Greetings from Africa...hope things will be back on the rails shortly...well done to the electricians
cheers
Ralph

---

Point is there was about 5 hours notice.

A full 5 hours?

Sorry, but you've got to be kidding. You should probably start to realize that people have a daytime job or rather playing with the kids than checking every few hours if there "possibly" is an outage announced on short notice.

As mentioned by others, the point is that there is (was?) no way to get official notice about any outage when you notice hours into the outage that there is no communication with the project in your BOINC client(s).

There should be rather some serious thoughts about separating the database/science part of the project from the website/forum.
Website/forum down isn't a big deal and when this happens to the database/science part, everyone has a place to check out why. Most people would probably call this common sense (I know, a rare commodity these days)...

Ralf

Point is there was about 5 hours notice.

A full 5 hours?

Sorry, but you've got to be kidding. You should probably start to realize that people have a daytime job or rather playing with the kids than checking every few hours if there "possibly" is an outage announced on short notice.

As mentioned by others, the point is that there is (was?) no way to get official notice about any outage when you notice hours into the outage that there is no communication with the project in your BOINC client(s).

There should be rather some serious thoughts about separating the database/science part of the project from the website/forum.
Website/forum down isn't a big deal and when this happens to the database/science part, everyone has a place to check out why. Most people would probably call this common sense (I know, a rare commodity these days)...

Ralf

For what reason? If the power is out no computer is going to be reachable.

Look here for status when it hits the fan.

Do you want a personal phone call when there is a major unplanned event?

---

Do you want a personal phone call when there is a major unplanned event?

LOL... Yes please, but only on day hours, by night I preffer an email...

It really doesn't matter too much to know it in advance, there is not much we can do to be "ready" for the outage, and most users will not even notice it... But if it happens that you find your host idle or just with transfers issues, it will be nice to be able to know what happens without hiring an investigator...

What I think is that in the event of a long outage, planned or not, it would be nice that the project URL were redirected to a small and simple page with a little explanation.

It's not a priority thing, but it's something that should not be very complex to do and it will be a nice touch for those that are not around here as often as the addicts like me...

---

One would think the most logical thing to do would be to visit the website for problems, and if available, check the forums. If the website is down, its safe to assume that the servers are not responding and are therefore the cause of being unable to connect to them with your client.

No need to hire an investigator, or pull your hair out wondering why. If you pull up to a store and all the lights are out, do you really need a sign out front or a person to tell you that its closed?

Talk about lacking common sense...

Do you want a personal phone call when there is a major unplanned event?

LOL... Yes please, but only on day hours, by night I preffer an email...

It really doesn't matter too much to know it in advance, there is not much we can do to be "ready" for the outage, and most users will not even notice it... But if it happens that you find your host idle or just with transfers issues, it will be nice to be able to know what happens without hiring an investigator...

What I think is that in the event of a long outage, planned or not, it would be nice that the project URL were redirected to a small and simple page with a little explanation.

It's not a priority thing, but it's something that should not be very complex to do and it will be a nice touch for those that are not around here as often as the addicts like me...

And how do you propose a re-direct if all the servers are down and the power is turned off? Inquiring minds want to know....

---

JEKitsonSr

We could have a pre-defined backup domain. for 60$ a year you can have unlimited hosting.. It should be within the seti@home budget, or even the Berkeley (Boinc) budget to pay 50-60$ a year for a hosted domain on which information could be posted?

---

#resist

Instead of an impossible redirect, I would have suggested a managed update of DNS as they shouldn't be on site. For a planned outage, the subdomain's resource record refresh rate is increased before the switch so that an update will happen relatively immediately.
However, with infinite wisdom, the forum website has the same domain name as the project's, so after a DNS update the backup info site would be swamped with half a million machines trying to connect. Not good!

The forum is also intimately tied to the project database, so it couldn't run standalone, unless connecting to a remote multiple master db, or to a slave as readonly.

A free blog site such as setiathome.wordpress.com could suffice, at present available for someone to register.

Or how about:
Twitter feed?
Boincstats shoutbox?
An official Facebook page? (not the uninteractive wiki)

I could also update my stats page on http://setistats.haveland.com/ if someone lets me know.

So many ways to communicate now - no excuses for info darkness.

The problem is that its a University of California, Berkeley science project, and therefore needs to be under the berkeley.edu domain.

There's only information darkness if you must have someone hold your hand and guide you to what should be intuitively obvious.

Well [blankman], I was one of the lucky few that got over to the boinc forums before they too went down, and managed to get the news. However, when our project is down, AND Berkeley DC is down, we do have a big lack of information source. Besides Lunatics. Which I guess I should get some links and get hooked up...


And in response to the previous poster, I wasn't referring to a redirect or anything of the sort. Just a simple website named "www.setiathome.com" or "www.boinc.com", where information could be relayed by project people in the event of major outages like we've had recently.
[Edit: They could even have this "backup" domain simply redirect to it's respective main site, EXCEPT during an outage, during which it would then display news, updates, whatever. for 50-60$ a year, I feel it's a waste to NOT do it.]

---

#resist

There is never a lack of information, there is only ways to interpret the information available.

Again, if the servers are down, you can't get to the website, that it would seem obvious that there's no point in going forward until later. Try again in a couple days.

There is never a lack of information, there is only ways to interpret the information available.

Again, if the servers are down, you can't get to the website, that it would seem obvious that there's no point in going forward until later. Try again in a couple days.

The point is....

Many of us dedicated Setizens would like to know WHY the servers are down.
And any info on when they might be expected to be back up.

---

"Time is simply the mechanism that keeps everything from happening all at once."

There is never a lack of information, there is only ways to interpret the information available.

Again, if the servers are down, you can't get to the website, that it would seem obvious that there's no point in going forward until later. Try again in a couple days.

The point is....

Many of us dedicated Setizens would like to know WHY the servers are down.
And any info on when they might be expected to be back up.

The point is...

You'll get told as soon as they can get the information to us. Does WHY really matter in the immediate, when its just as good later?

There is never a lack of information, there is only ways to interpret the information available.

Again, if the servers are down, you can't get to the website, that it would seem obvious that there's no point in going forward until later. Try again in a couple days.

The point is....

Many of us dedicated Setizens would like to know WHY the servers are down.
And any info on when they might be expected to be back up.

The point is...

You'll get told as soon as they can get the information to us. Does WHY really matter in the immediate, when its just as good later?

It eases our Seti anxiety.

---

"Time is simply the mechanism that keeps everything from happening all at once."

There is never a lack of information, there is only ways to interpret the information available.

Again, if the servers are down, you can't get to the website, that it would seem obvious that there's no point in going forward until later. Try again in a couple days.

The point is....

Many of us dedicated Setizens would like to know WHY the servers are down.
And any info on when they might be expected to be back up.

The point is...

You'll get told as soon as they can get the information to us. Does WHY really matter in the immediate, when its just as good later?

It eases our Seti anxiety.

So would medication! ;-P

One would think the most logical thing to do would be to visit the website for problems, and if available, check the forums. If the website is down, its safe to assume that the servers are not responding and are therefore the cause of being unable to connect to them with your client.

No need to hire an investigator, or pull your hair out wondering why. If you pull up to a store and all the lights are out, do you really need a sign out front or a person to tell you that its closed?

Talk about lacking common sense...

If the only provider of what I need is closed when it should be open and there is no notice of why or for how much time they could lose a customer... It's not a good way to handle a bussines.

That's how it is, common sense is the least common of the senses...
Assuming that everybody knows what you know and that everybody should perceive things as you see them it's a good sample of what "lack of common sense" means.
I've crunched for SETI for almost 13 year, but I've discovered the forums just 6 months ago.

SETI has 2 million donors but, if you look here, you will not see so many names, so for the rest of the world if they are not able to reach the SETI pages most of them will not know what it means.

About redirecting the home page, I'm sure it's possible, my home balancing router can redirect traffic based on the URL or IP address, so I'm sure that H.E. (the ISP) has more advanced routers than mine, so it should be as simple as calling them asking to re-route (specific) traffic temporarily to a simple page with a brief notice. Even if what I'm saying is not possible (for whatever cause: from technical stuff up to University rules) there are a lot of other ideas proposed here.

And as I said, this is not a priority, it's just a good way to be nice with all the people that contribute to the project. And is not a critic or a complain, it's just an idea for making things a bit better.

I dont get why somebody feels the necessity to reject ideas to make things better, if things were already perfect, then, we would not be having this conversation... Of course, it may happen that none of the ideas is possible, well, then we will live with that... it's not that we are going to make a strike... well, not me at least :D

---

One would think the most logical thing to do would be to visit the website for problems, and if available, check the forums. If the website is down, its safe to assume that the servers are not responding and are therefore the cause of being unable to connect to them with your client.

No need to hire an investigator, or pull your hair out wondering why. If you pull up to a store and all the lights are out, do you really need a sign out front or a person to tell you that its closed?

Talk about lacking common sense...

If the only provider of what I need is closed when it should be open and there is no notice of why or for how much time they could lose a customer... It's not a good way to handle a bussines.

But SETI@Home is not a business, and you're not a customer, and there was no promise of uptime, so who says it should be open?

Your a volunteer, ready to crunch work when the project is up, and its your job to keep your CPUs busy when SETI@Home is not.