If you can use rrd here it is:
https://transfer.kiska.pw/n2FN6/setiathomev8_creation-creation-g.rrd

That rrd file doesn't contain the 'pure' original values but instead averages of more than one value so it is (nearly) impossible to determine the original values to the last decimal position :(

It does contain what I get off the SSP xml.

Like I've ran:

root@vultr:~# rrdtool lastupdate /var/lib/munin/Munin-Node/Munin-Node-results_setiathomev8_creation-creation-g.rrd | sed ':a;N;$!ba;s/.*: \([0-9]*\)/\1/g'
6.6856

Which is consistent with the value seen in SSP at 22:10 UTC

Here is my configuration for munin

    print "multigraph results_setiathomev8_creation\n";
    print "graph_title setiathome sahv8 Creation Rate\n";
    print "graph_order creation\n";
    print "graph_args --base 1000\n";
    print "graph_vlabel Creation rate per second\n";
    print "update_rate 240\n";
    print "graph_category setiathome\n";
    print "graph_info This graph shows result statistics for setiathome sahv8\n";
    print "creation.info This shows the creation rate for setiathomev8\n";
    print "creation.label creation\n";
    print "creation.type GAUGE\n";

Also i dont know if this matters, but since the problem started,
i did remove my app_info.xml

Put it back, you'll need it. app_info isn't provided by the S@H website; it was created by the Lunatics installer you presumably ran. You'll need it to get the right apps running, or leave it off and the website will give you "stock" apps.

Best to wait a day or two. There is a new installer almost ready to launch, but I'm waiting until things settle down a bit to finalise testing.

Unlikely as getting work has still been near impossible much of the time, even when there was some work to get.

