LHC@home

Most of the LHCb jobs that run on my machine end with the subject error. I upgraded to the latest Virtual Box, so have no further clue what's apparently going haywire. Thoughts please on anything I can do to fix this apparent problem.

Obviously there are no LHCb-jobs at the moment.

Exit status 206 (0x000000CE) EXIT_INIT_FAILURE

and in the stderr output

VM Completion Message: Condor exited after 620s without running a job.

It seems that the problem comes from the server side.
I switched to cms untill it is fixed.
Apparently , even the wlcg performance test cluster encountered the same troubles.
It could be interesting when troubles occurs to have information on this page , using a colour code on the name of the application specified.
Example : a traffic light
name in :
Green when all is correct.
Yellow when troubles can be solved quickly.(no wu or upgrade server)
Red when the fail is permanent and admins are looking after the person which has the solution.(outage or overload)

So , crunchers would be able to know what choice to be made to not waste their time computer and select a sub-project with a chance to be useful for the community.

Is it possible ?

I have my computer enabled to receive task from all sub-projects. Typically it receives all LHCb tasks.

It would be great if the system knew there was an issue and gave me tasks from other sub-projects.

I have deselected LHCb tasks from my LHC@home preferences and Updated the project. Received one Atlas 8 Core, one CMS, and two Theory Simulation applications. Hope this works for others. Happy computing.

The HTCondorCE machine that sends LHCb simulations to the VM was sick since Friday, leading to these timeouts from the application within the VM.

LHCb simulations should be operational again now. Sorry for the trouble.

Is there a quota for daily tasks in LHCb ?(-1 for tasks with errors)
If this is real , it would be better to reset all the hosts which had lots of errored wus during the past week-end in order to use more quickly the big hosts to come back and run LHCb tasks.

I feel not, on my computers it will just keep getting tasks, waiting 10min to fail then getting another set.

It would better if there was then it would kick you over to another set of task as LHCb tends to hog the computer if given choice of all projects.

I came back to LHCb this morning and after solving some troubles on my side because a vm was stuck in virtualBox Manager , it occured the same behaviour ,you spoke about in your post(10 min working and then failing).
But after deleting this vm in virtualbox manager , the next task seems to run normaly (9h00 spent and still running).
I think it's better to have the pack extension same version virtualbox installed , so you can see the vm unreachable in virtualbox ,cleaning up the environment free the link between boinc and virtualbox.
Now i cross fingers , but it is working as expected.
---------------------------------------------------------------------------------
I believe that LHCb tasks hog the computer because they are not yet in production as other sub-projects.
Maybe the priority given to test application if "run test application" is checked, has to be modified ?
For instance (75 % to test application and 25 % to normal application , so the balancing between sub-project could be effective when LHCb is out of order...
---------------------------------------------------------------------------------
What are the difficulties which prevent LHCb to be like other sub-projects ?