Unless you need to check on a Host to make sure it is still returning valid work or see what kind of errored task you must have reported when the project says you have reached your daily quota of tasks.

---

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

A proud member of the OFA (Old Farts Association)

Well, at least we're getting new tasks. Viewing the hosts stats pages aren't that important.

. . We were for a while but over the last several hours I have only received about a half dozen jobs, compared to the hundreds I have uploaded, in a few hours I will be out of work ... again :(

Stephen

:(

Yes, web pages have been problematic for a while now...web page slow, account page even slower and status page not loading at all.
Was waiting for the other shoe to drop, and now it has. No tasks coming in.

---

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

I don't think I've yet had any reason to wish that I hadn't suggested this very thing, back in September. I also suggested that upgrades and preparatory work could also be done......and still think it is a sensible and prudent course to take.

---

Don't take life too seriously, as you'll never come out of it alive!

Uploads are starting to backup here now.

Cheers.

I've been having upload problems for about an hour. Some took 4 attempts to finally clear, but now, the message about 'project backoff' has appeared against 7 WUs that were trying to upload. Oh well.....looks like my power use is going to reduce tonight.

---

Don't take life too seriously, as you'll never come out of it alive!

Uploads are starting to backup here now.

Cheers.

. . Well we know things are bad when they start to affect Wiggo :)

Stephen

:)

I'm happy now that Wiggo gets to join in the misery. LOL ;-{

---

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

A proud member of the OFA (Old Farts Association)

Yep

---

Caches are now full, I eagerly await the outrage.

---

Are AstroPulse work units having problems getting validated? See AstroPulse work unit 2916316164 which as of this writing had both results turned in on March 28, 2018, but still has not been validated as of April 3, 2018 on 4:29 UTC.

Dam, I was finally getting work for about an hour after I finally cleared all the stalled uploads. Then started getting the dreaded no work is available messages. Now its gone back to internal server error on connecting to the scheduler.

---

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

A proud member of the OFA (Old Farts Association)

Now its gone back to internal server error on connecting to the scheduler.

Haven't seen any of those since the earlier outage & recovery. Lately it's just been the random allocation of work; 5-15 requests before getting any.

And without any fresh Arecibo work we can look forward to our RAC taking a dive again (in addition to the drop from running out of work due to the Seti server system glitches).

---

Grant
Darwin NT

After going for a few drinks all was back to normal again, the power of beer triumphs again. :-D

Cheers.

I didn't see anything reflecting the old glitch in the Haveland graphs, but the symptoms appeared very similar to what we had in the past. There was an hour or so where you either got the no tasks are available message or the internal server error message. Effect was the usual drop in caches. But after an hour or so and down to my last dozen or so tasks, the machines started connecting again and began to rebuild the caches. Back to full again after several hours.

---

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

A proud member of the OFA (Old Farts Association)

Here's to hoping that their DB reorganization does the trick!
Meow!

---

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

Here's to hoping that their DB reorganization does the trick!
Meow!

Indeed.

They're struggling a bit under the onslaught just at the moment, but that's only to be expected. Large chunks of my completed work have been reported, but some are bouncing off at the 'connect' stage (that's server loading, nothing to do with the database). It'll be many more hours before the active database tables are cached from disk, and we start to see the true performance - for good or ill.

Here's to hoping that their DB reorganization does the trick!
Meow!

Indeed.

They're struggling a bit under the onslaught just at the moment, but that's only to be expected. Large chunks of my completed work have been reported, but some are bouncing off at the 'connect' stage (that's server loading, nothing to do with the database). It'll be many more hours before the active database tables are cached from disk, and we start to see the true performance - for good or ill.

I left my setting to report only 50 completed tasks at a time, and so far reporting is going well.
When one can connect, at least.

---

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

Here's to hoping that their DB reorganization does the trick!
Meow!

Indeed.

They're struggling a bit under the onslaught just at the moment, but that's only to be expected. Large chunks of my completed work have been reported, but some are bouncing off at the 'connect' stage (that's server loading, nothing to do with the database). It'll be many more hours before the active database tables are cached from disk, and we start to see the true performance - for good or ill.

. . I guess that explains the http error

. . Where was that report number setting again ??

Stephen

:(

Here's to hoping that their DB reorganization does the trick!
Meow!

Indeed.

They're struggling a bit under the onslaught just at the moment, but that's only to be expected. Large chunks of my completed work have been reported, but some are bouncing off at the 'connect' stage (that's server loading, nothing to do with the database). It'll be many more hours before the active database tables are cached from disk, and we start to see the true performance - for good or ill.

. . I guess that explains the http error

. . Where was that report number setting again ??

Stephen

:(

cc_config.xml in your Boinc data directory.
<max_tasks_reported>50</max_tasks_reported>

I have not gotten any HTTP errors at 50 so far.

---

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