Some Theory tasks on VirtualBox hang Probing /cvmfs/alice.cern.ch...
MadGraph5
These types of tasks are rare, but I see the same scenario on one of my PCs.
1. For about half an hour, there is some activity in the VM: Guest shows some CPU load, it downloads around 200 MB, and writes about 100 MB to the disk.
2. After that, Guest activity drops to zero, all performance graphs are flat, and the task log file becomes unreachable.
Here is an excerpt from the log:
===> [runRivet] Wed Apr 8 07:03:39 AM UTC 2026 [boinc pp zinclusive 13000 -,-,200 - madgraph5amc 2.7.2.atlas3...] ... ValueError: unsupported hash type md5 AttributeError : 'module' object has no attribute 'md5' ... ERROR: missing LHE output file: /scratch/tmp/tmp.UjcDJkl2wh/MG5RUN/Events/run_01/unweighted_events.lhe ... [2]+ 2535 Running ( $rivetExecString; exit $? ) & ERROR: fail to run madgraph5amc 2.7.2.atlas3 or Rivet (error exit code)
My preliminary, but not yet firm conclusion: The simulation never started because the angry Python strangled everything, maybe even itself. :)
My action: Brick therapy for that VM.
P.S. For those who are experienced or have real knowledge – please comment, is this "Brick therapy" a correct solution?
These types of tasks are rare, but I see the same scenario on one of my PCs.
1. For about half an hour, there is some activity in the VM: Guest shows some CPU load, it downloads around 200 MB, and writes about 100 MB to the disk.
2. After that, Guest activity drops to zero, all performance graphs are flat, and the task log file becomes unreachable.
Here is an excerpt from the log:
===> [runRivet] Wed Apr 8 07:03:39 AM UTC 2026 [boinc pp zinclusive 13000 -,-,200 - madgraph5amc 2.7.2.atlas3...] ... ValueError: unsupported hash type md5 AttributeError : 'module' object has no attribute 'md5' ... ERROR: missing LHE output file: /scratch/tmp/tmp.UjcDJkl2wh/MG5RUN/Events/run_01/unweighted_events.lhe ... [2]+ 2535 Running ( $rivetExecString; exit $? ) & ERROR: fail to run madgraph5amc 2.7.2.atlas3 or Rivet (error exit code)
My preliminary, but not yet firm conclusion: The simulation never started because the angry Python strangled everything, maybe even itself. :)
My action: Brick therapy for that VM.
P.S. For those who are experienced or have real knowledge – please comment, is this "Brick therapy" a correct solution?