Problem VirtualBox zombi.
/usr/bin/vboxmanage controlvm or-prodtest reset
[!] FAILED calling virtualBox->OpenExistingSession (session, uuid) at line 5536!
[!] Primary RC = E_ACCESSDENIED (0×80070005) – Access denied
[!] Full error info present: true , basic error info present: true
[!] Result Code = E_ACCESSDENIED (0×80070005) – Access denied
[!] Text = The machine 'or-prodtest' does not have an open session
[!] Component = Machine, Interface: IMachine, {f95c0793-7737-49a1-85d9-6da81097173b}
[!] Callee = IVirtualBox, {2d3b9ea7-25f5-4f07-a8e1-7dd7e0dcf667}
I usually screw up the state of the machine by going to start it up without the -vrdp option and then trying to ctrl-c out of it in time. You can find the defunct VirtualBox process. Caution this is a heavy hammer and is presented only as an alternative to the system restart described in the bug title – there’s almost always a way to avoid a system restart in linux.
ps -ef | grep Virtu
machines 3761 1 0 Nov19 ? 00:00:01 /opt/VirtualBox-1.4.0/VBoxXPCOMIPCD
machines 3765 1 0 Nov19 ? 00:00:05 /opt/VirtualBox-1.4.0/VBoxSVC –automate
machines 19548 3765 0 10:32 ? 00:00:00 [VirtualBox] <defunct>
machines@mox:~/.VirtualBox/Machines/propt$ kill -9 3765
machines@mox:~/.VirtualBox/Machines/propt$ ps -ef | grep Virtu
machines 3761 1 0 Nov19 ? 00:00:01 /opt/VirtualBox-1.4.0/VBoxXPCOMIPCD
machines 24568 17657 0 10:55 pts/5 00:00:00 grep Virtu
machines@mox:~/.VirtualBox/Machines/propt$
kill -9 3765