Well, based on the number of Nbody WUs that are waiting to be sent, it looks like the WUs that need re-validation were kicked back to the surface! I'm going to let things run. If you wind up with problems getting work, please let me know and I will figure something out.

If we can just let this run then I think all those "stuck" WUs will finally be processed, although it will take a while for people to work through 11M of them...

Not sure if this is the right place, but I'm seeing "Server error: feeder not running" when trying to update. And the Server Status page is showing that as well. Is there some maintenance going on?

Can’t report anything….seems lots of systems stopped.

Not sure if this is the right place, but I'm seeing "Server error: feeder not running" when trying to update. And the Server Status page is showing that as well. Is there some maintenance going on?

I am running out of WUs :D thats bad.

But the likes of this is not my doing:

        <rec_half_life_days>10.000000</rec_half_life_days>
        <report_results_immediately>0</report_results_immediately>
        <run_apps_manually>0</run_apps_manually>
        <save_stats_days>30</save_stats_days>
        <skip_cpu_benchmarks>0</skip_cpu_benchmarks>
        <simple_gui_only>0</simple_gui_only>
        <start_delay>0.000000</start_delay>
        <stderr_head>0</stderr_head>
        <suppress_net_info>0</suppress_net_info>
        <unsigned_apps_ok>0</unsigned_apps_ok>
        <use_all_gpus>1</use_all_gpus>
        <use_certs>0</use_certs>
        <use_certs_only>0</use_certs_only>
        <vbox_window>0</vbox_window>

That is the standard cc_config.xml configuration settings. As I stated, when you change any one of the default logging options, the client will create a FULLY populated cc_config.xml file with the default settings.
These are the same ones operating even without a cc_config.xml file present. All you have done is expose them for your control now.

Some of the ones that you probably should change from default is the save stats parameter and extend it out to 180 days. Makes for clearer understanding of your RAC changes in the graphing of project RAC's
Another beneficial one is the rec half lifes setting and change that to 1 day vice the default 10 days. The makes projects and scheduler response more responsive to exaggerated production of one project against others so that the REC changes are more rapid in balancing resource shares of projects.

And of course the sched_op_debug I mentioned previously.

---

Server processes offline for maintenance again, I suppose. Haven't had work for half a day now.

---

If it helps, I last got work today, May 3rd, at 7:42 AM Central Daylight Time, and I first got the feeder not running error at 8:32 AM Central Daylight Time.

Well, based on the number of Nbody WUs that are waiting to be sent, it looks like the WUs that need re-validation were kicked back to the surface! I'm going to let things run.
If you wind up with problems getting work, please let me know and I will figure something out.
If we can just let this run then I think all those "stuck" WUs will finally be processed, although it will take a while for people to work through 11M of them...

Seems like a good time to leave the nbody_work_generator offline for a while till the 11M backlog gets crunched

Please restore the Separation work generator though.

---

But the likes of this is not my doing:

        <rec_half_life_days>10.000000</rec_half_life_days>
        <report_results_immediately>0</report_results_immediately>
        <run_apps_manually>0</run_apps_manually>
        <save_stats_days>30</save_stats_days>
        <skip_cpu_benchmarks>0</skip_cpu_benchmarks>
        <simple_gui_only>0</simple_gui_only>
        <start_delay>0.000000</start_delay>
        <stderr_head>0</stderr_head>
        <suppress_net_info>0</suppress_net_info>
        <unsigned_apps_ok>0</unsigned_apps_ok>
        <use_all_gpus>1</use_all_gpus>
        <use_certs>0</use_certs>
        <use_certs_only>0</use_certs_only>
        <vbox_window>0</vbox_window>

That is the standard cc_config.xml configuration settings. As I stated, when you change any one of the default logging options, the client will create a FULLY populated cc_config.xml file with the default settings.
These are the same ones operating even without a cc_config.xml file present. All you have done is expose them for your control now.

Some of the ones that you probably should change from default is the save stats parameter and extend it out to 180 days. Makes for clearer understanding of your RAC changes in the graphing of project RAC's
Another beneficial one is the rec half lifes setting and change that to 1 day vice the default 10 days. The makes projects and scheduler response more responsive to exaggerated production of one project against others so that the REC changes are more rapid in balancing resource shares of projects.

And of course the sched_op_debug I mentioned previously.

They may be there if I've installed from scratch the latest Boinc, or on quite a few machines I have used some debugging temporarily. But I turned that off after a while as it cluttered the messages tab.

I don't use the inbuilt graphs, I just refer to Boincstats webpage, I assume this setting won't affect his stats.

I did used to reduce the halflife. But currently I concentrate on only 1 or 2 projects at a time.

I have yet to see post rating that isn't zero.
Have they ever been used?

I have yet to see post rating that isn't zero.
Have they ever been used?

I asked about this before, somebody told me no they are ignored by most servers. Pretty daft it's sat there. The red X probably works considering how many bans I've had.

I have yet to see post rating that isn't zero.
Have they ever been used?

I asked about this before, somebody told me no they are ignored by most servers. Pretty daft it's sat there. The red X probably works considering how many bans I've had.

Yes the Red X works at most projects but not all of them and at some you have to be REALLY REALLY bad to get banned.

Yes the Red X works at most projects but not all of them and at some you have to be REALLY REALLY bad to get banned.

I've been banned for up to 2 months 38 times on the main Boinc forum, over 5 accounts. Sometimes they realise I'm the same person.

I've been banned permanently from WCG and somehow they recognise me on a new account, even though I change everything including browser and IP address. Maybe it's my arrogance?

Primegrid and loads of non-Boinc stuff I've been banned for all over the place, the smallest thing was for saying the word "damn" which is apparently very very bad for American religious loonies, of which the admin was one. I think all I said was "The Scottish wet weather is damn annoying".

This project down, WCG still down, it sucks.

BTW: I like people from Scotland, they are brave and honest but sometimes not politically correct - which is OK for me.

This project down, WCG still down, it sucks.

BTW: I like people from Scotland, they are brave and honest but sometimes not politically correct - which is OK for me.

And I like the Germans for reasons I won't get into here :-)

Well.... the up side is I'm saving money on my ever increasing power bill while I wait for Milkyway to come back online :) That's a silver lining if ever there was one.

---

Well.... the up side is I'm saving money on my ever increasing power bill while I wait for Milkyway to come back online :) That's a silver lining if ever there was one.

Mine is increasing until the point they get very angry and send the debt to a debt collection agency, which under Scottish law can get virtually nothing. My 70 grand credit card debts will be paid off in 400 years.

It's a pity there isn't more money in research. Imagine we were paid enough to pay for the electricity and make a small profit. 100 times more people would be doing it and everything would be solved immediately. Technology would move forwards 1000s of years.

It's a pity there isn't more money in research. Imagine we were paid enough to pay for the electricity and make a small profit. 100 times more people would be doing it and everything would be solved immediately. Technology would move forwards 1000s of years.

Science isn't just about computing. There are supercomputers 100 times more powerful than Milkyway@home, there are more researchers using powerful supercomputers than those use BOINC. But the scientific impact is less than what you'd expect. The only program you can profit from running it right now is cryptocurrency, and yeah, it does change the world by accelerating climate change.

Science isn't just about computing. There are supercomputers 100 times more powerful than Milkyway@home, there are more researchers using powerful supercomputers than those use BOINC.

So they must have the money to pay for the electricity and using that expensive supercomputer. So why can't we get in on a bit of that?

But the scientific impact is less than what you'd expect. The only program you can profit from running it right now is cryptocurrency, and yeah, it does change the world by accelerating climate change.

Just as well I'm an atheist.