Bug #5227

VM can not start due to already binded VNC address

Added by Kristian Feldsam over 3 years ago. Updated over 3 years ago.

Status:ClosedStart date:07/12/2017
Priority:HighDue date:
Assignee:-% Done:

0%

Category:Drivers - VM
Target version:-
Resolution:duplicate Pull request:
Affected Versions:OpenNebula 5.2

Description

Thu Jul 6 04:43:36 2017 [Z0][VM][I]: New state is ACTIVE
Thu Jul 6 04:43:36 2017 [Z0][VM][I]: New LCM state is PROLOG
Thu Jul 6 04:43:39 2017 [Z0][VM][I]: New LCM state is BOOT
Thu Jul 6 04:43:39 2017 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/10609/deployment.0
Thu Jul 6 04:43:39 2017 [Z0][VMM][I]: Successfully execute transfer manager driver operation: tm_context.
Thu Jul 6 04:43:39 2017 [Z0][VMM][I]: ExitCode: 0
Thu Jul 6 04:43:39 2017 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Thu Jul 6 04:43:40 2017 [Z0][VMM][I]: Command execution fail: cat << EOT | /var/tmp/one/vmm/kvm/deploy '/var/lib/one//datastores/110/10609/deployment.0' 'node1.feldhost.cz' 10609 node1.feldhost.cz
Thu Jul 6 04:43:40 2017 [Z0][VMM][I]: error: Failed to create domain from /var/lib/one//datastores/110/10609/deployment.0
Thu Jul 6 04:43:40 2017 [Z0][VMM][I]: error: internal error: process exited while connecting to monitor: 2017-07-06T08:43:40.649149Z qemu-kvm: -vnc 0.0.0.0:10609: Failed to start VNC server: Failed to bind socket: Address already in use
Thu Jul 6 04:43:40 2017 [Z0][VMM][E]: Could not create domain from /var/lib/one//datastores/110/10609/deployment.0
Thu Jul 6 04:43:40 2017 [Z0][VMM][I]: ExitCode: 255
Thu Jul 6 04:43:40 2017 [Z0][VMM][I]: Failed to execute virtualization driver operation: deploy.
Thu Jul 6 04:43:40 2017 [Z0][VMM][E]: Error deploying virtual machine: Could not create domain from /var/lib/one//datastores/110/10609/deployment.0
Thu Jul 6 04:43:40 2017 [Z0][VM][I]: New LCM state is BOOT_FAILURE

Related issues

Duplicates Backlog #5125: Support for VNC/SPICE autoport rather than tracking in Op... Pending 04/23/2017

History

#1 Updated by Ruben S. Montero over 3 years ago

Hi

Right now in OpenNebula we track the VNC ports used cluster-wise. Do you have any hint of who is using that port? Is it a VM, was it launch through OpenNebula. Note that if the port is being used by a well known service, you can reserved that port so it is not assgined to a VM.

This port management is going to be re-worked to use the qemu/libvirt facilities as described here #5125

#2 Updated by Kristian Feldsam over 3 years ago

hi, port is not used, but I think about folowing scenario:

throught API VM is created, VM is shutdowned, another VM is created with sam eport as shutdowning VM....

it occurs only when VMs are instanciated throught gitlab autoscaling docker-machine runner, which sometimes go mental and creates and deletes VMs....

#3 Updated by Ruben S. Montero over 3 years ago

OK,then this needs to be addressed as in #5125. I'll closed this so we can refer to any further input to the auto port feature.

#4 Updated by Ruben S. Montero over 3 years ago

  • Status changed from Pending to Closed
  • Resolution set to duplicate

#5 Updated by Ruben S. Montero over 3 years ago

  • Duplicates Backlog #5125: Support for VNC/SPICE autoport rather than tracking in OpenNebula added

Also available in: Atom PDF