Development for LHC@home

Summary without using app_config.xml:

With the old project URL, I get the newest application v47.60 for 1 core and 3000MB RAM

With the new https project URL, I get the old application v47.40 with 2048MB RAM.
This old version can't handle multi core. The number of cores is correct, but the RAM stays on 2048MB.
Running e.g. a dual core always ends into an error: Exit status 207 (0x000000CF) EXIT_NO_SUB_TASKS

What I am getting is 47.50 on the new URL.
Tullio
They all fail not being able to connect to the Condor server

What I am getting is 47.50 on the new URL.
Tullio
They all fail not being able to connect to the Condor server

According to this page you got v47.40.

Howsoever, I guess this was the last version before you changed from the HTTP URL to the HTTPS URL?

You may crosscheck this by reattaching your host to the old HTTP URL: http://lhcathomedev.cern.ch/vLHCathome-dev/
I'm sure you will get the most recent v47.60 from there.

Beside that CERN had some trouble regarding the condor server and I'm not sure if this is solved.
All I can say is that my hosts are currently running regular CMS tasks without errors.

When I check Properties on my Boinc Manage I see 47.50. I am running now Atlas@home both single core and two cores.
Tullio

I see. You wrote about the regular project, I wrote about the dev project.

On my hosts the HTTP/HTTPS error occurred in both projects.

Now I have one CMS task running, two Atlas tasks trying to upload and a LHCb task waiting to run. Why?
Tullio

Most likely waiting for memory.

I got 24 GB of RAM. It is used at 20%.
Tullio

Now I have one CMS task running, two Atlas tasks trying to upload and a LHCb task waiting to run. Why?
Tullio

Atlas has been missing since around 0300GMT. Even their website is down for me.

Edit:-
Back now, tho' @1545.

I have uploaded 3 Atlas tasks, one two cores and two one core. All validated.
Tullio

Now I have one CMS task running, two Atlas tasks trying to upload and a LHCb task waiting to run. Why?
Tullio

An ATLAS-task thinks it needs 8900MB of memory despite of settings in app_config.xml due to rsc_memory_bound in client_state.xml of 9332326400 bytes.
This value comes from 2500MB + 800MB*max_of_8_cores makes 8900MB.

Atlas tasks run two at a time, except the dual core version. It is LHCb which won't run while another task is running. Now I have a Theory dual core task running and two LHCb tasks waiting to run, plus SETI@home GPU tasks running one at the time. I got plenty of RAM (24 GB) on the Windows 10 PC and I am never out of memory.
Tullio