Hi everyone, there's something wrong with the camb_legacy tasks, possibly related to a recent upgrade. I've temporarily disabled them (no validation, no new workunits created) until I can figure out the problem. The camb_boinc2docker application is still working normally.

Hello,
strange, yesterday i got two legacy WU.
One already crunched, returned and validated !!!
http://www.cosmologyathome.org/workunit.php?wuid=55728409
But still 129 WU awaiting validation since 22th june !
Why ?

---

Taking a guess, testing the fix with a small set of work units

Taking a guess, testing the fix with a small set of work units

Greetings. Since the camb_legacy tasks were "tweaked", my cosmology@home workload has been heavy and all jobs appear to complete successfully. However, I'm receiving very little credit for the work done. Where I once was receiving between 5,000-6,900 credits daily, I now receive only a few hundred credits per day, if any at all, even though I continue to process as many jobs as before. I suspect there might be something wrong with the accreditation process. Can you please address this issue? Thanks. - Gene Weber

You have a lot of jobs waiting for validation and I think that 'issue' is still being worked on as 'script_validator (camb)' is still showing as not running on the Server Status page

Hello,
We are a litle less than 3 weeks without any news. from admin.
And no any news or information from team..
Conclusion, I suspend all work of this project and also advise my team to do the same till problem is solved.
Sorry.
Credits here are ridiculous to compare with other project.
I compare bteween project , based on the same host.(355352)
And on all my four host, everywhere the same : this project give the lowest credit/WU.
So why to crunch for a project unable to solve problems ?

The worst is that there are no any news from admin, developer , scientist !!!

Best regards from the first belgian team admin

---

Greetings. Since the camb_legacy tasks were "tweaked", my cosmology@home workload has been heavy and all jobs appear to complete successfully. However, I'm receiving very little credit for the work done. Where I once was receiving between 5,000-6,900 credits daily, I now receive only a few hundred credits per day, if any at all, even though I continue to process as many jobs as before. I suspect there might be something wrong with the accreditation process. Can you please address this issue? Thanks. - Gene Weber

Hi Gene, looking at your hosts, the credits/job seems normal to me, the problem is simply that we don't have many camb_legacy jobs being sent out since I haven't been able to fix the problem. Are you sure the issue isn't simply that you are crunching fewer jobs and so not receiving as much credit? You could also look into setting up your computers to run camb_boinc2docker jobs, which are running fine at the moment.

Hello,
Credits here are ridiculous to compare with other project.
I compare bteween project , based on the same host.(355352)
And on all my four host, everywhere the same : this project give the lowest credit/WU.

Credit/WU isn't a good metric since WU across different projects can be different lengths (our WU are quite short for example, hence credit/WU is fairly small). In any case, since every project is free to award credits as they please, you should not put too much stock in cross-project comparison of credits. In case you weren't familiar with it, Cosmology@Home uses the BOINC Credit New system; I don't think its perfect but its the best I would say we have. Discussion about that is probably best for the BOINC message boards / email lists.

Also, apologies I've not solved the camb_legacy issues yet, its proving somewhat difficult. I will get it sorted it out but in the meantime I encourage everyone to take a look at running camb_boinc2docker jobs which are of more use to us scientifically anyway.

Hello,
Credits here are ridiculous to compare with other project.
I compare bteween project , based on the same host.(355352)
And on all my four host, everywhere the same : this project give the lowest credit/WU.

Credit/WU isn't a good metric since WU across different projects can be different lengths (our WU are quite short for example, hence credit/WU is fairly small). In any case, since every project is free to award credits as they please, you should not put too much stock in cross-project comparison of credits. In case you weren't familiar with it, Cosmology@Home uses the BOINC Credit New system; I don't think its perfect but its the best I would say we have. Discussion about that is probably best for the BOINC message boards / email lists.

Also, apologies I've not solved the camb_legacy issues yet, its proving somewhat difficult. I will get it sorted it out but in the meantime I encourage everyone to take a look at running camb_boinc2docker jobs which are of more use to us scientifically anyway.

Hello Marius,
Thanks for answer, reaction.
A lot of people are not able to install VB (or for some reason not want it, just like me).
So I suspend all WU. Some WU are validated (after the problem) the most not.
Why there are validated and other not. All my host are open. Look freely.
Best regards from the first Belgian's team admin

---

Marius,

the server status page currently shows that new camb_legacy work is generated, but the corresponding script_validator is not running. Also, 158071 tasks are shown waiting for validation, certainly mainly camb_legacy tasks.

Can you clarify why the work is generated even though the validator is stopped? Is validation planned for the whole active batch of camb_legacy work to occur at a scheduled time?

[quote]Hello,
Credits here are ridiculous to compare with other project.


Also, apologies I've not solved the camb_legacy issues yet, its proving somewhat difficult. I will get it sorted it out but in the meantime I encourage everyone to take a look at running camb_boinc2docker jobs which are of more use to us scientifically anyway.

It seems to me that you are not interested in volunteers and their problems. It costs us a lot of money to run your research and if you choose to use Credit New or as some will say Credit Screw than that is a sure way of loosing customers. You have other choices to use. Look at other projects, talk to their Admin to see what is best for all concerned.

At this moment you are still advocating (as stated four days ago and I see no change to that statement, to use Docker jobs.) The problem is that you are not generating work for Docker and the validator for legacy is turned off, yet jobs are available for legacy jobs and the pendings are increasing. Have you actually fixed the problem?

