The Linux machine is in the process of getting kicked. I'm down 300 tasks on it. Been getting the "no work is available" message all day.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

The Linux machine is in the process of getting kicked. I'm down 300 tasks on it. Been getting the "no work is available" message all day.

. . Apart from needing to do lots of server kicking, I am loving these new Blc04 WUs. They only take as long to run on GPUs as a normal Arecibo task. And despite that they are even quicker to run on CPUs than any other Blc task. Only 40 mins each on my i5-6600 :) I'll take all they can give me :)

Stephen

:)

And my luck would have it that I have received nothing but Arecibo shorties as I recover the 200 ghosts the server created when I had the server communication issue.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

And my luck would have it that I have received nothing but Arecibo shorties as I recover the 200 ghosts the server created when I had the server communication issue.

. . There seems to be plenty of them at the moment so hang in there :)

Stephen

:)

And my luck would have it that I have received nothing but Arecibo shorties as I recover the 200 ghosts the server created when I had the server communication issue.

. . There seems to be plenty of them at the moment so hang in there :)

Stephen

:)

. . Damn, I spoke too soon, they seem to have dried up :(

Stephen

:(

And my luck would have it that I have received nothing but Arecibo shorties as I recover the 200 ghosts the server created when I had the server communication issue.

. . There seems to be plenty of them at the moment so hang in there :)

Stephen

:)

Well it turned out I had about 260 ghosts. Every recovery session to clear them netted nothing but Arecibo shorties. Spent most of the afternoon and early evening doing that. And it was nothing to do on my part just the internal server error communications on several work requests.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Well it turned out I had about 260 ghosts. Every recovery session to clear them netted nothing but Arecibo shorties. Spent most of the afternoon and early evening doing that. And it was nothing to do on my part just the internal server error communications on several work requests.

. . I do not envy going through that, juggling half a dozen windows and holding your tongue just right to provoke the resends is tedious and getting only 20 at a time makes it all the more so. I have 48 of them on this rig but I lack the spirit to tackle that ATM :(

Stephen

:(

For the last 30 mins or so, I've been getting that dreaded message about task availability. Maybe it'll sort itself out, now that I've posted!

---

Don't take life too seriously, as you'll never come out of it alive!

I've never been so lucky. Always had to give the machines the old recovery kick. In the process of 5 minute countdown now.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

For the last 30 mins or so, I've been getting that dreaded message about task availability. Maybe it'll sort itself out, now that I've posted!

. . You can almost bet on that :)

Stephen

:)

Woke up this morning to the Linux machine with no GPU tasks onboard or running and only running on the CPU. Have "no work is available" messages in the log for the past 5 hours. Time to kick the servers.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I can't actually remember running out of tasks other than during maintenance periods, or server outages affecting everyone. I'm sure their was times, but not in recent memory ... shhh, about age now!
I have seen the cache run down very low, 25% maybe, then recover, and repeat, but not actually run out.
A kick usually makes it act normal again, for me any ways ....

This has happened to me twice now on the Linux cruncher. It takes less than 3 hours to mow through my 300 task GPU allotment. So 3 hours of no work is available responses from the servers and I am running only my CPU cache. When I wake up in the morning the first thing I do is pull up BoincTasks and see what is running. If I see 8 cpu tasks running on the Linux machine I know I ran out of gpu tasks overnight. I've had lots of instances like yourself where I get really low on gpu cache, maybe 25 tasks, but it has either pulled them out of the servers on its own, or I have been around to kick the servers.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

This has happened to me twice now on the Linux cruncher. It takes less than 3 hours to mow through my 300 task GPU allotment. So 3 hours of no work is available responses from the servers and I am running only my CPU cache. When I wake up in the morning the first thing I do is pull up BoincTasks and see what is running. If I see 8 cpu tasks running on the Linux machine I know I ran out of gpu tasks overnight. I've had lots of instances like yourself where I get really low on gpu cache, maybe 25 tasks, but it has either pulled them out of the servers on its own, or I have been around to kick the servers.

. . For me on the Linux big hitter I routinely do the "kick the server in the pants" thing. Any time the cache drops more than a dozen or so tasks below normal I do it. Usually it is right for a few hours after that. I don't want it running out whenever my back is turned.

Stephen

:)

...getting ready for this week's outrage in a few hours time.

Not that there's anything I can do as I'm at work, miles from my crunchers.

---

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

...getting ready for this week's outrage in a few hours time.

Not that there's anything I can do as I'm at work, miles from my crunchers.

. . Work is the curse of the crunching man ...

. .If you'll pardon the bad paraphrase ...

Stephen

:(

The splitters don't seem to be running properly. The output is only ~3 tasks per second when it is usually 60-70 tasks per second after the resumption from outage.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

The splitters don't seem to be running properly. The output is only ~3 tasks per second when it is usually 60-70 tasks per second after the resumption from outage.

Back up to >56 tasks/sec. This seems to happen each week until the transitioner backlog is cleared.

---

Well I was looking at the Haveland/Munin page and it spiked to 70 per second as the project came back but promptly cratered. And if you look at the Munin page by week, last weeks splitters output didn't show that. It had a good solid sustained 6 hours of 65 tasks per second output.

seti@home Server Statistics

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Time to kick the servers. Only half my allotted cache on all machines.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)