Bug #3885
Failed to start VNC server... socket bind failed: Address already in use
| Status: | Closed | Start date: | 07/22/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due 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
History
#1
Updated by Ruben S. Montero almost 6 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 almost 6 years ago
- Duplicates Feature #2475: Reserve a VNC port number added