Look at the 'Application' column in BOINC Manager, advanced view. If it starts with the word 'Local:', BOINC is using Anonymous Platform. If the word 'Local:' is missing, it's running stock.

Yep, not local. I can probably keep it running as is until Anonymous Platform is fixed, but the tasks missing from task page is concerning. It's possible the WU's are getting thrown out anyway. It's winter and I need the heat so it's probably OK. :-)

The task page is not up to date due the server is some 40.000 secs behind, so what you see is the status for 40.000 secs ago.

And it's just getting worse, yesterday it was some 17.000 secs behind.

The task page is not up to date due the server is some 40.000 secs behind, so what you see is the status for 40.000 secs ago.

And it's just getting worse, yesterday it was some 17.000 secs behind.

The task page is updated from the Replica, which as of now is 43961 seconds behind (more than 12 hours)
No worry about that, your downloaded tasks does exist, you just can't see them on the task pages.

Edit: JohnDK beat me to it.

Ah, thanks. It makes sense that these non-critical stats are from querying replica. It just means I need to check on hosts directly for now, which I am kinda already doing anyway...

---

Anonymous Platform here.
Scheduler requests take 40sec up to a timeout & result in
22/12/2019 04:43:47 | SETI@home | Scheduler request failed: Failure when receiving data from the peer
22/12/2019 05:35:29 | SETI@home | Scheduler request failed: Couldn't connect to server
22/12/2019 06:25:27 | SETI@home | Scheduler request failed: HTTP service unavailable
22/12/2019 06:32:28 | SETI@home | Scheduler request failed: HTTP internal server error

Once or twice I have got a valid response (taking almost 2 min, usual response time 3 sec) which results in a "Project has no tasks available" response.


Edit- both systems have all work completed & reported, they're just trying for new work.

Interestingly, my Windows system is still getting mostly Scheduler errors (30sec to 3min wait for a response), my Linux system is getting "Project has no tasks available" responses (30-50sec response time).

---

Grant
Darwin NT

Greetings,

Ok, now I'm running stock again. I got cuda60 and sah WUs. This, on my main. My other Linux PC still has almost 16 hours of crunching to do before I work with it.

Instead of archiving my anonymous SETI directory, I just renamed it before restarting BOINC and resetting the project. Works for me. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

I was just sent two more groups of "Lost" tasks, I think that was all of them. So it appears 'Resend Lost Tasks' is turned on by default just as it was on BETA. Hopefully it will help cut down on Database bloat.
I also found you can download tasks while running Stock with 'Suspend GPU' set, that helps when the Server insists on sending you Apps that crash 5 seconds after they start. Once you have a few hundred tasks you can 'reschedule' the crashing tasks to an App that doesn't crash....such as CUDA90.

One observation, when we ask for new work it returns: Sat 21 Dec 2019 05:39:10 PM EST | SETI@home | Scheduler request failed: HTTP internal server error

Maybe somebody forget to update the address of the server on the task started when the anonymous host ask for new work...

---

So it appears 'Resend Lost Tasks' is turned on by default just as it was on BETA.

That probably accounts for the database sluggishness, all by itself - it was implicated in the November 2013 database event. That CAN'T have been deliberate, surely? Have you told Eric yet?

I haven't had any reply from Eric yet, but I won't pester him - but I will pass on what we know by the beginning of tomorrow's Berkeley daylight.

One observation, when we ask for new work it returns: Sat 21 Dec 2019 05:39:10 PM EST | SETI@home | Scheduler request failed: HTTP internal server error

Maybe somebody forget to update the address of the server on the task started when the anonymous host ask for new work...

This is, I think, further evidence that something went very wrong in the disconnection noted in News and we're actually connecting to the Beta scheduler.

---

One observation, when we ask for new work it returns: Sat 21 Dec 2019 05:39:10 PM EST | SETI@home | Scheduler request failed: HTTP internal server error

Maybe somebody forget to update the address of the server on the task started when the anonymous host ask for new work...

