Well, this is bizarre. My WinVista machine just got this:

1/17/2018 11:32:03 AM | SETI@home | Sending scheduler request: To fetch work.
1/17/2018 11:32:03 AM | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
1/17/2018 11:32:05 AM | SETI@home | Scheduler request completed: got 0 new tasks
1/17/2018 11:32:05 AM | SETI@home | Project has no tasks available
1/17/2018 11:32:07 AM | SETI@home | Started download of arecibo_181.png
1/17/2018 11:32:07 AM | SETI@home | Started download of sah_40.png
1/17/2018 11:32:07 AM | SETI@home | Started download of sah_banner_290.png
1/17/2018 11:32:07 AM | SETI@home | Started download of sah_ss_290.png
1/17/2018 11:32:09 AM | SETI@home | Finished download of arecibo_181.png
1/17/2018 11:32:09 AM | SETI@home | Finished download of sah_40.png
1/17/2018 11:32:09 AM | SETI@home | Finished download of sah_banner_290.png
1/17/2018 11:32:09 AM | SETI@home | Finished download of sah_ss_290.png

Back to business.

Wed 17 Jan 2018 02:45:33 PM EST | SETI@home | Sending scheduler request: To fetch work.
Wed 17 Jan 2018 02:45:33 PM EST | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
Wed 17 Jan 2018 02:45:36 PM EST | SETI@home | Scheduler request completed: got 95 new tasks

---

On one of my hosts I got those files 3 times, with some minutes apart.

btw On another host I got 88 new tasks.

Well, this is bizarre. My WinVista machine just got this:

1/17/2018 11:32:03 AM | SETI@home | Sending scheduler request: To fetch work.
1/17/2018 11:32:03 AM | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
1/17/2018 11:32:05 AM | SETI@home | Scheduler request completed: got 0 new tasks
1/17/2018 11:32:05 AM | SETI@home | Project has no tasks available
1/17/2018 11:32:07 AM | SETI@home | Started download of arecibo_181.png
1/17/2018 11:32:07 AM | SETI@home | Started download of sah_40.png
1/17/2018 11:32:07 AM | SETI@home | Started download of sah_banner_290.png
1/17/2018 11:32:07 AM | SETI@home | Started download of sah_ss_290.png
1/17/2018 11:32:09 AM | SETI@home | Finished download of arecibo_181.png
1/17/2018 11:32:09 AM | SETI@home | Finished download of sah_40.png
1/17/2018 11:32:09 AM | SETI@home | Finished download of sah_banner_290.png
1/17/2018 11:32:09 AM | SETI@home | Finished download of sah_ss_290.png

. . I have received the resend of these files about 4 times this morning. I am not sure just what it means but it is what you get if you select "reset project".

Stephen

? ?

i've shut down. letting my electric bill take a break.
will power back on in a day. let things settle down a bit.

I am happy, I got 23 WU on one of my computer. Just enough for four houyrs GPU work

Sorry, Correction, I got 150WU. SETI is back . I hope for a very long time.
Well done Berkely.

---

I got a reply from Dr. Korpela about five hours ago; the splitters were reporting themselves as fine with normal output but weren't actually doing any work. This is why it wasn't caught after the outrage. So it will take a while to fill all those hungry caches but it's working.

Those naughty splitters...

---

I have never understood why BOINC decides to fill my slowest crunchers first before ever recognizing my fastest crunchers. Ho-hum.

---

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

A proud member of the OFA (Old Farts Association)

. . <smirk>

mb_splitter/ap_splitter: Reads tapes (or tape images on disk) containing raw telescope data and creates SETI@home (multi-beam) or Astropulse workunits for the BOINC/SETI@home clients. At least one needs to be running to produce work, and that's usually enough.

. . nuff said :)

Stephen

:)

I noticed that gbt_splitter#4 got briefly pulled from duty. Now back. I wonder if it was hanging up the output. Really frustrating that my Linux box is still unable to get any appreciable work while my slow Windows7 boxes have mostly full caches.

---

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

A proud member of the OFA (Old Farts Association)

Really frustrating that my Linux box is still unable to get any appreciable work while my slow Windows7 boxes have mostly full caches.

I noticed that as well... I'm sure some would disagree but I see it with my own eyes: even with a zero resource share, if E@H has minimal work (one WU per slot running and zero cached) and SETI@Home is empty, BOINC often stops asking for SETI@Home work (has zero work units and it's just sitting with no countdown timer to next scheduler request) and I have to hit Update manually to remind it. Well I did that with six fast Linux machines and they got zilch and the seventh was my wife's slower SoG Win7 box and presto... 130 tasks. Just the luck of the draw (I hope.)

---

I noticed that gbt_splitter#4 got briefly pulled from duty. Now back. I wonder if it was hanging up the output. Really frustrating that my Linux box is still unable to get any appreciable work while my slow Windows7 boxes have mostly full caches.

The guys are probably trying to break up the congregation of splitters working on the 1st GBT file in the list (still looks to be a half dozen splitters still working on the 1 file when you zoom in on it) and get them working on other files instead and you just caught them in the act. ;-)

Cheers.

I noticed that gbt_splitter#4 got briefly pulled from duty. Now back. I wonder if it was hanging up the output. Really frustrating that my Linux box is still unable to get any appreciable work while my slow Windows7 boxes have mostly full caches.

. . Ironic as it may be for once I have the opposite experience. Both Linux boxes received nearly full caches (over many requests) while the Windows box got work right away for the GPU but struggled over many many attempts before getting any work for the CPU. I had to reschedule WUs from the GPU Q.

Stephen

? ?

I finally had to shut off gpu work entirely for the project and wait through 4 request cycles before the servers finally decided to send me 40 cpu tasks on the Linux machine. I haven't had any cpu tasks from Seti for 2 days now on that machine until just now.

---

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

A proud member of the OFA (Old Farts Association)

I noticed that gbt_splitter#4 got briefly pulled from duty. Now back. I wonder if it was hanging up the output. Really frustrating that my Linux box is still unable to get any appreciable work while my slow Windows7 boxes have mostly full caches.

. . Ironic as it may be for once I have the opposite experience. Both Linux boxes received nearly full caches (over many requests) while the Windows box got work right away for the GPU but struggled over many many attempts before getting any work for the CPU. I had to reschedule WUs from the GPU Q.

Stephen

? ?

I'm absolutely convinced that the project ignores Ryzen machines for work requests. Couldn't get work on the Windows Ryzen either.

---

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

A proud member of the OFA (Old Farts Association)

Creation time is at 72 a second at the moment. That's the highest I've ever seen it. Most of my machines have a full cache - a couple of them I did have to kick start though.

0 results ready to send and number of units received in the last hour is at 55k but I would imagine those numbers will return to normal in the next few hours.

---

~Chris

Hard to say exactly what the state of play is with the replica being over an hour behind the master....

---

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

....from the number of tasks on my crunchers it looks as if the splitters are spluttering again :-(

---

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

I'd allowed one of my single GPU machines to help Einstein for a while. I've just given it a prod to restore normal service, and got the full 100 at the first request. As somebody said, it's the luck of the draw.

Caches are full and RAC is steadily dropping
............everything back to normal and the Credit Screw is turning as usual.

---

"Sour Grapes make a bitter Whine." <(0)>