About time to start another one.

---

Anyone else having troubles getting work?

---

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

A proud member of the OFA (Old Farts Association)

Nope.

Well you did ask..........

[edit] BTW, I use 6.10.60 and seeing as Mark's just a bit older than me he uses 6.10.58. :-D

Cheers.

Anyone else having troubles getting work?

At the moment, no.
But looking at my log, it shows there have been issues getting work for several hours. Multiple requests resulting in nothing, before finally getting then in one or 2 hits.

---

Grant
Darwin NT

That's what I have been dealing with. Multiple requests for work and nothing but your machine has reached its limit. Then finally after 5 o 6 requests I get one task or if lucky five. Nothing close to replenishing what I turn in at each scheduler contact.

---

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

A proud member of the OFA (Old Farts Association)

Well I think I finally figured out how to fix the problem. The old scheduler project app preferences was buggered like it used to do. I had been simply toggling on and off the separate MB and AP app buttons to no effect. Triple Update was doing nothing.

Finally I did the complete unselect of all projects on the preferences page. When you do that that, the individual app buttons disappear and the project then says "All projects" enabled.

I finally started getting cache task refills in the 100 or so bunch at a time like you normally do. I wish I had remembered that trick about 6 hours ago. Forgotten how to do that since the project preferences bug has not been showing up now for several months.

---

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

A proud member of the OFA (Old Farts Association)

Not sure if what you make made the difference since i did not make anything and my host start to receive the work by the 100's like normally too.
Maybe somebody kicks some server buts on the lab side.

<edit> But after some rounds of all normal new work the old msg reapears:

Tue 27 Mar 2018 06:33:20 AM EST | SETI@home | This computer has reached a limit on tasks in progress

I know if far from the limit so the bug returns or is a new one.

---

Ahhh...website is back, but still no tasks.
That was a fun outrage....past 24 hrs so far...

---

Humans may rule the world...but bacteria run it...

Ahhh...website is back, but still no tasks.
That was a fun outrage....past 24 hrs so far...

. . I make it just on the 24 hour mark. BUT ... I cannot report work or get new tasks. I keep getting the server brush off or the http error message.

Stephen

:(

The same here

Wed 28 Mar 2018 07:46:03 AM EST | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
Wed 28 Mar 2018 07:47:37 AM EST | SETI@home | Scheduler request failed: HTTP internal server error

---

So anyone was just changing some settings to prevent BOINC turning my laptop into a toaster while Maximising usage, and not i got no calculations to run... because all are done and i cant get any new.

The same here

Wed 28 Mar 2018 07:46:03 AM EST | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
Wed 28 Mar 2018 07:47:37 AM EST | SETI@home | Scheduler request failed: HTTP internal server error

. . Well it is way past my bedtime. I have been trying to report for 1.5 hours and I give up. I'm going to bed and so are the PCs ....

Stephen

:(

For HTTP internal server error only:

Try reducing the number of tasks reported at once. In cc_config.xml, set

<max_tasks_reported>N</max_tasks_reported>
Report at most N tasks per scheduler RPC. Try N=50 or N=64 if your computer has lots of tasks to report and is having trouble completing a scheduler RPC.

My take on this is that I am getting this failure only on the computer which has a lot of tasks to report. My other computers just continues along in Bristol fashion.

83917 SETI@home 3/28/2018 09:40:56 Fetching scheduler list
83918 SETI@home 3/28/2018 09:40:58 Master file download succeeded
83919 SETI@home 3/28/2018 09:41:04 Sending scheduler request: Requested by user.
83920 SETI@home 3/28/2018 09:41:04 Reporting 397 completed tasks
83921 SETI@home 3/28/2018 09:41:04 Requesting new tasks for CPU and NVIDIA GPU
83922 SETI@home 3/28/2018 09:42:38 Scheduler request failed: HTTP internal server error


/edit I see you were thinking the same thing Richard. I changed it to 50 at a time and I still cannot connect to the server.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

For HTTP internal server error only:

Try reducing the number of tasks reported at once. In cc_config.xml, set

<max_tasks_reported>N</max_tasks_reported>
Report at most N tasks per scheduler RPC. Try N=50 or N=64 if your computer has lots of tasks to report and is having trouble completing a scheduler RPC.

Reduced to 64, still not works..... FYI My host has more than 2000 WU to report.

Wed 28 Mar 2018 09:27:47 AM EST | SETI@home | Sending scheduler request: Requested by user.
Wed 28 Mar 2018 09:27:47 AM EST | SETI@home | Reporting 64 completed tasks
Wed 28 Mar 2018 09:27:47 AM EST | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
Wed 28 Mar 2018 09:28:57 AM EST | SETI@home | Scheduler request failed: HTTP internal server error

---

After much cajoling, I got one (1) GPU task for the main rig. I have nearly a thousand completed units on the other crunchers that still won't report.

Also, the "tasks" function on the project will not initialize. It just spins.....

---

Looks just like mine Juan. I am now up to 3 hour backoffs.

For HTTP internal server error only:

Try reducing the number of tasks reported at once. In cc_config.xml, set

<max_tasks_reported>N</max_tasks_reported>
Report at most N tasks per scheduler RPC. Try N=50 or N=64 if your computer has lots of tasks to report and is having trouble completing a scheduler RPC.

Reduced to 64, still not works..... FYI My host has more than 2000 WU to report.

Wed 28 Mar 2018 09:27:47 AM EST | SETI@home | Sending scheduler request: Requested by user.
Wed 28 Mar 2018 09:27:47 AM EST | SETI@home | Reporting 64 completed tasks
Wed 28 Mar 2018 09:27:47 AM EST | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
Wed 28 Mar 2018 09:28:57 AM EST | SETI@home | Scheduler request failed: HTTP internal server error

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

I think some lines on the status page aren't updating at all, but I totally agree I have a long list of waiting to be validated even though 2 copies of the WU are done.