I have been doing some playing around today and added
<max_tasks_reported>50</max_tasks_reported>
Which eliminated the HTTP internal error message, by slowing down the reporting.

I have had all my 4000+ tasks in for about 20 minutes now.
Getting a trickle come in now, with a couple of big pulls.

. . Absolutely nothing here on all 4 machines. Within the hour they will begin to fall over with no work.

Stephen

:(

I've found I can usually get away with<max_tasks_reported>100</max_tasks_reported> and have the scheduler accept it with no problems. I don't have as much luck with values higher than that though. Still takes a considerable amount of connections to report all the tasks crunched during such a long outage.

---

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

A proud member of the OFA (Old Farts Association)

sometimes I find it tricky to trigger the double resend I will give it a go

I set 178 tasks free by abandoning them

---

Forums have gone in to super slow motion mode, and the project is no longer issuing work (again), as of about 20min ago.
27/12/2018 14:15:08 | SETI@home | Scheduler request completed: got 0 new tasks

---

Grant
Darwin NT

Forums have gone in to super slow motion mode, and the project is no longer issuing work (again), as of about 20min ago.
27/12/2018 14:15:08 | SETI@home | Scheduler request completed: got 0 new tasks

yup. This isn't a good recovery. Hoping things will fix themselves, but worried we might need to send out the Seti signal. It is 9pm in CA. Not sure if that is too late.

And now it appears to be functioning again.

---

Grant
Darwin NT

sometimes I find it tricky to trigger the double resend I will give it a go

I set 178 tasks free by abandoning them

. . Abandoning or aborting? I know how to abort tasks but not how to abandon a task.

Stephen

??

sometimes I find it tricky to trigger the double resend I will give it a go

I set 178 tasks free by abandoning them

. . Abandoning or aborting? I know how to abort tasks but not how to abandon a task.

Stephen

??

All the tasks were ghosts so I detached from the project and reattached which caused the ghost tasks to error out. Here is an example http://setiathome.berkeley.edu/result.php?resultid=7268578562

---

All the tasks were ghosts so I detached from the project and reattached which caused the ghost tasks to error out.

Why?
The same thing would have occurred when they reached their due dates.

---

Grant
Darwin NT

All the tasks were ghosts so I detached from the project and reattached which caused the ghost tasks to error out.

Why?
The same thing would have occurred when they reached their due dates.

I was just trying to help the database not be so bloated and not making wing people having to wait till next year for credit. Just trying to be an all round good person

---

Did I miss another hiccup again?

Cheers.

Did I miss another hiccup again?

Yep.

---

Grant
Darwin NT

I was just trying to help the database not be so bloated and not making wing people having to wait till next year for credit. Just trying to be an all round good person

A couple of hundred tasks out of 5million or so isn't too much of an issue.
If it's something that keeps occurring you'd want to look in to it, but for a one off thing? Not worth worrying about IMHO.

---

Grant
Darwin NT

All the tasks were ghosts so I detached from the project and reattached which caused the ghost tasks to error out.

Why?
The same thing would have occurred when they reached their due dates.

. . So the tasks do NOT sit in limbo for 2 months and cause his wingmen undue delays ...

Stephen

? ?

I thought it was a good idea Speedy. I know when I got ghosts I did what I could so my wingman wouldn't have to wait forever, and so they would clear the db sooner. The system has been having enough hiccups lately as it is, I would think every little bit would help.

To stay on topic: I will note that I think the creation rate it is a bit low. It might meet demand, or might slowly dwindle, but it needs a kick in the pants to build the RTS up to normal.

Almost have all tasks reported, still about 500 to go on my last unreported host. Still getting nothing on all requests.

. . I found that when I was having trouble reporting I set my caches very low so they would not request work, all the rigs then reported AOK. I noticed this because I had already set the Linux caches low as they had sufficient tasks and they were reporting just fine but the Windows boxes were not. So I set the windows boxes to minimum and then they were able to report we well.

. . But like you, despite the fact that the RTS is overflowing there are still "no tasks available"

Stephen

:(

Did I miss another hiccup again?
Cheers.

It's almost like you're shutting the system down when you go to bed ....

---

I wonder if they set the RTS cache to 100k to see if less stress in the files system would help the server performance.
It sure seems that way to my eye.

---

I wonder if they set the RTS cache to 100k to see if less stress in the files system would help the server performance.
It sure seems that way to my eye.

I was kinda wondering the same thing. Usually by this time the day after the weekly maint, the RTS cache is back to normal of around 500k.

---

~Chris

Did I miss another hiccup again?
Cheers.

It's almost like you're shutting the system down when you go to bed ....

. . Here I have the opposite issue
, this machine 'shuts itself down' during the day when the heat gets too much to bear ...

Stephen

:(