Message boards :
Theory Application :
New version v300.94
Message board moderation
Author | Message |
---|---|
![]() Send message Joined: 20 Jun 14 Posts: 401 Credit: 238,712 RAC: 0 ![]() ![]() |
The version fixes the local proxy issues reported a few days ago. |
Send message Joined: 27 Jan 17 Posts: 5 Credit: 5,686,037 RAC: 3,937 ![]() ![]() ![]() |
I am able to run Theory tasks again, but it's still putting the virtualbox directory in /Library/Application Support/BOINC Data/projects/virtualbox, which I thought was being fixed. Or did it just detect and re-use the directory that was left over by an ATLAS job? The owner of the virtualbox directory is still boinc_project, which is going to annoy the BOINC client file ownership check. (which could be left over from ATLAS creating the directory) |
![]() Send message Joined: 15 Jun 08 Posts: 2636 Credit: 277,000,235 RAC: 145,594 ![]() ![]() |
It's a bit more complex. ATLAS is still using an outdated vboxwrapper (don't know when they replace it). VirtualBox uses the profile set by the first vbox component starting up. This can be the GUI, vboxmanage or vboxheadless. The profile is in use until the background process vboxsvc times out, usually a couple of seconds after the components just mentioned are finished. This means: When BOINC starts a vbox app using an old vboxwrapper first, the wrong profile location will be used. When BOINC starts a vbox app using a new vboxwrapper (>=26210) first, the correct profile location will be used. This is a per user limitation. So, this affects all vbox tasks from various projects running under the same user account. Simple rule: first vboxwrapper wins A temporary workaround could be: Replace the old vboxwrapper file with the recent one but keep the old name. In the <options> section of cc_config.xml set <dont_check_file_sizes>1</dont_check_file_sizes>. Then reload config files. This shouldn't be used long term as you won't get automatic app updates for all projects any more. |
©2025 CERN