1) Forums : Technical Support : client_state.xml keeps getting rewritten (Message 22015)
Posted 17 Dec 2018 by xii5ku
For the time being, Cosmology@home does not generate new tasks. If you want to test your host for VirtualBox functionality right now, consider to run the VB based subprojects of LHC@home.

At LHC@home, study Yeti's "Checklist Version 3 for Atlas@Home (and other VM-based Projects) on your PC".

At Cosmology@home, study the FAQ.

Note, client_state.xml contains just this: Client state. It is not a configuration file. Normally this file is "write only", written by the client. AFAIU the only time that the client reads this file is when it starts. In other words, (a) don't edit this file unless you know exactly what you are doing, (b) edit this file only while the client is not running.

Deleting a tag from one of BOINC's xml files does not reset the pertaining setting to a default state. You need to keep the tag and edit it explicitly to the desired default value, instead of merely deleting the tag, if you want the client to go back to the default.


  1. Reboot and go into the BIOS. Check that hardware extensions for virtualization are enabled (Intel VT-x or AMD-v).
  2. Boot into the OS. If the BOINC client was auto-started, shut it down.
  3. If you have Hyper-v, Docker, KVM, or Xen installed, deinstall them.
  4. In BOINC's client_state.xml, change the line <p_vm_extensions_disabled>1</p_vm_extensions_disabled> to <p_vm_extensions_disabled>0</p_vm_extensions_disabled>.
  5. Start the client.

2) Forums : Technical Support : script_validator (camb) is down (Message 22011)
Posted 2 Dec 2018 by xii5ku
The validators have been running during the last 3 days, and are bound to be done with their backlog soon:

This is helped by the fact that task generation stopped yesterday (camb_boinc2docker at least, don't know about camb_legacy) ... once more, after it went off and on again before. Whether or not this is connected with the mid-November announcement (Preparation for a server upgrade) is unknown to me.
3) Forums : Technical Support : No tasks (Message 21991)
Posted 5 Nov 2018 by xii5ku
I confirm: Server status shows plenty of tasks ready to send, yet most of the requests for new work are unsuccessful.

I noticed that the number of tasks in progress is pretty constant at about 16,000 tasks (since about November 3, 00:00 UTC). Maybe the scheduler is throttling the emission of new work such that tasks in progress don't exceed ~16,000, maybe with the goal to have a chance to catch up on WUs waiting for validation?

(The camb_boinc2docker tasks which I complete are validated almost instantly like usual, hence I suspect that the large number of WUs waiting for validation is all camb_legacy.)
4) Forums : Technical Support : No tasks (Message 21987)
Posted 3 Nov 2018 by xii5ku
for several days until Friday 18:00UTC, server status showed several daemons being down. Then they were all up for a while, but now db_purge (camb_boinc2docker) is down again.
5) Forums : News : camb_legacy tasks temporarily suspended (Message 21976)
Posted 20 Oct 2018 by xii5ku
This week's pending validation graph:

Looks like by the end of October 15, more people began to notice that the camb_legacy validator is not working, and turned away.

Transitioner backlog:

Yet, despite these troubles, contributors continue to download and process every single new task, fetching them the very minute one gets ready to send:

(Graphs courtesy to my team mate Kiska.)
6) Forums : News : Recent outage explanation (Message 21962)
Posted 11 Oct 2018 by xii5ku
@Trotador, do you think so? Maybe the only difference is that the server was finally done validating its backlog of almost 80,000 camb_legacy WUs, and now both the processor load from the validator and the database size should have gone down.

If there was a server upgrade, it was performed without server downtime. Hence I doubt it.

Besides, looking up computer results lists, let alone user results lists, at the Cosmo web server is still an extremely slow undertaking.
7) Forums : News : camb_legacy tasks temporarily suspended (Message 21961)
Posted 11 Oct 2018 by xii5ku
As a followup:
Evidently, Marius gave the legacy validator a kick on October 5.

