OK, so I'm not getting any work either.

What's broken now?

According to the server page, everything is OK.

Do you believe that? I don't. So at the very least, the server status is broken.

Bah!

2 of your computers are getting work, just one isn't. Look to it to make sure it is asking for work.

---

Definitely something wrong somewhere, my 660's are already doing backup projects and my 550Ti's are about to do the same.

A feeder issue maybe?

Cheers.

To add to the difficulty in getting work, there won't be any to get anyway- the splitters have stopped splitting again.
Even though the server staus page shows themn running & tonnes of data ready to be split.

---

Grant
Darwin NT

Now I will get gastric problems, including flatulence, belching, abdominal bloating and pain, headache, pain, indigestion and dizziness.

I should hope so.

---

Grant
Darwin NT

Now I will get gastric problems, including flatulence, belching, abdominal bloating and pain, headache, pain, indigestion and dizziness.

I should hope so.

With all of that going-on, I'm just glad he's in Sweden and not at my house.

I wonder if the creation rate could be related to file 20jn12ac as it has been in its current state for way longer than is usual.

That file is still in SSP.

I sent a message to Eric asking about it, but have not received a response as of yet.

Looks like they re-kicked that file as it's back down to 13 from 14 but whether that will help it....

Cheers.

I did get a response from Eric this afternoon whilst I was at work. He was having some time off with dear Angela this weekend.

He said that when a dataset (he used the word 'tape') gets stuck like that, it DOES tie up a splitter, thereby reducing potential work production by 1/6th, as there are 6 enabled MB splitters at present.

I emailed him back, politely asking why then, was the offending dataset still languishing in the queue....LOL.

If what you are telling me is correct, it looks like he DID give it a kick, but it must have gotten stuck again.
I suspect when he gets my message tomorrow, he'll take another look at it and either kick it again or eject it.
Either way, it's on his radar now, and I am sure he'll keep an eye on it.

The moral of the story is, kitties......
If anybody notices a dataset 'stuck' like that for more than a couple of days, when everything else around it has been split and sent out, please feel free to PM me or at least bring it up in the forums. It DOES tie up a splitter when that happens. I'll try to get the message to Eric.

Meow.

---

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

My GPU is rarely getting work also.
I want my VLAR`s back.

---

With each crime and every kindness we birth our future.

I am wondering what the sustained inbound traffic to the servers as seen on the Cricket graphs for the last 10-11 hours is all about.....

It is unlike any 'normal' comms from the hosts, and it is also unlike any previous bursts of uploading new data from the lab.

DOS attack??

The kitties are curious.

---

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

I am wondering what the sustained inbound traffic to the servers as seen on the Cricket graphs for the last 10-11 hours is all about.....

It is unlike any 'normal' comms from the hosts, and it is also unlike any previous bursts of uploading new data from the lab.

DOS attack??

The kitties are curious.

I was thinking it might be the usual data from the archive traffic, but limited by whatever is causing issues with the Scheduler/splitters/feeders.

There's plenty of work there, but it's just not being allocated. AP assimilators are backing up again. Ready-to-send buffer actually spiked much higher than usual before it topped out.
So something's gummed up the works.

---

Grant
Darwin NT

I am wondering what the sustained inbound traffic to the servers as seen on the Cricket graphs for the last 10-11 hours is all about.....

It is unlike any 'normal' comms from the hosts, and it is also unlike any previous bursts of uploading new data from the lab.

DOS attack??

The kitties are curious.

I was thinking it might be the usual data from the archive traffic, but limited by whatever is causing issues with the Scheduler/splitters/feeders.

There's plenty of work there, but it's just not being allocated. AP assimilators are backing up again. Ready-to-send buffer actually spiked much higher than usual before it topped out.
So something's gummed up the works.

I just dunno....
Whatever is going on, it is not usual.

When you are on the Cricket graphs, click the 'long term' link.
There has not been any activity similar to this since the move to the colo.

---

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

When you are on the Cricket graphs, click the 'long term' link.
There has not been any activity similar to this since the move to the colo.

Nope.
But then we haven't had Scheduler/feeder issues either since the move. Till now.

---

Grant
Darwin NT

2 of your computers are getting work, just one isn't. Look to it to make sure it is asking for work.

The one not getting work is no longer online. It was GPU only. I recently acquired an i7-3820 and MB and 4x2GB of quad channel 2133MHz RAM (thanks, Craigslist!), and have replaced Unimatrix002 with I7-3820. Am now running 8 HT cores, with 4 CPU tasks and the other 4 reserved for graphics support (love those AP 6.04s!).

When I can get them, that is.

Right now, neither is getting work except for a (very) few APs overnight. I7-3820 is about to run out of work; Fermibox2 still has a bunch to do.

---

Re. lack of AP work. Could it be that more and more switch to doing AP only (like me), due to the credits + there's now a stock linux GPU AP app?

Re. lack of AP work. Could it be that more and more switch to doing AP only (like me), due to the credits + there's now a stock linux GPU AP app?

Maybe, but I note that on the server status page, the number of channels to do for MB hasn't changed since at least last night, and very few (if any) of AP have been processed either.

Definitely seems to be a splitter problem, at least at first glance.

---

UPDATE: Since my last post, SSP says that 3 channels of AP and 3 of MB have been processed. Not very much.

---

Re. lack of AP work. Could it be that more and more switch to doing AP only (like me), due to the credits + there's now a stock linux GPU AP app?

Maybe, but I note that on the server status page, the number of channels to do for MB hasn't changed since at least last night, and very few (if any) of AP have been processed either.

Definitely seems to be a splitter problem, at least at first glance.

I think its more a feeder problem since still over 300.000 V7 are ready to send.
I might be wrong on that.

---

With each crime and every kindness we birth our future.

I think its more a feeder problem since still over 300.000 V7 are ready to send.
I might be wrong on that.

The question then becomes: do we split a feeder or feed a splitter?

---

Right now, neither is getting work except for a (very) few APs overnight. I7-3820 is about to run out of work; Fermibox2 still has a bunch to do.

About to run out of work is normal with the BOINC 7.X. Unless you change the setting for connect every to a long value, it drains the queue until it is dry before it asks for more work.

e.g. set to default 10 times a day, queue is drained to 1/10 day's work. Set to every 2 days, queue is drained to 2 days work. Yeah, kind of works backwards.

I don't suggest a too big value for the extra work fill either. We haven't had a long outage since they have moved to the co-lo and too big a number here simply runs you into the max tasks limit and you don't get it anyway.

---

And I see the 'mystery bandwidth' has continued.
The kitties have been losing cache all night. Not a usual thingy since the move to the colo.
Hopefully they'll sort it all during today's outage.

---

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

Guess something got fixed. My first request after maintenance brought me back to the limits. Hope it holds up.

And I see the 'mystery bandwidth' has continued.

Don't know what to think of that. Maybe they thorottled back to Lab-to-CoLo transfers?

---

Another Fred
Support SETI@home when you search the Web with GoodSearch or shop online with GoodShop.