And I doubt that things will improve while all these blc35 noise bombs are being spewed out. :-(

Cheers.

+1

Looks like the splitters have been enabled again. I got some work on a host. Looks like 44 tasks.

. . Nothing here :(

Stephen

:(

If you can use rrd here it is:
https://transfer.kiska.pw/n2FN6/setiathomev8_creation-creation-g.rrd

I couldn't get exact match because of the averaged noise in the data but the window size that matched the most samples was 299 seconds. Multiples of 299 matched a little bit more but so little that it was just by chance. 149.5 (half of 299) matched about half the number of samples compared to 299 and quarter of 299 about quarter the number of samples. These
are the expected results if 299 is the true value.

. . Try 303 ...

Stephen

. .

Which is consistent with the value seen in SSP at 22:10 UTC

Thats a single sample. About half of all the unique sample values in the data I downloaded fitted in the four decimal format. The rest were a lot longer. Some of them obvious averages of a few samples with decimals after 4th all being 3s etc.

How often and at what times are you scraping the data? The rrd has 5 minute time resolution so if you sample more frequenty, it'll probably average the samples. Or if your samples happen at different times than the rrd's regularily spaced 5 minute slots, then it might interpolate between two of your samples to get the value at the point of time it wants.

---

Which is consistent with the value seen in SSP at 22:10 UTC

Thats a single sample. About half of all the unique sample values in the data I downloaded fitted in the four decimal format. The rest were a lot longer. Some of them obvious averages of a few samples with decimals after 4th all being 3s etc.

How often and at what times are you scraping the data? The rrd has 5 minute time resolution so if you sample more frequenty, it'll probably average the samples. Or if your samples happen at different times than the rrd's regularily spaced 5 minute slots, then it might interpolate between two of your samples to get the value at the point of time it wants.

Its sampled once per 5 minutes which matches up with the 5 minute time resolution :D

And at what time... well it runs when it runs :D

EDIT: But it typically runs at :(x)0 and :(x)5
I don't monitor the server every second of my life, so that is probably a generalisation of when it runs

And at what time... well it runs when it runs :D

And there is your problem. From rrdtool manpage:

RRDtool lets you update the log file at
any time you want. It will automatically interpolate the value
of the data-source (DS) at the latest official time-slot
(interval) and write this interpolated value to the log.

Half of the values were correct because you update at twice the frequency the ssp updates, so you always get two identical samples and interpolating between identical values gives the original value.

---

I've been able to get a few tasks on the daily driver, but the majority are the BLC35 "noise bombs"

Thankfully, half a dozen are AP tasks and at least those will run for a while. Even have 3 cpu AP tasks good for a couple of hours.

---

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

A proud member of the OFA (Old Farts Association)

It could be my "Seti Toaster"

To win a SETI Toaster you need to crunch at least 1 Billion credits. LOL

. . I don't think my current toaster will last that long :(

Stephen

:)

I hope you have had time to collect them/those for a bad toaster day. It is a short resource.

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones

Fri 24 Jan 2020 07:18:54 PM CST | SETI@home | [sched_op] Server version 709
Fri 24 Jan 2020 07:18:54 PM CST | SETI@home | Project has no tasks available
Fri 24 Jan 2020 07:18:54 PM CST | SETI@home | Project requested delay of 303 seconds

---

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

The splitters have been turned off the great majority of the day and no work available has been the result. Whatever they did to reorganize the database has given them more issues to deal with other than just reducing the results out in the field or the size of the database.

Unless someone continues to work on the project this weekend, I fear the project won't get going anytime soon until Monday or Tuesday.

---

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

A proud member of the OFA (Old Farts Association)

The splitters have been turned off the great majority of the day and no work available has been the result. Whatever they did to reorganize the database has given them more issues to deal with other than just reducing the results out in the field or the size of the database.

Unless someone continues to work on the project this weekend, I fear the project won't get going anytime soon until Monday or Tuesday.

AP splitters are running and one MB splitter is running as of 5-10 ago.

Unless someone has an idea, I guess I will reset the project and lose the 150 completed work units.

I am still unable to report.

Since the project came back up:

I have 2 machines
1 finally recovered and is getting a trickle of work.
The other

1/24/2020 9:37:26 AM | SETI@home | Fetching scheduler list
1/24/2020 9:37:39 AM | | Project communication failed: attempting access to reference site
1/24/2020 9:37:40 AM | | Internet access OK - project servers may be temporarily down.

Have rebooted, etc.

Cannot even get it to report.

Any ideas ?

Dave

---

Dave

Unless someone has an idea, I guess I will reset the project and lose the 150 completed work units.

I am still unable to report.

Since the project came back up:

I have 2 machines
1 finally recovered and is getting a trickle of work.
The other

1/24/2020 9:37:26 AM | SETI@home | Fetching scheduler list
1/24/2020 9:37:39 AM | | Project communication failed: attempting access to reference site
1/24/2020 9:37:40 AM | | Internet access OK - project servers may be temporarily down.

Have rebooted, etc.

Cannot even get it to report.

Any ideas ?

Dave

Set No New Tasks in the Manager to report work.

---

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

A proud member of the OFA (Old Farts Association)

AP splitters are running and one MB splitter is running as of 5-10 ago.

I see the AP splitters running. No sign of any MB splitter running though.

---

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

A proud member of the OFA (Old Farts Association)

Unless someone has an idea, I guess I will reset the project and lose the 150 completed work units.

I am still unable to report.

Since the project came back up:

I have 2 machines
1 finally recovered and is getting a trickle of work.
The other

1/24/2020 9:37:26 AM | SETI@home | Fetching scheduler list
1/24/2020 9:37:39 AM | | Project communication failed: attempting access to reference site
1/24/2020 9:37:40 AM | | Internet access OK - project servers may be temporarily down.

Have rebooted, etc.

Cannot even get it to report.

Any ideas ?

Dave

Set No New Tasks in the Manager to report work.

Tried that hours ago, no luck.

---

Dave

Unless someone has an idea, I guess I will reset the project and lose the 150 completed work units.

I am still unable to report....

Sometimes I have to limit the number of tasks reported as well as setting NNT, but, I usually limit it to 240. Try limiting it to 50 and see if it helps.
Place it in the cc_config.xml file,
<max_tasks_reported>50</max_tasks_reported>

with all 5 pc i got. maybe i got 5 wu...... so atm for it not request over 1k worth of wu. i switch to prime grid.
k a update to a odd bug. if you get a astro pulse now it will run on both gpus at once. but only show up as running on one.

---

Unless someone has an idea, I guess I will reset the project and lose the 150 completed work units.

I am still unable to report....

Sometimes I have to limit the number of tasks reported as well as setting NNT, but, I usually limit it to 240. Try limiting it to 50 and see if it helps.
Place it in the cc_config.xml file,
<max_tasks_reported>50</max_tasks_reported>

Set as indicated. Still no luck.

Within seconds of requesting update, project goes to 24 Hour back-off.

---

Dave