ok merci

---

Your 1st job failed after a "[ERROR] glidein exited with return value 1.".
Those errors can't be investigated at the BOINC level since they happen deeper in the scripts.

your CMS tasks fail because the VMs don't have the permission to write the heartbeat file:
[pre]2023-10-03 01:50:09 (7176): VM Heartbeat file specified, but missing.[/pre]
Together with other log entries it looks like your user account is not a member of the boinc group.

]12:27:09 +0200 2023-10-03 [INFO] Requesting an idtoken from LHC@Home
X509_USER_PROXY = /tmp/x509up_u1000

Waiting, waiting.. since a quarter of hour.
Half an hour now, canceling after one hour of waiting...

2023-10-03 12:26:53 (28104): Guest Log: [INFO] Reading volunteer information
2023-10-03 12:27:08 (28104): Guest Log: [INFO] Requesting an X509 credential from LHC@home
2023-10-03 12:27:09 (28104): Guest Log: [INFO] CMS application starting. Check log files.
2023-10-03 12:27:10 (28104): Guest Log: [INFO] Requesting an idtoken from LHC@home
2023-10-03 13:14:39 (28104): Powering off VM.
2023-10-03 13:14:40 (28104): Successfully stopped VM.
2023-10-03 13:14:40 (28104): Deregistering VM. (boinc_a31803bb699ff414, slot#33)
2023-10-03 13:14:40 (28104): Removing network bandwidth throttle group from VM.
2023-10-03 13:14:40 (28104): Removing VM from VirtualBox.

Hypervisor System Log:

313:12:21.054578 Saving settings file "S:\ProgramData\BOINC\slots\17\boinc_9ebd457c4ec9cc22\boinc_9ebd457c4ec9cc22.vbox" with version "1.19-windows"[/quote]
That task was running fine until an impatient user cancelled it due to a misinterpretation of the console 1 output:
[pre]Run time 48 min 57 sec
CPU time 44 min 59 sec[/pre]
Should have been better to also check ALT-F2, ALT-F3 and ALT-F4.

pour moi ça refonctionne.j'ai désinstaller virtualbox 7.010 et j'ai installé la version 6.146.


for me it works again. I uninstall virtualbox 7.010 and I installed version 6.146.[/img]

---

something seems indeed to be wrong with all the CMS tasks I downloaded this early afternoon on several machines, i.e. about 8 hours ago.
CPU activity ended after about three hours, and since then the CPU is running idle. However, none of these tasks comes to an end :-(
Anyone making the same experience?

one job inside of a Task need two and a half hour.
The Task run about twelve hour.

one job inside of a Task need two and a half hour.
The Task run about twelve hour.

yes, thats true. All tasks which I started yesterday early afternoon got finished during last night, after about 10-12 hours. So there is a big difference in the runtime compared to what it was before. But it's okay, as long as one is aware of it.

From the server status page you can see what was the average runtime of a task (Runtime of recent tasks in hours: average, min, max).

---

From the server status page you can see what was the average runtime of a task (Runtime of recent tasks in hours: average, min, max).

I know that there is this kind of information shown on the server status page.
However, if one sees something like
0.81 (0.03 - 7.89)
it's clear that this does not tell much.

Fact is that here on my machines, it now takes the tasks about 3 times as long as before. But that's the way it is at the moment, no problem for me.

Yes, it is sometimes difficult to put it to perspective. Here is the same info as graphical format so you can view the history: https://grafana.kiska.pw/d/boinc/boinc?orgId=1&var-project=lhc@home&from=now-2d&to=now&refresh=30m

There are other projects there too.

---

Yes, it is sometimes difficult to put it to perspective. Here is the same info as graphical format so you can view the history: https://grafana.kiska.pw/d/boinc/boinc?orgId=1&var-project=lhc@home&from=now-2d&to=now&refresh=30m

There are other projects there too.

Thanks, Harri, for the link.
The per app runtime graph is exactly in accordance with my observation, what concerns CMS; in fact, this is true also for ATLAS and Theory :-)