LHC@home

Same for me, my main PC hasn't gotten any tasks since Friday. I'll check with the admins...

Me too, but not all of my machines are effected

PHuW10: 5xCMS exist, no ATLAS
Atlas1: 0xCMS, Full with ATLAS
WoolyW10: 0xCMS, several ATLAS, just got more ATLAS

From my infrastructure, I would make a guess, that the existence of other CERN-VM-Apps (CMS by me) blocks the download of ATLAS

---

Supporting BOINC, a great concept !

One box, that didn't get ATLAS-Tasks, has finished all CMS-Tasks and immediatly it could download ATLAS-Tasks.

Another BOX still has running CMS-Tasks and didn't get ATLAS again

---

Supporting BOINC, a great concept !

Yeti wrote:

From my infrastructure, I would make a guess, that the existence of other CERN-VM-Apps (CMS by me) blocks the download of ATLAS.


One box, that didn't get ATLAS-Tasks, has finished all CMS-Tasks and immediatly it could download ATLAS-Tasks.

Another BOX still has running CMS-Tasks and didn't get ATLAS again

Not here as I run a separate client instance that is configured to run nothing else but ATLAS.

On every of three PC's one SL69 native.
One is getting Atlas-tasks without interrupt.
The other two get nothing since last week.
So it seem infrastructure ?

On every of three PC's one SL69 native.
One is getting Atlas-tasks without interrupt.
The other two get nothing since last week.
So it seem infrastructure ?

Same for me: 3 Windows PCs with VirtualBox, same settings in LHC@Home preferences (ATLAS + SixTrack), but only one can get ATLAS tasks. I just tried removing and re-adding LHC@Home in BOINC on one of the machines but the result is the same: "No tasks are available for ATLAS Simulation".

---

We are the product of random evolution.

The deadline in LHCatHome Website for the starting tasks is ONE day later as in Boincmanager shown. (Also for Theory-tasks)
Maybe this info is useful.

The deadline in LHCatHome Website for the starting tasks is ONE day later as in Boincmanager shown. (Also for Theory-tasks)
Maybe this info is useful.

This is normal behaviour

---

Supporting BOINC, a great concept !

ATLAS jobs recently adds the "priority" feature, and with the old configuration on the lhc@home server, only the very reliable hosts can get these priority jobs, that is why for the past a few days, some volunteer hosts could not get any task even though there are unsent (high priority) jobs. We reconfigured the server, so now volunteer host can all get tasks!

---

Wenjing Wu wrote:

... only the very reliable hosts can get these priority jobs ...

Is it possible to get a definition for that?
To me it seems that the job distribution was just random.

I noticed that just before I stopped receiving jobs that I had an http error
which failed a task,

Then nothing after that forever.

Rather harsh wouldn't y0ou say?

Thank you for fixing it.

Stderr output
<core_client_version>7.6.22</core_client_version>
<![CDATA[
<message>
WU download error: couldn't get input files:
<file_xfer_error>
<file_name>jf_103ca2cca0d32ddc21eadb90b9344233</file_name>
<error_code>-224 (permanent HTTP error)</error_code>
<error_message>permanent HTTP error</error_message>
</file_xfer_error>

</message>
]]>

Only one I've seen in months

Adding to the conversation... I have regularly been receiving Atlas tasks without interruption, for the past few weeks. Behaviour on my computer: Atlas will download 8 tasks, run 1 (4 CPU), as soon as it completes and transmits, a new task will download. This keeps a queue of 8 tasks always on my computer (1 running, 7 waiting). This behaviour appeared immediately after the deadlines were cut from 2 weeks to 1 week. Late last week, the deadlines moved to 3 days, now they appear to be back out to 1 week. But I have not seen any times when my computer was without Atlas tasks.

The deadline in LHCatHome Website for the starting tasks is ONE day later as in Boincmanager shown. (Also for Theory-tasks)
Maybe this info is useful.

And the deadline showing in Boinc Manager is what seems to apply. I just had over 30 LHCb tasks automatically aborted because "Not started by deadline - canceled" when deadline in Boinc Manager arrived. So the deadline on the web-pages is off by one day.

---

ATLAS jobs recently adds the "priority" feature, and with the old configuration on the lhc@home server, only the very reliable hosts can get these priority jobs, that is why for the past a few days, some volunteer hosts could not get any task even though there are unsent (high priority) jobs. We reconfigured the server, so now volunteer host can all get tasks!

I think the problem of 'No sent Tasks' in Atlas is not solved completly at the moment.
I got max. 6 Task, this include the active one's. At the Moment i drive 4 Task with 3 Cores on the Ryzen CPU (runtime about 10.000 sec), so there are only 2 fresh WU's in queue.

This is a to low value because of the upload Limitation of my DSL-Connect.
If the Ryzen Cpu finished more than 2 WU's at the same time and other Computer's are uploading something (GPUGrid files are 100 - 150MB's upload)
Ryzen will be on idle for hour's.

Aktual all 3 Computers got max. 6 Task include active one's. No difference between slower i7-2600, mid i7-5820k and Ryzen 1700.

Hope you can figure out the Task limitation of the scheduler.

Aktual all 3 Computers got max. 6 Task include active one's. No difference between slower i7-2600, mid i7-5820k and Ryzen 1700.

Hope you can figure out the Task limitation of the scheduler.

Did you set in your preferences for Max # jobs "No limit". If, then try Max # jobs 24.

Hi Crystal,

I have Max # jobs 24 on my 3 machines and can only get 6 pending ATLAS tasks. See this thread: https://lhcathome.cern.ch/lhcathome/forum_thread.php?id=4432

---

We are the product of random evolution.

The queue for ATLAS simulation tasks is empty. Please refill.

http://atlasathome.cern.ch

There is work enough. The problem must be a other reason.

We had two separate problems this morning in our infrastructure which stopped the submission of WU to the BOINC server. These have both been fixed and there are new WU available now.

Thank you David and your Team.