I had to abort a task that was dead with .12% being used on the cpu
turns out that was strike 3
had a canceled by server (since when does that count against you?)
a computation error (their fault) and my abort.

2022-04-15 13:22:17 (15696): Detected: BOINC client v7.16.20
2022-04-15 13:22:19 (15696): Detected: VirtualBox VboxManage Interface (Version: 6.1.32)
2022-04-15 13:22:20 (15696): WARNING: Communication with VM Hypervisor failed. (Possibly Out of Memory).
2022-04-15 13:22:20 (15696): WARNING: Communication with VM Hypervisor failed.
2022-04-15 13:22:20 (15696): ERROR: VBoxManage list hostinfo failed

huh? WTF is this?

robertmiles wrote:

Virtualbox has the old vbox, which handles 32-bit programs
.
.
.
Where's any evidence that the multicore Cosmology tasks use Virtualbox?

It's mentioned at the apps overview page of any project:
https://boinc.bakerlab.org/rosetta/apps.php
https://www.cosmologyathome.org/apps.php


no "()" in the "Version" col indicates a native/legacy app without special requirements like SSE, AVX ...
(vbox64) in the "Version" col indicates an app that requires VirtualBox 64-bit.
(vbox64_mt) in the "Version" col indicates an app that requires VirtualBox 64-bit and is able to run multicore VMs.
64-bit vbox apps don't run on a computer that has 32-bit vbox installed.

Thank you.

It looks like Cosmology@Home ran out of space to write this in the other place where I expected it to appear.

I'm now back after a week with no internet access.

My computer has both the 64-bit and the 32-bit versions of VirtualBox installed. It runs 64-bit vbox apps.

My computer has both the 64-bit and the 32-bit versions of VirtualBox installed. It runs 64-bit vbox apps.

This is news to me, I just have 64 bit installed, I think, no idea how to find out. Does that mean I can't run the 32 bit ones? I would have thought the 64 would include the 32?

My computer has both the 64-bit and the 32-bit versions of VirtualBox installed. It runs 64-bit vbox apps.

This is news to me, I just have 64 bit installed, I think, no idea how to find out. Does that mean I can't run the 32 bit ones? I would have thought the 64 would include the 32?

My 32-bit version may be left over from the earlier BOINC work that used it, such as RNA World. It's a separate program.

If you can reach the command line while no Virtualbox task is running, Try entering vbox to test if the 32-bit version can be found. If the program starts, try entering exit to see if this will shut it down. For a similar test for the 64-bit version, enter vbox64 instead.

When i run vbox i get "vbox" is not recognized as an internal or external command operable program or batch file
The same happens to "vbox64"

When i run vbox i get "vbox" is not recognized as an internal or external command operable program or batch file
The same happens to "vbox64"

I guessed wrong on how to start the emulators, then.

Or maybe neither is available for your Android computer.

I have https://download.virtualbox.org/virtualbox/5.2.44/VirtualBox-5.2.44-139111-Win.exe installed

My computer has both the 64-bit and the 32-bit versions of VirtualBox installed. It runs 64-bit vbox apps.

This is news to me, I just have 64 bit installed, I think, no idea how to find out. Does that mean I can't run the 32 bit ones? I would have thought the 64 would include the 32?

My 32-bit version may be left over from the earlier BOINC work that used it, such as RNA World. It's a separate program.

If you can reach the command line while no Virtualbox task is running, Try entering vbox to test if the 32-bit version can be found. If the program starts, try entering exit to see if this will shut it down. For a similar test for the 64-bit version, enter vbox64 instead.

Not sure what you mean. Where do I enter this? I'm running Windows 11.

I have https://download.virtualbox.org/virtualbox/5.2.44/VirtualBox-5.2.44-139111-Win.exe installed

Same. I assume that's 64 bit. The website doesn't say.

My computer has both the 64-bit and the 32-bit versions of VirtualBox installed. It runs 64-bit vbox apps.

This is news to me, I just have 64 bit installed, I think, no idea how to find out. Does that mean I can't run the 32 bit ones? I would have thought the 64 would include the 32?

My 32-bit version may be left over from the earlier BOINC work that used it, such as RNA World. It's a separate program.

If you can reach the command line while no Virtualbox task is running, Try entering vbox to test if the 32-bit version can be found. If the program starts, try entering exit to see if this will shut it down. For a similar test for the 64-bit version, enter vbox64 instead.

Not sure what you mean. Where do I enter this? I'm running Windows 11.

Sorry, I have no information on whether Windows 11 even makes a way to do it available.