It worked through its backlog of WUs waiting for validation and finished it at October 10, ~22:00 UTC.
8) Forums : Technical Support : BOINC manager glitch/quirk on account connection [Linux] (Message 21959)
Posted 11 Oct 2018 by xii5ku
The BOINC data directory is located at C:\ProgramData\BOINC in most Windows installations, and /var/lib/boinc or /var/lib/boinc-client in most Linux installations.
9) Forums : Technical Support : BOINC manager glitch/quirk on account connection [Linux] (Message 21956)
Posted 10 Oct 2018 by xii5ku
any way around?

Two even.

a) You can run boinccmd --project_attach "http://www.cosmologyathome.org/" authenticator in a terminal. authenticator is a long hexadecimal string, also known as acount key. It is the first key shown at weak_auth.php when you are logged in here. (At your user account page, go to "Acoount keys - View".)

b) You can copy the file account_www.cosmologyathome.org.xml from the BOINC data directory of a host which is already attached to Cosmo to the BOINC data directory of the host that you whish to attach. Then restart this client.
10) Forums : News : Recent outage explanation (Message 21953)
Posted 10 Oct 2018 by xii5ku
While I had difficulties to receive tasks during the last few days, I nevertheless used to get quite a few, as my RAC indicates.

But I have not received a single tasks anymore since today, 10:30:24 UTC. (Talking about camb_boinc2docker only; I have camb_legacy checked off.)

I looked at the top 100 hosts. None of them has received tasks after 10:30:24 UTC either; neither camb_boinc2docker nor camb_legacy. With the following exceptions: Hosts 356704, 330383, 349863, 348148, 338259 received 7 tasks together, all of which are resends of previously failed tasks, not newly generated WUs.

server_status.php claims that camb_boinc2docker_work_generator and camb_legacy_work_generator are both running (status from 10 Oct 2018, 17:49:32 UTC), but there are clearly no new WUs.
11) Forums : News : camb_legacy tasks temporarily suspended (Message 21944)
Posted 3 Oct 2018 by xii5ku
Since September 28, the camb_legacy validator is down again.
Meanwhile, the camb_kegacy work generator keeps generating...

(I am not affected myself, as I run camb_boinc2docker only.)

BTW, the drop in PPD in Gridcoin's stats shows that the Gridcoin miners are on auto-pilot, and run 95 % camb_legacy : 5 % camb_boinc2docker. (Going by credit; going by CPU time it is an even lower percentage of camb_boinc2docker.)
12) Forums : News : Recent outage explanation (Message 21943)
Posted 1 Oct 2018 by xii5ku
xii5ku wrote:
- No tasks available.

OK, almost no tasks available, and this was explained by the 2nd part of message 21940.
13) Forums : News : Recent outage explanation (Message 21942)
Posted 1 Oct 2018 by xii5ku
Something is amiss again:
- No tasks available.
- free-dc and boincstats pulled negative stats updates yesterday.
14) Forums : Technical Support : Snooze function - options request (Message 21858)
Posted 24 Jul 2018 by xii5ku
M wrote:
I had to manually navigate to the BOINC folder in the basic Windows commandline

Do you mean the program directory, or the data directory?

You don't need to CD into the program directory if you either specify the full path to the exe like in my example, or add the program directory to the PATH environment variable.

You don't need to CD into the data directory if it is the default BOINC data directory path (C:\ProgramData\BOINC\) or if you add the --host and --passwd options to boinccmd call. The latter is applicable if your boinc client is configured for restricted remote control.

(A brief and not very readable info on control access: https://boinc.berkeley.edu/wiki/Controlling_BOINC_remotely)

M wrote:
but still a GUI fix would be nice for the sake of convenience.

If you need the snooze function with just one particular timeout, you can put the command with all its parameters into a *.BAT file or simply into a shortcut.

For a selection of several often needed timeouts, you could create a subdirectory somewhere, e.g. in the Programs folder of Windows' start menu*, which you populate with several shortcuts for different timeouts; say 1.25 h, 1.5 h, 1.75 h, and so on.

If you run your movie player on the same PC as the boinc client, you could add the movie player into the dialogue "Options" / "Exclusive applications..." of boincmgr's advanced view. Then, the boinc client will always suspend computation as long as the movie player runs.

*) I'm still on Windows 7, dunno if it works the same on Windows 10.
15) Forums : Technical Support : Snooze function - options request (Message 21856)
Posted 23 Jul 2018 by xii5ku
This can be done in DOS/Windows' basic CMD shell with just a single command:

    "C:\Program Files\BOINC\boinccmd" --set_run_mode never 3600

