Development for LHC@home

Unfortunately a copy/rename on the filsystem doesn't change the UUID.
Best would be to
- unzip "CMS_2021_07_07.vdi.gz"
- run "vboxmanage clonemedium CMS_2021_07_07.vdi CMS_2022_06_20.vdi" (CMS_2022_06_20.vdi is just a suggestion)
- gzip "CMS_2022_06_20.vdi" to get "CMS_2022_06_20.vdi.gz"
- create a new app_version based on "CMS_2022_06_20.vdi.gz"


unzip -> clone -> gzip takes less than a minute.

Done. New version available. Sorry for the delay.

Might be a firewall issue.

computezrmle, thanks again for that guru level opinion !
I'm able to confirm now that it was infact an issue with a firewall setting in my cable modem.

I remembered that I had changed the 'Firewall Protection' setting from 'Low' to 'Medium' some time ago. And I hadn't run any LHCathome-dev or LHC@Home tasks after making that change, until this week.

I don't know what those different levels (Low, Medium, High) actually change under-the-hood on the 'Firewall Protection'. There's no information about that. Only this: "This setting helps protect your network from denial of service (DoS) attacks and other common Internet attacks."
There's also additional settings for the 'Firewall' : IPv6 Firewall Protection, Block Fragmented IP Packets, Port Scan Detection, WAN Blocking.
These can be OFF or ON, but their settings don't seem to change by adjusting the 'Firewall Protection' level. I hadn't changed them. They have been ON all the time.

With 'Firewall Protection : Medium' I had problems with 100% of the CMS and ATLAS tasks from both LHCathome-dev and LHC@Home on both of my hosts (W10 and W11).

ATLAS example : https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3094625
CMS example : https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3094303

And after I made that change from 'Medium' back to 'Low' ... all problems were gone immediately:

ATLAS example : https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3095229
CMS example : https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3094836

This was a new thing for me as I hadn't noticed any differences while using my internet connection outside these projects. Logging in on various services, streaming and everything else had worked without problems with 'Medium' too.

Executing CMSSW
cmsRun -j FrameworkJobReport.xml PSet.py
warn [frontier.c:1014]: Request 363 on chan 1 failed at Wed Jun 29 06:40:56 2022: -6 [fn-socket.c:239]: read from xx.xxx.xxx.xx timed out after 10 seconds
warn [frontier.c:1092]: Trying next server cms1-frontier.openhtc.io with same proxy xx.xxx.xxx.xx[xx.xxx.xxx.xx]
xx.xxx.xxx.xx is my own Proxy CentOS9-VM with squid 5.2.
Is this ok?