I think the database is a little mad right now. Was it some new changes for the limits to get removed that hosed it all up, or what?

I am only hoping it is not something new that delays the limit changes any further, the way this machine is struggling at times the sooner they can increase or remove the limits the better.

They might have run into problems with the database changes to increase the maximum number of records....

---

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

I have a full GPU cache on both machines now.

some should be so lucky ... not thing here all day ...

soooo frustrating

---

They might have run into problems with the database changes to increase the maximum number of records....

Could be. The db is defiantly unhappy. Trying to pull up host info or tasks is iffy at the moment for me.

Maybe the RAID choked again and is in rebuild mode.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

This is a strange problem. Of my 4 crunchers, two have managed to connect this morning and reported all their finished tasks. However they were not able to download any new tasks. My other two machines have so far totally failed to connect despite much button abuse every 5 minutes. Of course Murphy's law has struck as usual and it is the two with GPUs which are therefore desperate for work that have not been able to connect, while the two with only CPUs that have about 10 days work each were able to connect.

---

I've had little problem uploading results, but cannot report them.
Looking at the Crickets very little is being passed in or out.
The status page shows most things working, there are WU available for dispatch, but the transaction rate is way down.
Hmm
So has the scheduler croaked, despite it reporting healthy?

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

I am really beginning to miss being able to build a cache. My GPU's ran dry for the umpteenth time again last night.

Steve

---

Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website

I've had little problem uploading results, but cannot report them.
Looking at the Crickets very little is being passed in or out.
The status page shows most things working, there are WU available for dispatch, but the transaction rate is way down.
Hmm
So has the scheduler croaked, despite it reporting healthy?

That just lists the status of the service. It doesn't indicated if there is anything preventing it from being connected to, or functioning correctly.

If something is not working correctly we won't really know until they decide to share it with us. That is if they are aware of any issues.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

When they eventually solve the current problem, it will probably create another one. Suddently everyone will want to report and fill up at the same time and with over 4300 AP units waiting to be sent out the bandwith is going to vanish so that the connection problems continue. By the time that problem sorts itself out we wil be at the next weekly outage:))

---

mollases. The website seems to be on dialup. It's taking a long time just to load pages on the forums. What gives

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

Hope they'll fix it this year.

mollases. The website seems to be on dialup. It's taking a long time just to load pages on the forums. What gives

Well, something in the server closet is very unhappy. If it's the database, don't forget that the forums use the database too to post user stats.

I dunno if it's anything simple that a quick reboot when the boyz get into the lab this morning is gonna fix. If not, I suspect some info will be posted about the issue today.

Vader seems to have been twitchy lately, Boinc server code still has to be fixed, the database record size adjustment may not be complete....

Like many others, I would not be as troubled by some extra downtime if the cache limits were raised so I could build enough cache to keep working through such difficulties. But therein lies the rub...some of the adjustments have to be completed before limits can be raised or lifted.

---

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

Looks like someone just got out of bed and kicked the servers. Suddenly my main cruncher was able to report all of its 150 finished tasks and get 1 new download! One down, about 799 to go.

---

Looks like someone just got out of bed and kicked the servers. Suddenly my main cruncher was able to report all of its 150 finished tasks and get 1 new download! One down, about 799 to go.

Indeed! I see a glimmer of green on the ol' Cricket graph!

Meow meow meow.

---

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

The error I'm seeing changed from "HTTP internal server error" which could be a number of things to
"Couldn't connect to server" which makes me think they're doing something.

---

Yes ever since my one successful connection, I have been getting the same response. Well we are still in the 3 day weekly outage window, so we cant complain (too much) about connection problems.

---

Alas, just a little blip for the Cricket.
But, it should mean that they are trying to sort things.

Kitties sending them that famous kitty juju.....meowomm, meowomm, meowomm.....

---

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

Looks like someone just got out of bed and kicked the servers. Suddenly my main cruncher was able to report all of its 150 finished tasks and get 1 new download! One down, about 799 to go.

Indeed! I see a glimmer of green on the ol' Cricket graph!

Meow meow meow.

Whatever it was it seems to have stopped again, according to my all tasks page this machine managed to report all that it has done but the server did not manage to report back so they are still listed as ready to report here.

Decisions decisions, I have to go to work in a couple of hours and GPU's do not have enough to last untill I get home. I might have to leave gpu's crunching VLAR's overnight:-(

---

Kevin

Yes ever since my one successful connection, I have been getting the same response. Well we are still in the 3 day weekly outage window, so we cant complain (too much) about connection problems.

Does those 3 days still count? I mean, the message is removed from the front page and have been after every Tuesdays outage for a long time.

Yes ever since my one successful connection, I have been getting the same response. Well we are still in the 3 day weekly outage window, so we cant complain (too much) about connection problems.

Does those 3 days still count? I mean, the message is removed from the front page and have been after every Tuesdays outage for a long time.

It's like the "allow 30 days for delivery" when they know that they're usually going to deliver in 2 or 3 days. In this case they normally finish in a few hours but the 3 day window gives them some extra time in case something comes up that takes longer.

Used to call that the "Scotty clause". Let's see who can figure out the connection.

---

Finally got a good connection and reported 269 completed tasks but got no new tasks. The cricket graph is charging back up too.

---