Development for LHC@home

I've made a new version 1.14 which adds the open_file tag to the vdi image as discussed in this thread.

This may increase stability for some people.

@CP
Please repeat the test from here (https://lhcathomedev.cern.ch/lhcathome-dev/forum_thread.php?id=570&postid=7536) with v1.14.

The postponed task issue is also happening with v1.14 occasionally.

https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3097676

From Manager Event log;

LHC@home 05 Jul 18:28:21 Computation for task Theory_2390-1121113-268_0 finished
LHC@home 05 Jul 18:28:21 Starting task Theory_2390-1140193-268_1
LHC@home 05 Jul 18:28:22 Started upload of Theory_2390-1121113-268_0_r1802300195_result
LHC@home 05 Jul 18:28:24 Finished upload of Theory_2390-1121113-268_0_r1802300195_result
lhcathome-dev 05 Jul 18:28:26 Computation for task szwLDmtCfS1n7Olcko1bjSoqABFKDmABFKDmKFbSDmEMHKDmNImevm_1 finished
lhcathome-dev 05 Jul 18:28:26 Starting task F8kMDmkCfS1n7Olcko1bjSoqABFKDmABFKDmKFbSDm5LHKDmiDTt7n_1
lhcathome-dev 05 Jul 18:28:28 Started upload of szwLDmtCfS1n7Olcko1bjSoqABFKDmABFKDmKFbSDmEMHKDmNImevm_1_r1739401601_ATLAS_result
lhcathome-dev 05 Jul 18:28:28 Started upload of szwLDmtCfS1n7Olcko1bjSoqABFKDmABFKDmKFbSDmEMHKDmNImevm_1_r1739401601_ATLAS_hits
LHC@home 05 Jul 18:28:29 Sending scheduler request: To report completed tasks.
LHC@home 05 Jul 18:28:29 Reporting 1 completed tasks
LHC@home 05 Jul 18:28:29 Not requesting tasks: "no new tasks" requested via Manager
LHC@home 05 Jul 18:28:30 Scheduler request completed
LHC@home 05 Jul 18:28:30 Project requested delay of 6 seconds
lhcathome-dev 05 Jul 18:28:36 Finished upload of szwLDmtCfS1n7Olcko1bjSoqABFKDmABFKDmKFbSDmEMHKDmNImevm_1_r1739401601_ATLAS_hits
lhcathome-dev 05 Jul 18:29:30 Task F8kMDmkCfS1n7Olcko1bjSoqABFKDmABFKDmKFbSDm5LHKDmiDTt7n_1 postponed for 86400 seconds: VM environment needs to be cleaned up.
lhcathome-dev 05 Jul 18:29:53 Finished upload of szwLDmtCfS1n7Olcko1bjSoqABFKDmABFKDmKFbSDmEMHKDmNImevm_1_r1739401601_ATLAS_result
lhcathome-dev 05 Jul 18:29:57 Sending scheduler request: To report completed tasks.
lhcathome-dev 05 Jul 18:29:57 Reporting 1 completed tasks
lhcathome-dev 05 Jul 18:29:57 Not requesting tasks: "no new tasks" requested via Manager
lhcathome-dev 05 Jul 18:29:59 Scheduler request completed

Crystal,
Cosmology@Home have also some postponed.
Have running it for a longer time, up to two weeks ago.
There is no control, when it comes.
The only Version Virtualbox with no problems, always is 5.2.44.
Is it possible to test it for us?
Thank you.
Do it also tomorrow on my 8-Core.

I will not test (very) old versions of VirtualBox.

btw: project admin and -scientist of C@H wasn't active himself for over 4 years.

The postponed status overthere probably is coming from communication lost between vboxwrapper and VBoxSVC.exe

Run 2 wus without problem
I have not the message "posponed", but this message in the log:

022-07-05 21:44:25 (1264): Guest Log: 00:00:10.006968 timesync vgsvcTimeSyncWorker: Radical guest time change: -7 188 627 562 000ns (GuestNow=1 657 050 265 281 557 000 ns GuestLast=1 657 057 453 909 119 000 ns fSetTimeLastLoop=true )

It seems a bit challenging to get these tasks at the moment. Could you make a bunch of them available again... ? Thanks

Seeing the same, we have to wait.

Run 2 wus without problem
I have not the message "posponed", but this message in the log:

022-07-05 21:44:25 (1264): Guest Log: 00:00:10.006968 timesync vgsvcTimeSyncWorker: Radical guest time change: -7 188 627 562 000ns (GuestNow=1 657 050 265 281 557 000 ns GuestLast=1 657 057 453 909 119 000 ns fSetTimeLastLoop=true )

Did you follow this and set your Windows host to UTC?
https://lhcathomedev.cern.ch/lhcathome-dev/forum_thread.php?id=570&postid=7519

Did you follow this and set your Windows host to UTC?
https://lhcathomedev.cern.ch/lhcathome-dev/forum_thread.php?id=570&postid=7519

Mmm, no.
Here, in Italy, we are UTC+1

This setting doesn't change your local timezone.
It just tells Windows whether the BIOS RTC is set to UTC or to local time.

See here for a deeper explanation:
https://github.com/BOINC/boinc/pull/4631

See here for a deeper explanation:
https://github.com/BOINC/boinc/pull/4631

I'll try

I encountered that "postponed" problem now for the first time. This task:
https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3098089

"Postponed" had happened while that task was running parallel to one LHC@home ATLAS v2.00 task.
I suspended both tasks, shutdown Boinc, restarted Boinc and resumed both tasks. This v1.14 task then started all over from the beginning. It's making progress again.

Have reinstalled Virtualbox 5.2.44 and get no postponed.
See thread with Vers.1.13.

I encountered that "postponed" problem now for the first time. This task:
https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3098089

I aborted that task as there was no real prosessing happening.
Then I clicked "reset" for this project and made sure there were no vdi-images left on the disk. And also VirtualBox Manager didn't show any.

Still, the next task was again postponed straight away:
https://lhcathomedev.cern.ch/lhcathome-dev/result.php?resultid=3098138
There was one v2.00 task running in parallel at this point.

Command:
VBoxManage -q storageattach "boinc_ff69ef3af1554759" --storagectl "Hard Disk Controller" --port 0 --device 0 --type hdd --mtype multiattach --medium "D:/Boinc_data/projects/lhcathomedev.cern.ch_lhcathome-dev/ATLAS_vbox_1.14_image.vdi"
Output:
VBoxManage.exe: error: Cannot attach medium 'D:\Boinc_data\projects\lhcathomedev.cern.ch_lhcathome-dev\ATLAS_vbox_1.14_image.vdi': the media type 'MultiAttach' can only be attached to machines that were created with VirtualBox 4.0 or later
VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component SessionMachine, interface IMachine, callee IUnknown
VBoxManage.exe: error: Context: "AttachDevice(Bstr(pszCtl).raw(), port, device, DeviceType_HardDisk, pMedium2Mount)" at line 776 of file VBoxManageStorageController.cpp

Notes:

Another VirtualBox management application has locked the session for this VM.
BOINC cannot properly monitor this VM and so this job will be aborted.


2022-07-07 03:51:53 (8328): Could not create VM
2022-07-07 03:51:53 (8328): ERROR: VM failed to start
2022-07-07 03:51:58 (8328):
NOTE: VM session lock error encountered.
BOINC will be notified that it needs to clean up the environment.
This might be a temporary problem and so this job will be rescheduled for another time.

Have Atlas-Production tasks (Virtualbox 6.0.14) running with vboxwrapper204 (rename of the original name vboxwrapper_26198ab7_windows_x86_64)
Testing Theory from -dev, no postponed.
So, when both are using vboxwrapper204, it ok.https://lhcathomedev.cern.ch/lhcathome-dev/show_host_detail.php?hostid=4639

I have the following combination running both with vboxwrapper 26204: Theory from LHC@home (production) and ATLAS from the dev-server.
The difference is: dev is using multi attach VM's and production is using 'normal' VM's.
It's not the vboxwrapper itself causing problems, but the access of multi-attach, when also a normal VM is in use.
It's always the multi-attach not able to create the difference file and get the postponed and powered off status

lhcathome-dev 07 Jul 00:52:56 Computation for task YFbLDmcyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDm4OHKDm3myKQm_0 finished
lhcathome-dev 07 Jul 00:52:56 Starting task jsuMDmhyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDm9OHKDmv1HVdn_0
lhcathome-dev 07 Jul 00:53:43 Task jsuMDmhyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDm9OHKDmv1HVdn_0 postponed for 86400 seconds: VM environment needs to be cleaned up.
lhcathome-dev 07 Jul 00:53:43 Starting task kzHMDmfyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDm7OHKDmanDY1n_0
lhcathome-dev 07 Jul 00:54:29 Task kzHMDmfyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDm7OHKDmanDY1n_0 postponed for 86400 seconds: VM environment needs to be cleaned up.
lhcathome-dev 07 Jul 00:54:29 Starting task 6SfLDmbyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDm3OHKDmEVBFVn_0
lhcathome-dev 07 Jul 00:55:13 Task 6SfLDmbyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDm3OHKDmEVBFVn_0 postponed for 86400 seconds: VM environment needs to be cleaned up.
lhcathome-dev 07 Jul 00:55:13 Starting task KNwLDmdyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDm5OHKDml3ryWo_0
lhcathome-dev 07 Jul 00:55:58 Task KNwLDmdyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDm5OHKDml3ryWo_0 postponed for 86400 seconds: VM environment needs to be cleaned up.
lhcathome-dev 07 Jul 00:55:58 Starting task hk3KDmTyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDmuOHKDmJYKt2n_0
lhcathome-dev 07 Jul 00:56:42 Task hk3KDmTyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDmuOHKDmJYKt2n_0 postponed for 86400 seconds: VM environment needs to be cleaned up.
lhcathome-dev 07 Jul 00:56:42 Starting task yulLDmSyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDmtOHKDmWxo2Nm_0
lhcathome-dev 07 Jul 00:57:27 Task yulLDmSyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDmtOHKDmWxo2Nm_0 postponed for 86400 seconds: VM environment needs to be cleaned up.
lhcathome-dev 07 Jul 00:57:27 Starting task RZzLDmgyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDm8OHKDmCiYU8n_0
lhcathome-dev 07 Jul 00:58:14 Task RZzLDmgyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDm8OHKDmCiYU8n_0 postponed for 86400 seconds: VM environment needs to be cleaned up.
lhcathome-dev 07 Jul 00:58:14 Starting task 4hXLDmvyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDmMPHKDmAFBxkn_0
lhcathome-dev 07 Jul 00:59:00 Task 4hXLDmvyGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDmMPHKDmAFBxkn_0 postponed for 86400 seconds: VM environment needs to be cleaned up.
lhcathome-dev 07 Jul 00:59:00 Starting task WdcNDm3yGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDmVPHKDmxEUqvn_0
lhcathome-dev 07 Jul 00:59:46 Task WdcNDm3yGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDmVPHKDmxEUqvn_0 postponed for 86400 seconds: VM environment needs to be cleaned up.
lhcathome-dev 07 Jul 00:59:46 Starting task AHFNDmKzGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDmlPHKDm6SHoen_0
lhcathome-dev 07 Jul 01:00:31 Task AHFNDmKzGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDmlPHKDm6SHoen_0 postponed for 86400 seconds: VM environment needs to be cleaned up.
lhcathome-dev 07 Jul 01:00:31 Starting task 3KmLDmC0GT1n7Olcko1bjSoqABFKDmABFKDmKFbSDmcQHKDm82B66m_0
lhcathome-dev 07 Jul 01:01:15 Task 3KmLDmC0GT1n7Olcko1bjSoqABFKDmABFKDmKFbSDmcQHKDm82B66m_0 postponed for 86400 seconds: VM environment needs to be cleaned up.
lhcathome-dev 07 Jul 01:01:15 Starting task xAPNDmjzGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDmAQHKDmssqy8n_0
lhcathome-dev 07 Jul 01:02:00 Task xAPNDmjzGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDmAQHKDmssqy8n_0 postponed for 86400 seconds: VM environment needs to be cleaned up.
lhcathome-dev 07 Jul 01:02:00 Starting task iArLDm3zGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDmTQHKDmZaRlQn_0
lhcathome-dev 07 Jul 01:02:45 Task iArLDm3zGT1n7Olcko1bjSoqABFKDmABFKDmKFbSDmTQHKDmZaRlQn_0 postponed for 86400 seconds: VM environment needs to be cleaned up.

Theory vboxwrapper204 in Production AND Theory in -dev?
I making a test today!
Theory
VBoxService 5.2.6 r120293 (verbosity: 0) linux.amd64 (Jan 15 2018 14:51:00) release log
Atlas
VBoxService 5.2.32 r132073 (verbosity: 0) linux.amd64 (Jul 12 2019 10:32:28) release log

I have to add, that I had the User Interface VirtualBox Manager open during the test.

Does it also happen when you keep the VirtualBox GUI closed?