Works just fine here.

You win the lotto! Still nothing here. Even if i reduce the number of reported WU to 16.

---

Works just fine here.

You win the lotto! Still nothing here. Even if i reduce the number of reported WU to 16.

Hehe, I edited out "Works just fine here", after I realized that it didn't really work fine at all :-)

Just get the first completed scheduler request now. Still no new WU but that will take a while.

Wed 28 Mar 2018 10:55:52 AM EST | SETI@home | Scheduler request completed: got 0 new tasks
Wed 28 Mar 2018 10:55:52 AM EST | SETI@home | Project has no tasks available

---

I finally got everything reported and started catching a very few loose splatters from the splitters.

---

I'm not an "anarchist", but is this project about done, lacking any leadership and having lost any partner respect. The web pages are dated or wrong and are almost never updated. The statistics are at best delayed and unkempt but generally seem untrustworthy. For example, what's with the 71 V7 results waiting to be purged (for many months). Weekly downtimes are typically well in excess of the handful of hours advertised on the project page, which hasn't changed its wording in years I think. There is almost no interaction with, or education of the partner network on anything. For example, today there hasn't been a post on the "News" board for 19 days. Looking at the number of complaints posted on the bulletin board, those related to seti management seem to be rising. Is anybody home? Are they changing something to try to be "better"? Improved server software architecture? Client software? Metrics? I've been turned off for awhile and have added a second backup project. I did so in part to find a project that appreciates the meager resources I can offer: just a desktop or two with no GPU's. But I find that backup project is becoming the main project and have reversed its role with SETI.

Please Administrators, don't this venerable project fall apart unless that is a reasoned decision, not based on lack of continued enthusiasm.

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

Keep reducing the number reported until you can start whittling down the backlog.

Last time I suggested this, I reported that batches of 150 and 191 had failed, batches of 64 were getting through. Much the same happened today.

Take a look at the size of sched_request_setiathome.berkeley.edu.xml (in your BOINC sata directory). Again from last time, 2.4 MB failed, 845 KB succeeded. See if you can get yours below 1 MB.

The status page got a good update. Looks like someone is working on the problems.

Truthfully I'd like all hands on fixing the problem instead of informational updates. Isn't like you can predict when the system will be up and working again anyway.

OK, getting new tasks now:

SETI@home 2018-03-28 18:16:05 Requesting new tasks for NVIDIA GPU and Intel GPU
SETI@home 2018-03-28 18:16:11 Scheduler request completed: got 50 new tasks

Same here, trick is now to actually download them!!

There's an issue with the splitters: the governor hasn't kicked in, so there's over 1 .2 million WU's available; and, when I first looked, the splitters were still going at 59 WU produced per second! (they've backed down to 8/sec, on a second look)... (Normally [unless they've quite recently changed something] the governor kicks in at around .5 million...) This may have something to do with why people are getting the dreaded "Project has no tasks available", as the "next to send " queue has only 400 slots (IIRC) available - and may not be filling them when empty, due to the excessive I/O of the splitters on the database.

---

.

Hello, from Albany, CA!...

The server cache is 600k, when it is overfull (like now) it is because of all the resends the system has identified and inserted in.

Results ready to send	0	3,713	1,109,512

We could only especulate but 1 MM???
All the 0 (zero) Tapes done, maybe another source of the problems.
I have > 100 WU ready to DL but they not sttart. HTTP error....
Time to go for something cool to refresh myself is at 32C and rising here.

---

trick is now to actually download them!!

I can't connect to 119, getting nothing but header errors from 127. Gonna be a long night.

I got maybe 30 tasks downloaded before I started having download issues

I'm not an "anarchist", but is this project about done, lacking any leadership and having lost any partner respect. The web pages are dated or wrong and are almost never updated. The statistics are at best delayed and unkempt but generally seem untrustworthy. For example, what's with the 71 V7 results waiting to be purged (for many months). Weekly downtimes are typically well in excess of the handful of hours advertised on the project page, which hasn't changed its wording in years I think. There is almost no interaction with, or education of the partner network on anything. For example, today there hasn't been a post on the "News" board for 19 days. Looking at the number of complaints posted on the bulletin board, those related to seti management seem to be rising. Is anybody home? Are they changing something to try to be "better"? Improved server software architecture? Client software? Metrics? I've been turned off for awhile and have added a second backup project. I did so in part to find a project that appreciates the meager resources I can offer: just a desktop or two with no GPU's. But I find that backup project is becoming the main project and have reversed its role with SETI.

Please Administrators, don't this venerable project fall apart unless that is a reasoned decision, not based on lack of continued enthusiasm.

There's a difference between the site science and project pages not being updated and the BOINC server backend being updated. As far as I'm concerned the latter is the important part and the admins are updating that. There are many, many BOINC projects that are not on the BOINC site version that moved the links to the top/username on the right. Many still have the 'Main page · Your account · Message boards' links at the bottom.

There's a difference between the site science and project pages not being updated and the BOINC server backend being updated. As far as I'm concerned the latter is the important part and the admins are updating that. There are many, many BOINC projects that are not on the BOINC site version that moved the links to the top/username on the right. Many still have the 'Main page · Your account · Message boards' links at the bottom.

And I suspect that maybe why we had a 24 hour outage, since there was some changes to server side code that may have broken something, and since S@H is the guinea pig of untested BOINC code.........

Keep reducing the number reported until you can start whittling down the backlog.

Last time I suggested this, I reported that batches of 150 and 191 had failed, batches of 64 were getting through. Much the same happened today.

Take a look at the size of sched_request_setiathome.berkeley.edu.xml (in your BOINC sata directory). Again from last time, 2.4 MB failed, 845 KB succeeded. See if you can get yours below 1 MB.

Thanks Richard. It worked. After getting 50 to upload each time it went into No Task Available.

It has finally gotten up to being near full cache with not having to babysit the dowload process.

---

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

Yes, all looking like it's got up to speed now - both work assignment and downloads. I'm starting to wind down the backup projects and set normal running caches. Then some beer to celebrate.

There's a difference between the site science and project pages not being updated and the BOINC server backend being updated. As far as I'm concerned the latter is the important part and the admins are updating that. There are many, many BOINC projects that are not on the BOINC site version that moved the links to the top/username on the right. Many still have the 'Main page · Your account · Message boards' links at the bottom.

And I suspect that maybe why we had a 24 hour outage, since there was some changes to server side code that may have broken something, and since S@H is the guinea pig of untested BOINC code.........

We'd have to wait for an admin to say why it was down extra long.

There is a SETI Beta project where BOINC server versions are tested before moving to SETI proper.

Keep getting "transient HTTP error" when my machines try to download work.
The "Backing off" time keeps getting longer.
I'll just wait for the issues to subside, eventually I'll get them downloaded.

---

Keep getting "transient HTTP error" when my machines try to download work.
The "Backing off" time keeps getting longer.
I'll just wait for the issues to subside, eventually I'll get them downloaded.

I suggest you read more from the recent posts to this thread.

---

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

Keep getting "transient HTTP error" when my machines try to download work.
The "Backing off" time keeps getting longer.
I'll just wait for the issues to subside, eventually I'll get them downloaded.

I suggest you read more from the recent posts to this thread.

My problem isn't reporting, it's downloading work.
I guess I could set <http_debug>, but that only gives me more verbose errors?

---