Bug #3885

Failed to start VNC server... socket bind failed: Address already in use

Added by Anonymous over 5 years ago. Updated over 5 years ago.

Status:ClosedStart date:07/22/2015
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Resolution:duplicate Pull request:
Affected Versions:OpenNebula 4.12

Description

Hi, we have a problem with clashing VNC Ports...

2015-07-21T01:45:25.113700Z qemu-kvm: Failed to start VNC server on `0.0.0.0:36395': socket bind failed: Address already in use

We have machine ids of 96030 and counting. With this problem our full automated vm environment gets stuck on some vms.
Am I right in thinking that OpenNebula calculates the VNC port as start_of_ephemeral_range + vm_id ?


Related issues

Duplicates Feature #2475: Reserve a VNC port number Closed 11/19/2013

History

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

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

Yes that's right. For now you need to fix the port for those VM's

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

Also available in: Atom PDF