Hi everyone, there's something wrong with the camb_legacy tasks, possibly related to a recent upgrade. I've temporarily disabled them (no validation, no new workunits created) until I can figure out the problem. The camb_boinc2docker application is still working normally.

You stated the above on 25 Jun. On 16 Jul you stated that the problem is complicated and not yest fixed. . At this date the validator is still turned off and the pendings are climbing. Why are you issuing work units and wasting our time when in your own words something is wrong and you do not know how to fix it obviously.

I am sorry to use this tone of voice but your interaction with volunteers have never been very informative. I would have expected that once you state in the News that you disable the WU, I would expect that you announce in the News that it is working again. I see in the server that there is no Docker units being worked on yet legacy units are still being issued.

Some updates:

* The camb_legacy work generator was turned back on on accident, its off now, since I'm still unable to fix the validation problem (the validator is sporadically segfaulting and I've not been able to figure out why yet).

* The camb_boinc2docker workunits *are* being generated as normal, however, there is a formula BOINC sprint happening which is draining them about as fast as we can generate them. This should be over by Sunday, July 22, 22:00 UTC as I understand it.

Some updates:

* The camb_legacy work generator was turned back on on accident, its off now, since I'm still unable to fix the validation problem (the validator is sporadically segfaulting and I've not been able to figure out why yet).

* The camb_boinc2docker workunits *are* being generated as normal, however, there is a formula BOINC sprint happening which is draining them about as fast as we can generate them. This should be over by Sunday, July 22, 22:00 UTC as I understand it.

Hello,
Thanks for info.
But because legacy WU validator is off, you exclude a lot of people to participate at the sprint on Formula !!!
In fact you exclude all who do not want (or can not) install Virtual box !

---

Hello,
Thanks for info.
But because legacy WU validator is off, you exclude a lot of people to participate at the sprint on Formula !!!
In fact you exclude all who do not want (or can not) install Virtual box !

I do apologize for that, but at the same time there's not much I can do when the sprint chose to run C@H despite that we had had a notice up for a few weeks stating that camb_legacy was currently broken.

I try to run for the FB sprint; got quite a bunch of legacy WU (around 1000); 7 validated ... so I guess I can dump the rest ? and call it a day ?

FYI. Currently unable to download new tasks for camb_boinic2docker since 5:50am PST.

Snippet from the Boinc mgr event log:

7/20/2018 6:48:43 AM | Cosmology@Home | Temporarily failed download of vbox_job_b51ea4c387624bf391088b0588547110.xml: can't resolve hostname
7/20/2018 6:48:43 AM | Cosmology@Home | Backing off 00:07:59 on download of vbox_job_b51ea4c387624bf391088b0588547110.xml
7/20/2018 6:48:43 AM | Cosmology@Home | Started download of boinc_app_b5a9fd3f5b6d450996feb6cc5f02d1fd
7/20/2018 6:48:43 AM | Cosmology@Home | Started download of params_f4457e8a0c0442bc9f6e5f4fe388550b.tgz
7/20/2018 6:48:44 AM | | Project communication failed: attempting access to reference site
7/20/2018 6:48:46 AM | | Internet access OK - project servers may be temporarily down.
7/20/2018 6:48:46 AM | Cosmology@Home | Temporarily failed download of boinc_app_b5a9fd3f5b6d450996feb6cc5f02d1fd: can't resolve hostname
7/20/2018 6:48:46 AM | Cosmology@Home | Backing off 00:04:15 on download of boinc_app_b5a9fd3f5b6d450996feb6cc5f02d1fd
7/20/2018 6:48:46 AM | Cosmology@Home | Temporarily failed download of params_f4457e8a0c0442bc9f6e5f4fe388550b.tgz: can't resolve hostname
7/20/2018 6:48:46 AM | Cosmology@Home | Backing off 00:05:25 on download of params_f4457e8a0c0442bc9f6e5f4fe388550b.tgz
7/20/2018 6:50:26 AM | Cosmology@Home | update requested by user
7/20/2018 6:50:27 AM | Cosmology@Home | Sending scheduler request: Requested by user.
7/20/2018 6:50:27 AM | Cosmology@Home | Not requesting tasks: some download is stalled
7/20/2018 6:50:29 AM | Cosmology@Home | Scheduler request completed

Hello,
Thanks for info.
But because legacy WU validator is off, you exclude a lot of people to participate at the sprint on Formula !!!
In fact you exclude all who do not want (or can not) install Virtual box !

I do apologize for that, but at the same time there's not much I can do when the sprint chose to run C@H despite that we had had a notice up for a few weeks stating that camb_legacy was currently broken.

Thanks anyways Marius. You now see part of the frustration many of us have with the admin of Formula-BOINC.

---

Hello,
Thanks for info.
But because legacy WU validator is off, you exclude a lot of people to participate at the sprint on Formula !!!
In fact you exclude all who do not want (or can not) install Virtual box !

I do apologize for that, but at the same time there's not much I can do when the sprint chose to run C@H despite that we had had a notice up for a few weeks stating that camb_legacy was currently broken.

Hello,
Server status show legacy validator is up and running !!!
Also strange, I had 140 WU waiting validation. Now 139. But no any change in valid task (1WU since 06 jul)