Warning: number_format() expects parameter 1 to be double, string given in /disks/carolyn/b/home/boincadm/projects/sah/html/seti_boinc_html/sah_status.php on line 604 Warning: number_format() expects parameter 1 to be double, string given in /disks/carolyn/b/home/boincadm/projects/sah/html/seti_boinc_html/sah_status.php on line 608

Now getting Scheduler request failures.

---

Grant
Darwin NT

Now getting Scheduler request failures.

+1
...

---

SSP now shows:

Workunits waiting for assimilation 0 0 54 15m
Workunits waiting for db purging 0 7,380 22,669,039 15m
Results waiting for db purging 0 1 27,791,219 15m

From what I remember there were millions of units waiting for assimilation last night.
What happened ? Were they all processed over night or is the data on SSP incorrect ?

Tom

Scheduler's awake again, an there's work ready to go.
Unfortunately the Scheduler isn't actually sending anything out at present.

---

Grant
Darwin NT

Tom I'm not exactly sure what happened. From what I remember they got shifted back to waiting for administration. Hard to know I guess it's just a waiting game

---

SSP now shows:
Workunits waiting for assimilation 0 0 54 15m
Workunits waiting for db purging 0 7,380 22,669,039 15m
Results waiting for db purging 0 1 27,791,219 15m
From what I remember there were millions of units waiting for assimilation last night.
What happened ? Were they all processed over night or is the data on SSP incorrect ?
Tom

. . If you look now there are 22 million WUs waiting for purging and 27 million Tasks waiting to be purged. It seems that furball has been moved ...

. . Sorry that was what you were pointing out, there were too many numbers jumbled together ... :(

. . The missing WUs waiting for assimilation may be because they are part of the rise to 8.5 million tasks in the field.

Stephen

. . YAY! ... (?)

SSP now shows:

Workunits waiting for assimilation 0 0 54 15m
Workunits waiting for db purging 0 7,380 22,669,039 15m
Results waiting for db purging 0 1 27,791,219 15m

From what I remember there were millions of units waiting for assimilation last night.
What happened ? Were they all processed over night or is the data on SSP incorrect ?

Most likely another glitch.
After the last system outage the numbers were all messed up for an hour or two before returning to their previous excessive values.

---

Grant
Darwin NT

. . If you look now there are 22 million WUs waiting for purging and 27 million Tasks waiting to be purged. It seems that furball has been moved ...

And all the Ready-to-send numbers went along with them.

---

Grant
Darwin NT

SSP now shows:

Workunits waiting for assimilation 0 0 54 15m
Workunits waiting for db purging 0 7,380 22,669,039 15m
Results waiting for db purging 0 1 27,791,219 15m

From what I remember there were millions of units waiting for assimilation last night.
What happened ? Were they all processed over night or is the data on SSP incorrect ?

Most likely another glitch.
After the last system outage the numbers were all messed up for an hour or two before returning to their previous excessive values.

Good guess: SSP now shows

Workunits waiting for assimilation 0 0 8,172,827 9m

Back to where we were before ...

Tom

And on the next refresh, it says that there are 4,882,659 Results ready to send. I think we have one (or possibly several) very confused servers. Hopefully they'll stop arguing amongst themselves as the day progresses.

it says that there are 4,882,659 Results ready to send.

You forgot to wash your eyes out with coffee again in these coronadays? RRtS is 0, has been since the last tape went through. RoitF is 4,880,027

it says that there are 4,882,659 Results ready to send.

You forgot to wash your eyes out with coffee again in these coronadays? RRtS is 0, has been since the last tape went through. RoitF is 4,880,027

Well, it was a copy'n'paste from the 08:10 show. Went back to 0 at 08:20. Like I said, confused.

MB ready to send fall to 0 and creation rate to 2/sec

---

it says that there are 4,882,659 Results ready to send.

You forgot to wash your eyes out with coffee again in these coronadays? RRtS is 0, has been since the last tape went through. RoitF is 4,880,027

Well, it was a copy'n'paste from the 08:10 show. Went back to 0 at 08:20. Like I said, confused.

This is what happened the other day when they switched the pages to the replica DB. In fact, it looks like exactly the same data being displayed on my data when that happened. High readings on the astropulse valid tasks. Probably a remnent of that data.

I would say I must have some ghosts. The website says I have 640 waiting to be processed.

I only have one system (my Windows 10 box) that is still processing.
And it is processing GPU tasks only.
The tasks are taking up to 40+ minutes per task so it is taking a long time to get through the cache.

Tom M

---

A proud member of the OFA (Old Farts Association).

At least it was a good time to change BOINC over onto a new webserver, which promptly went offline.
Good thing I read that David asked to report any problems. I think the server being AWOL since about 10am LT counts like such. :P

I would say I must have some ghosts. The website says I have 640 waiting to be processed.

I only have one system (my Windows 10 box) that is still processing.
And it is processing GPU tasks only.
The tasks are taking up to 40+ minutes per task so it is taking a long time to get through the cache.

Tom M

the website is 3-4 days out of date due to the replica delay. it's been this way for a long time. anything you see on the website reflects what your system was doing several days ago.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

it says that there are 4,882,659 Results ready to send.

You forgot to wash your eyes out with coffee again in these coronadays? RRtS is 0, has been since the last tape went through. RoitF is 4,880,027

. . The numbers have been flicking back and forth like a fan dancers fans ... very confusing ...

Stephen

:(

At least it was a good time to change BOINC over onto a new webserver, which promptly went offline.
Good thing I read that David asked to report any problems. I think the server being AWOL since about 10am LT counts like such. :P

Isn't that David's usual modus operandi?

* no pre-warning
* do the business last thing at night
* post about what a cracking success it's been
* go to bed
* let the Europeans watch it fall over

?