Not sure what you mean. Where do I enter this? I'm running Windows 11.

On the command line - type window-R then enter cmd in the text box that comes up.

Not sure what you mean. Where do I enter this? I'm running Windows 11.

On the command line - type window-R then enter cmd in the text box that comes up.

Yes I know how to get a command line. But I assumed this was the wrong place as:

C:Userspeter>vbox
'vbox' is not recognized as an internal or external command,
operable program or batch file.

C:Userspeter>vbox64
'vbox64' is not recognized as an internal or external command,
operable program or batch file.

(Note the backslashes have been removed because this forum is a piece of shit)

This forum removes three of four backslashes.
every four backslashes equate to one displayed.
\

This forum removes three of four backslashes.
every four backslashes equate to one displayed.
\

Yeah I used to do that, now I just can't be bothered. Why can't the programmers of the forum make it just work?

Recently getting many units that say 'error while computing'. Is this a common issue or is it possibly my hardware?

---

Recently getting many units that say 'error while computing'. Is this a common issue or is it possibly my hardware?

You only seem to have one error reported, and it says "chi angle must be between -180 and 180" - I've seen that before, it's Rosetta's problem not yours. Any of the 4.2 tasks going wrong are their fault.

Python can go wrong if your computer doesn't have Virtualbox set up right, or is an older processor without AVX.

Hello,

My python tasks are continually failing. Any help appreciated.

1482401603 1318790836 13 Apr 2022, 23:59:43 UTC 17 Apr 2022, 0:00:23 UTC Not started by deadline - canceled 0.00 0.00 --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1482405713 1318794923 13 Apr 2022, 23:59:43 UTC 17 Apr 2022, 0:00:23 UTC Not started by deadline - canceled 0.00 0.00 --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1482399717 1318788959 13 Apr 2022, 23:59:43 UTC 17 Apr 2022, 0:00:23 UTC Not started by deadline - canceled 0.00 0.00 --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1482394992 1318784644 13 Apr 2022, 22:35:23 UTC 16 Apr 2022, 22:35:29 UTC Not started by deadline - canceled 0.00 0.00 --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1482387483 1318778078 13 Apr 2022, 18:57:38 UTC 16 Apr 2022, 18:58:21 UTC Not started by deadline - canceled 0.00 0.00 --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1482387339 1318777972 13 Apr 2022, 18:57:38 UTC 16 Apr 2022, 18:58:21 UTC Not started by deadline - canceled 0.00 0.00 --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1482379340 1318774461 13 Apr 2022, 15:42:54 UTC 16 Apr 2022, 15:43:22 UTC Not started by deadline - canceled 0.00 0.00 --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1482378634 1318774035 13 Apr 2022, 15:42:54 UTC 16 Apr 2022, 15:43:22 UTC Not started by deadline - canceled 0.00 0.00 --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1482376733 1318772964 13 Apr 2022, 13:08:45 UTC 16 Apr 2022, 13:08:45 UTC Timed out - no response 0.00 0.00 --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1482376781 1318772997 13 Apr 2022, 13:08:45 UTC 16 Apr 2022, 13:08:45 UTC Timed out - no response 0.00 0.00 --- rosetta python projects v1.03 (vbox64)
windows_x86_64
1482376842 1318773032 13 Apr 2022, 13:08:45 UTC 16 Apr 2022, 13:08:45 UTC Timed out - no response 0.00 0.00 --- rosetta python projects v1.03 (vbox64)
windows_x86_64

Hello,

My python tasks are continually failing. Any help appreciated.

The log says it all

Not started by deadline - canceled

The deadline for Rosetta Tasks is 3 days.
Your cache is excessive, especially so considering you are running multiple projects. Set your cache to 0.05 days and 0.01 additional days and you'll start returning work before it's too late.

However there are other issues with Python Tasks that will likely result in some Tasks failing or not being completed in time.
But that's a whole different issue.

---

Grant
Darwin NT

Hello,

My python tasks are continually failing. Any help appreciated.

The log says it all

Not started by deadline - canceled

The deadline for Rosetta Tasks is 3 days.
Your cache is excessive, especially so considering you are running multiple projects. Set your cache to 0.05 days and 0.01 additional days and you'll start returning work before it's too late.

However there are other issues with Python Tasks that will likely result in some Tasks failing or not being completed in time.
But that's a whole different issue.

They're not too bad if you have AVX. I only have to cancel about 1 in 20.

Thank you. I have changed the settings. I am not sure what you mean by "They're not too bad if you have AVX."