VBoxManage Crashes VBoxSVC

[seano2]

Hi

We have recently upgraded from 4.0.16 to 4.1.24 on Solaris 10 x86u10. Once upgraded we noticed that the VBoxSVC is crashing fairly often (every 2 days), which in turn forces all the VBoxHeadless sessions to terminate. The broker we have unfortunately issues quite a few VBoxManage commands to establish the status of various VM's and this is what causes the crash of VBoxSVC. There are no particular parameters that do this, as they all work for about a day, its just when there are multiple (VBoxManage) commands issued at the same time that issue arises. This didn't happen on 4.0.16 and we had months and months of uptime with the same broker.

We have other users on the same server that don't have VBoxManage commands issues against them when running and these are stable and have no issue, it is definitely related to the volume of commands that the problem occurs. The VBoxSVC log doesn't seem to have anything useful in it.

Has anyone experienced similar problems or have a recommended solution to this ?

Sean

[noteirak]

Could you still attach as a zip file the VBoxSVC log, just to check it out?

[seano2]

Attached, I have a wrapper script waiting for the next crash but this does appear to be the log at the time of the crash.

[noteirak]

An aweful lot of this error over & over again

Code: Select all

ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={Machine} aText={The object functionality is limited}, preserve=false

What is this repeated operation that you are trying to perform? This is repeated almost every second.
The machine UUID is 5eaa9319-62fc-4b0a-843c-0cb1940f8a91

[seano2]

A few things I noticed things here,

1) broker is not calling VirtualBox that often (maybe every 5 seconds), so these entries are generated on their own accord.
2) that UUID {5eaa9319-62fc-4b0a-843c-0cb1940f8a91} doesn't exist on the server at all , vms or hdds, it seems to be an internal UUID as other forum entries refer to the same UUID, and it appears on other servers I have too.
3) I know with 100% certainty that the broker, is not explicitly calling any snapshot functionality, so I am not sure why there is reference to this in the log.

30:02:31.111 nspr-2 ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={SessionMachine} aText={This machine does not have any snapshots}, preserve=false

bash-3.00$ VBoxManage showvminfo 5eaa9319-62fc-4b0a-843c-0cb1940f8a91
VBoxManage: error: Could not find a registered machine with UUID {5eaa9319-62fc-4b0a-843c-0cb1940f8a91}
VBoxManage: error: Details: code VBOX_E_OBJECT_NOT_FOUND (0x80bb0001), component VirtualBox, interface IVirtualBox, callee nsISupports
Context: "FindMachine(Bstr(VMNameOrUuid).raw(), machine.asOutParam())" at line 2335 of file VBoxManageInfo.cpp