This is for exactly 1 hour suspension of boinc's CPU activity. Replace 3600 as desired.
More info: https://boinc.berkeley.edu/wiki/Boinccmd_tool

If you want to issue two specific boinccmd commands with a defined gap between them, it can be done in CMD or as a *.BAT file too:

    "C:\Program Files\BOINC\boinccmd" your_first_command
    TIMEOUT /T 3600
    "C:\Program Files\BOINC\boinccmd" your_second_command

you'd perform this without shutting the boinc client down. The client simply suspends and resumes the science application on command.

16) Forums : General Topics : Formula BOINC sprint at Cosmology@Home, July 2018 (Message 21854)
Posted 23 Jul 2018 by xii5ku
Some graphs from stats3.free-dc.org:

Daily points added:

This dramatic increase in PPD is certainly to be attributed to the camb_legacy validator put back into operation, and only to a small part to the sprint activity. The validator began its work on Friday, July 20, 12:48 UTC, but stats-free-dc picked it up first with their Saturday update.

Daily teams added:

Nothing unusual to see here.

Daily users added:

Again, the effects of the camb_legacy validator operating again is dwarfing any effect that the sprint may have had. free-dc's Saturday stats update was the first to catch points of validated work from many users who joined during the 4 weeks during which the validator was off.

Daily hosts added:

Here we may see a certain effect of the sprint announcement on July 18 22:00 UTC, and then on Saturday again a huge effect of the validator fix. Most of these hosts were surely added during the past 4 weeks.

17) Forums : General Topics : Formula BOINC sprint at Cosmology@Home, July 2018 (Message 21853)
Posted 23 Jul 2018 by xii5ku

FYI, the sprint is over since 14 hours now.
The server status page currently shows:

application ....................... unsent .... in progress
camb_legacy .................. 0 .............. 52906
camb_boinc2docker ....... 0 .............. 9137

0 unsent looks correct to me because no tasks are received by my clients now. (I didn't try hard though.)

But 62043 in progress is likely incorrect. My own tasks list shows 2 tasks in progress which the hosts reported as complete mid Friday, and 11 tasks which they reported complete mid Sunday. The clients must have received proper scheduler replies that the reports were taken by the server, otherwise I would still see these tasks locally, of course.

I don't worry about the credit for these 13 tasks. I am only mentioning it just in case there is something odd with the database in general.
18) Forums : General Topics : Formula BOINC sprint at Cosmology@Home, July 2018 (Message 21848)
Posted 22 Jul 2018 by xii5ku
atp1916 wrote:
Is the project in need of hardware donations?

We need to send equipment (packed up safe for transport) to Marius and his fellow cosmologists until they finally figure out what's been up with all the as yet unaccounted matter in this universe.
19) Forums : General Topics : Formula BOINC sprint at Cosmology@Home, July 2018 (Message 21845)
Posted 22 Jul 2018 by xii5ku
Marius, thank you.

I ran camb_legacy for half a day on Thursday until I had time to add Virtualbox on hosts which didn't have it before. Current status of my camb_legacy results: 90 % valid, 10 % pending validation (not counting tasks which I aborted once I had vbox sorted out).

I don't particularly like to have vbox's kernel modules on my machines due to their bad track record WRT kernel stability in the past (works for me currently though). And I do not like the footprint and subpar BOINC integration of vboxwrapper based DC applications. But I acknowledge that it may be a help to application development, and also recognize that results from camb_boinc2docker are of more value to the C@H project now.
20) Forums : General Topics : Formula BOINC sprint at Cosmology@Home, July 2018 (Message 21829)
Posted 21 Jul 2018 by xii5ku
perhaps the camb_boinc2docker work generator shouldn't even work faster than it does. Given that the tasks have a run time of just a few minutes but produce results files that are 2.6 MB big, I wonder if Cosmology@Home's internet connection bandwidth is another limit which prevents a higher production rate here.

(In other words, camb_boinc2docker tasks are not very effective from the Distributed Computing point of view, because of too short of a run time and too large network transfers.)

Next 20