Things are looking better. I went to sleep last night right after I started getting the Project is Down message. This morning the caches were Empty and No tasks were being sent.

Just Now, I'm starting to get New Work.

Oh well,
A couple of machine got a few dozen tasks, then nothing since.
Now they are out again, and are receiving;

Sat Mar 31 06:29:48 2018 | SETI@home | Sending scheduler request: To report completed tasks.
Sat Mar 31 06:29:48 2018 | SETI@home | Reporting 6 completed tasks
Sat Mar 31 06:29:48 2018 | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
Sat Mar 31 06:29:48 2018 | SETI@home | [sched_op] CPU work request: 166313.25 seconds; 0.00 devices
Sat Mar 31 06:29:48 2018 | SETI@home | [sched_op] NVIDIA GPU work request: 281457.27 seconds; 0.00 devices
Sat Mar 31 06:29:50 2018 | SETI@home | Scheduler request completed: got 0 new tasks
Sat Mar 31 06:29:50 2018 | SETI@home | Project has no tasks available

blah...

Just Now, I'm starting to get New Work.

You must be one of the very few.
I haven't picked up any work for hours, V8 In-progress numbers continue to decline. Eric posted in the News thread, more database issues.

---

Grant
Darwin NT

I haven't picked up any work for hours, V8 In-progress numbers continue to decline. Eric posted in the News thread, more database issues.

The crunching den is so quiet, can't even hear the fans, CPU at 32C Gpus 30-34C, running out of gas.
All requests for UL/DL from my side ends on:

Sat 31 Mar 2018 06:23:19 AM EST | SETI@home | Scheduler request failed: HTTP internal server error

---

Uploads seem to be working fine here.
But work requests result in no joy.

---

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

Sat 31 Mar 2018 06:43:47 AM EST | SETI@home | update requested by user
Sat 31 Mar 2018 06:43:52 AM EST | SETI@home | Sending scheduler request: Requested by user.
Sat 31 Mar 2018 06:43:52 AM EST | SETI@home | Reporting 67 completed tasks
Sat 31 Mar 2018 06:43:52 AM EST | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
Sat 31 Mar 2018 06:44:35 AM EST | SETI@home | Scheduler request failed: HTTP internal server error

Interesting: Why you can UL and I no?
Could be related to the Boinc version we use?
Pause for some coffee & aspirins.

---

Sat 31 Mar 2018 06:43:47 AM EST | SETI@home | update requested by user
Sat 31 Mar 2018 06:43:52 AM EST | SETI@home | Sending scheduler request: Requested by user.
Sat 31 Mar 2018 06:43:52 AM EST | SETI@home | Reporting 67 completed tasks
Sat 31 Mar 2018 06:43:52 AM EST | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
Sat 31 Mar 2018 06:44:35 AM EST | SETI@home | Scheduler request failed: HTTP internal server error

Interesting: Why you can UL and I no?

That is not an upload. That is a reporting/work request.
The 67 WUs it is trying to report have already been uploaded.

---

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

Could be a long day tomorrow..

Sat 31 Mar 2018 06:43:47 AM EST | SETI@home | update requested by user
Sat 31 Mar 2018 06:43:52 AM EST | SETI@home | Sending scheduler request: Requested by user.
Sat 31 Mar 2018 06:43:52 AM EST | SETI@home | Reporting 67 completed tasks
Sat 31 Mar 2018 06:43:52 AM EST | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
Sat 31 Mar 2018 06:44:35 AM EST | SETI@home | Scheduler request failed: HTTP internal server error

Interesting: Why you can UL and I no?

That is not an upload. That is a reporting/work request.
The 67 WUs it is trying to report have already been uploaded.

As we discussed in this thread a couple pf days ago, a large report (and 67 tasks is large, in this context) may be triggering the internal server error. Check out the posts from the people who accepted the advice to make the reports smaller.

As we discussed in this thread a couple pf days ago, a large report (and 67 tasks is large, in this context) may be triggering the internal server error. Check out the posts from the people who accepted the advice to make the reports smaller.

Sat 31 Mar 2018 07:04:31 AM EST | SETI@home | Sending scheduler request: Requested by user.
Sat 31 Mar 2018 07:04:31 AM EST | SETI@home | Reporting 32 completed tasks
Sat 31 Mar 2018 07:04:31 AM EST | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
Sat 31 Mar 2018 07:05:15 AM EST | SETI@home | Scheduler request failed: HTTP internal server error

Down to 32 and the answer is the same. The question could be: What the number of WU to report who is not large?

---

Just keep reducing it until it works.
Try 10.

---

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

Just keep reducing it until it works.
Try 10.

Will try but normaly my host has more than 10WU to report.
<edit> Down to 8 and no joy, the same error.
Will shutdown the host until Seti recovers, at least i save power.

---

Just keep reducing it until it works.
Try 10.

Will try but normaly my host has more than 10WU to report.

Well, this is only temporary. Things are not working normally right now.

---

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

Well, this is only temporary. Things are not working normally right now.

Down to 2 and not even works.
Was you able to report your work or you get the same error? To see if the Boinc version makes difference.

---

Well, this is only temporary. Things are not working normally right now.

Down to 2 and not even works.
Was you able to report your work or you get the same error? To see if the Boinc version makes difference.

It should not. But I am reporting 5 or 6 at a time and it is working. Just getting no new work back in return.

---

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

Well, this is only temporary. Things are not working normally right now.

Down to 2 and not even works.
Was you able to report your work or you get the same error? To see if the Boinc version makes difference.

No Problems with this Ubuntu machine Reporting work. If you look at it, it received a New task as recent as 31 Mar 2018, 11:54:07 UTC.
It reported it as completed 5 minutes later, all perfectly normal. It just can't get enough to matter, <core_client_version>7.4.44</core_client_version>

Eric mentioned he may have to rebuild an index that is used for task requests, if the reboots didn't work. My cache is down 50% so I'm guessing he will have to rebuild the index. That will mean downtime for our machines - so get those backup projects ready or save a little electricity :-)

Over a million work units ready to send, so when everything is said and done, we should be able to fill our caches quickly enough.

---

~Chris

Down to 2 and not even works.

♫♫ One is the loneliest number that you'll ever do ♫♫

31/03/2018 15:54:02 | SETI@home | Sending scheduler request: To report completed tasks.
31/03/2018 15:54:02 | SETI@home | Reporting 1 completed tasks
31/03/2018 15:54:02 | SETI@home | Not requesting tasks: don't need (CPU: ; AMD/ATI GPU: job cache full)
31/03/2018 15:54:07 | SETI@home | Scheduler request completed
31/03/2018 15:54:07 | SETI@home | Project requested delay of 303 seconds

31/03/2018 16:01:03 | SETI@home | Sending scheduler request: To report completed tasks.
31/03/2018 16:01:03 | SETI@home | Reporting 1 completed tasks
31/03/2018 16:01:03 | SETI@home | Not requesting tasks: don't need (CPU: ; AMD/ATI GPU: job cache full)
31/03/2018 16:01:07 | SETI@home | Scheduler request completed

:)

---

Much better:

SETI@home 2018-03-31 16:09:32 Reporting 2 completed tasks
SETI@home 2018-03-31 16:09:32 Requesting new tasks for NVIDIA GPU
SETI@home 2018-03-31 16:09:38 Scheduler request completed: got 34 new tasks

Well, 'tain't happnin' on a regular basis yet, for shore. Lucky you be.

---

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

I got 12 GPU tasks an hour ago, but NO CPU tasks.

---

Ops! Just get the #1 WU since yesterday!

---