It's been doing that at intervals all day - among all the other grotty responses it's capable of sending out. I don't think it's anything to do with a bad address - it just uses up all the available time or memory and then crashes. Possibly because of all the extra work and database querying it's trying to do for a 'lost tasks' check.

It would seem to me that the current problems might be related to Eric's "BOINC Notice" he posted yesterday:

_____________________________________________________________________________________________________________________________
SETI@home: Some server issues today...
It's the Friday before a holiday week and the servers know it.

The file system containing the beta project uploads directory is having problems, so beta is down until further notice.

This problem may be affecting the rate at which the main project can handle results, so the validation and assimilation queues are getting large, which may affect the rate of work generation.
12/20/2019 17:10:04
_____________________________________________________________________________________________________________________________

I'm sure they're related, but I'm not exactly sure how, yet.

I thought they might have upgraded the server software in a misguided attempt to rectify the database problems. Now I'm not so sure. Recent posts have suggested that they might simply have got the wires crossed (well, not quite as simple as that ...) and set the Beta server up to process the Main project - but with the Beta settings still in place. Too soon to tell, until we set some feedback from inside the project. Our scheduler here is still running on Synergy, though - what was Beta's scheduler running on?

Have you told Eric yet? I haven't had any reply from Eric yet, but I won't pester him - but I will pass on what we know by the beginning of tomorrow's Berkeley daylight.

I told him about it a couple months ago, back when I was running Apps on BETA. I dunno, maybe remind him...

Have you told Eric yet? I haven't had any reply from Eric yet, but I won't pester him - but I will pass on what we know by the beginning of tomorrow's Berkeley daylight.

I told him about it a couple months ago, back when I was running Apps on BETA. I dunno, maybe remind him...

I was asking about the new observation about Resend Lost Tasks being active on Main - that's nearer two hours ago than two months ago!

Don't worry about it - Mr. Kevvy has passed the new information on. And I'm going to bed.

It certainly doesn't like Anonymous Platform.

On my WIndows system I exited BOINC, backed up my Seti project folder, removed app_info.xml and restarted BOINC. First couple of Scheduler requests failed, then got work.
22/12/2019 09:09:52 | SETI@home | Scheduler request failed: Failure when receiving data from the peer
22/12/2019 09:14:37 | SETI@home | Scheduler request failed: Couldn't connect to server
22/12/2019 09:15:58 | SETI@home | Scheduler request completed: got 68 new tasks
22/12/2019 09:21:25 | SETI@home | Scheduler request failed: Couldn't connect to server
22/12/2019 09:23:26 | SETI@home | Scheduler request completed: got 20 new tasks

With anonymous platform, any successful Scheduler request results in "Project has no tasks available", and there were very, very, very few successful requests.


Edit- and even running stock, successful Scheduler requests are in the minority.
So far 9 failures, 4 successful (3 successful and getting work in a sequence of 4 requests), and one "project has no tasks available response."

It is very, very broken.

---

Grant
Darwin NT

I'm looking into the problem. Grrrrr.....

---

@SETIEric@qoto.org (Mastodon)

I'm looking into the problem. Grrrrr.....

---

We are doing all we can do to help solve the problem.
https://boinc.berkeley.edu/dev/forum_thread.php?id=8105&postid=94433
https://boinc.berkeley.edu/dev/forum_thread.php?id=8105&postid=94439
Howling at the moon and seting our hair on fire often helps.

---

Well, running stock isn't helping that much.
So far I've picked up a dozen CUDA50 WUs, I did get 100 SoG WUs, but the downloads errored out for some reason. And I've picked up around 300 CUDA42 WUs, which take 30min to process (instead of the 9min or less with SoG).

I'll give it a while longer & see if i can get some SoG work that downloads OK, otherwise I might as well just set it for No New Tasks and wait till it's fixed.

---

Grant
Darwin NT

We are doing all we can do to help solve the problem.
https://boinc.berkeley.edu/dev/forum_thread.php?id=8105&postid=94433
https://boinc.berkeley.edu/dev/forum_thread.php?id=8105&postid=94439
Howling at the moon and seting our hair on fire often helps.

I'm out of hair, but I can still drink.

---

Juan maybe is waiting for you to arrive.

---