VirtualBox

Ticket #1619 (closed defect: fixed)

Opened 6 years ago

Last modified 5 years ago

Assertion Failed to release the client -> Fixed in 2.1.2

Reported by: mjlucas Owned by:
Priority: major Component: RDP
Version: VirtualBox 1.5.6 Keywords:
Cc: Guest type: other
Host type: other

Description

When powering off a vm an assertion was thrown by VBoxVRDP

41:29:57.892 VRDP: TCP server failed to send data to the client!!! Disconnecting the client.
41:29:57.892 VRDP: Failed to release the client. Status 0x2, Context 0x2!!!
41:29:57.892
41:29:57.892 !!Assertion Failed!!
41:29:57.892 Expression: <NULL>
41:29:57.892 Location  : /home/vbox/vbox-1.5.6/src/VBox/RDP/server/vrdpclient.cpp(340) void VRDPClient::ThreadContextRelease(int)

This put the machine into an aborted state and could not be recovered by a VBoxManage controlvm <vmname> poweroff|reset because the VBoxVRDP process had executed and there was no current session.

I had to manually change the aborted="true" value in the vm .xml file to reset this state.

What is the correct method from recovering from aborts such as these? Manually having to edit the xml file is a sloppy.

Attachments

VBox.log.vrdpassert Download (102.7 KB) - added by mjlucas 6 years ago.
Log file from crash (Last few lines after poweroff)

Change History

Changed 6 years ago by mjlucas

Log file from crash (Last few lines after poweroff)

comment:1 Changed 6 years ago by frank

AFAIR you don't need to recover from the aborted state as it should be handled like the powered off state. You should be able to just start aborted VMs.

comment:2 Changed 6 years ago by frank

  • Component changed from other to RDP

comment:3 Changed 5 years ago by sunlover

  • Status changed from new to closed
  • Resolution set to fixed
  • Summary changed from Assertion Failed to release the client to Assertion Failed to release the client -> Fixed in 2.1.2

Should be fixed in 2.1.2. Please reopen if the problem persists.

comment:4 Changed 5 years ago by mld

  • Status changed from closed to reopened
  • Resolution fixed deleted

I just got this error with virtualbox 2.1.4 on debian lenny. Was not able to get a core dump. I'm pretty sure this is the first time this has happened since I installed 2.1.4 a few months ago.

80:03:06.346 VRDP: TCP server failed to send data to the client!!! Disconnecting the client.
80:03:06.385 VBVA: VRDP acceleration has been disabled.
80:03:06.460 VRDP: Failed to release the client. Status 0xff357c30, Context 0x2!!!
80:03:06.460 
80:03:06.460 !!Assertion Failed!!
80:03:06.460 Expression: <NULL>
80:03:06.460 Location  : /home/vbox/vbox-2.1.4/src/VBox/RDP/server/vrdpclient.cpp(329) void VRDPClient::ThreadContextRelease(int)

Last RDP log message before this is:

79:46:24.870 VRDP: Received the Disconnect Request packet.
79:46:24.870 VRDP: Connection closed: 
79:46:29.894 VRDP: DisableStatus timed out 5000!!!
79:46:29.894 VRDP: Logoff: localhost (192.168.1.5) build 2600. User: [theuser] Domain: [] Reason 0x0001.

comment:5 Changed 5 years ago by MrX1980

Please try it with v3.0.0 again.

comment:6 Changed 5 years ago by mjlucas

This can likely be re-closed. The bug I originally reported was found and fix in 2.1.2 (as per the title)

Perhaps the Asset can be changed to be just a logged error (with the appropriate cleanup of resources on the server side). There could be many reasons why the client does not disconnect correctly which are out of the control of VBoxHeadless.

comment:7 Changed 5 years ago by frank

  • Status changed from reopened to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use