Theory_2922-4886297-643_2 runtime so far 49h43m09s doing: Integrate 465 of 760: - After integration part 50000 events

Theory_2922-4898459-649_2 runtime so far 25h44m57s doing: Integrate 168 of 760: - After integration part 32000 events

oohh i read it now..."show graphics"...never saw that in my long BOINC carrier xD is there any timeline in the logs i dont see that i know if it still gets finished in time with the integrations? ^^

Or is it enough to calculate the beginn of the tasks day and 496 of 700 done from the log as 2/3 is done in ..4d as example and it WILL finishing in time?

anyone an idea what this task after having run for more than 2 days and with result status "successful" has been classified as "invalid" ?
https://lhcathome.cern.ch/lhcathome/result.php?resultid=433057550

https://lhcathome.cern.ch/lhcathome/show_user.php?userid=567711
Somebody needs to stop these 88 computers from having half million of Invalid Atlas

one needs quite some patience with these Herwig7 longrunners :-); on my hosts, they use to run between 10 and 20 days, some of them even longer

In reply to Crystal Pellet's message of 27 Feb 2026:

A new one:
==================================================================================
===> [runRivet] Fri Feb 27 08:19:04 UTC 2026 [boinc pp z1j 13000 160 - herwig7 7.2.1 nlo-pw 50000 643]
==================================================================================

After 4 hours runtime: Integrate 30 of 760:

I, too, have gotten such longrunners lately.

In reply to Crystal Pellet's message of 25 Feb 2026:

Edit: number of Unsent tasks slowly increasing now

not really :-(

In reply to Crystal Pellet's message of 8 Feb 2026:

Although "Unsent" still zero, I got this task: Theory_2922-4870672-586_0 batch 19655072 created 8 Feb 2026, 14:41:36 UTC

Edit: number of Unsent tasks slowly increasing now

With the queue empty, you naturally notice when a task times out or returns as error and gets put into the queue again. Check that task's history; it should have visited a couple of computers and not finished there during its lifetime.

That's a strange error:

The filename wildcard characters * or ? were entered incorrectly or too many were specified.
(0xd0) - exit code 208 (0xd0)</message>

Does this mean there won't be any virtualbox tasks anymore, and I can delete the project from my config?

It seems to me a permissions issue on your Linux system.

ATLAS tasks (native) are running fine, other BOINC projects as well. Hard to imagine that this is a simple permission issue. Any ideas how to investigate into this problem?

It looks like the task is trying to copy/move the result file from the slots directory into the projects directory. Is it a necessary step?

Thanks :), I see this for one task I have running :-

19300 events processed
19400 events processed
19500 events processed
19600 events processed

I assume it's still running then? Is there anywhere in that file that shows progress point?
Are the warnings anything to worry about?

pp bbbar 7000 20 - pythia8 8.313 default 100000 644

vbox:   Run time  1 hours 18 min  2 sec        CPU time  1 hours 16 min 34 sec
docker: Run time          45 min  3 sec        CPU time          38 min 16 sec

pp zinclusive 8000 -,-,100,170 - pythia8 8.306 tune-AU2m 100000 650

vbox:   Run time  5 hours  7 min 54 sec        CPU time	4 hours 57 min 50 sec
docker: Run time  1 hours 54 min 10 sec        CPU time 1 hours 40 min 49 sec

                   1. docker                               2. VirtualBox
			
Returned          15 Feb 2026, 11:11:24 UTC                15 Feb 2026, 12:37:39 UTC
Computer ID       10772116		                   10772116
Run time          19 min 22 sec		                   53 min 36 sec
CPU time          16 min 36 sec                            52 min 34 sec
Validate state    Valid                                    Valid
Credit            8.93		                           24.69
peak FLOPS        3.32 GFLOPS                              3.32 GFLOPS
App-version       Theory Simulation v302.10 (docker)       Theory Simulation v301.00 (vbox64_theory)
PeakWorkingSet    13.20 MB                                 69.93 MB
Peak swap size    6.63 MB                                  56.40 MB
Peak disk usage   8.31 MB                                  614.12 MB

job: run exitcode 0                                        0
job: diskusage    18052                                    18084
job: logsize      8072 k                                   8192 k
job: time         23m 15.5s                                50m 55.4s
job: cpuusage     1447 s                                   3080 s