LHC@home

I have some also. Here's one: https://lhcathome.cern.ch/lhcathome/result.php?resultid=334410656 Probably more to come later.

---

I have some also. Here's one: https://lhcathome.cern.ch/lhcathome/result.php?resultid=334410656 Probably more to come later.

okay, I see. So most probably misonfigured WUs, and no reason for me to be afraid that something's wrong with my system.

The bad thing thoug is that such a bad WU would run for hours and hours, overnight, ... thus blocking a slot for nothing.

Over night, there were some more of these faulty tasks :-(

What you can testing, Boinc have a upgrade only for Windows, from 7.16.11 to 7.16.20,
if this faulty Atlas are involved.
Have also upgrated Virtualbox to 6.1.30.
Saw also some faulty before in Win10pro and Win11pro.

What you can testing, Boinc have a upgrade only for Windows, from 7.16.11 to 7.16.20,
if this faulty Atlas are involved.
Have also upgrated Virtualbox to 6.1.30.
Saw also some faulty before in Win10pro and Win11pro.

okay, I could try this, thanks for the hint.

What I am also seeing now are tasks that are faulty in a different way than before: they do use full CPU power (in contrast to the faulty tasks from before), but the VM console shows zero events processed, all the time long the task is running.

Looking at this example shows that the WU fails on Windows as well as on Linux (running native):

Erich's task:
https://lhcathome.cern.ch/lhcathome/result.php?resultid=334527292

Corresponding WU:
https://lhcathome.cern.ch/lhcathome/workunit.php?wuid=176712440

Checked a few other WUs and all failed on all computers they were sent to.
Hence, it's more likely that its a faulty batch than a local issue.

I keep getting WUs which fail with all kinds of error reasons.
This one here now failed after 6 minutes: https://lhcathome.cern.ch/lhcathome/result.php?resultid=334540111

so something seems to go rather wrong with ATLAS presently.

I am wondering that while it is known since this morning that there obviously is a batch with faulty WUs, no steps have been taken to get those removed or stopped.

within the past few hours, a had several task in a row, where CPU usage was less than 1 minute, but the task was running forever.
See here:
https://lhcathome.cern.ch/lhcathome/result.php?resultid=334449376

if I interpret the stderr correctly, the problem was

2021-11-25 14:19:01 (27532): Guest Log: 00:00:10.004806 timesync vgsvcTimeSyncWorker: Radical guest time change: -3 587 877 475 000ns (GuestNow=1 637 846 340 764 851 000 ns GuestLast=1 637 849 928 642 326 000 ns fSetTimeLastLoop=true )

has anyone else made same experience?

last night, I had another task with:

2021-12-06 23:23:04 (16356): Guest Log: 00:00:10.018997 timesync vgsvcTimeSyncWorker: Radical guest time change: -3 587 915 035 000ns (GuestNow=1 638 829 384 890 054 000 ns GuestLast=1 638 832 972 805 089 000 ns fSetTimeLastLoop=true )

CPU use was only 54 seconds, but the task did not stop automatically, but ran through all night thus wasting a slot for nothing.

https://lhcathome.cern.ch/lhcathome/result.php?resultid=335188584

what kind of failure is this "Radical guest time change" thing - what's the cause for it?

what kind of failure is this "Radical guest time change" thing - what's the cause for it?

This is not essentiell.
When one of hundreds Atlas-Tasks have this error, and run for several hours, we can live with it.
Had also one last week. We can only watching it over the time, atm.

what kind of failure is this "Radical guest time change" thing - what's the cause for it?

When one of hundreds Atlas-Tasks have this error, and run for several hours, we can live with it.

unfortunately, the error rate is much higher than just 1 out of hundreds.
I had one last night, I had the next one just now.

One on Win11pro atm with 2 Cores and 13 hours runtime. The faulty-Counter for me is now TWO!
Hoping, the last and only one for this week :-).

I got the next one right now (so the third one today).

what I notice is that with these faulty tasks, the vm_image.vdi is only about 2.5GB in size, as opposed to the others with about 3.3GB.
Also, when trying to open the VM console, localhost login does not work.

So these are the two characteristics of this kind of faulty task, and I now have no other choice than checking every once a new task starts :-(

The Rate of this failure has raised since yesterday to more than 10 for me :-(

---

Supporting BOINC, a great concept !

just now, I got the next one.
So this was the fourth one since last night. I am afraid more will follow :-(

just now, I got the next one.
So this was the fourth one since last night. I am afraid more will follow :-(

I'm shure more will follow !

---

Supporting BOINC, a great concept !

Have stopped Atlas for Windows and have send a PM to David.

This Morning I had to to cancel more than 15 WUs hanging around.

Sorry, but it sucks !

---

Supporting BOINC, a great concept !

Okay, for me time to take an outage from Atlas.

---

Supporting BOINC, a great concept !

This Morning I had to to cancel more than 15 WUs hanging around.
Sorry, but it sucks !

indeed, at this point it's a waste of time and ressources :-(
I am wondering that no one is stopping these faulty tasks.