Bug #5389
Vnc tries to bind to wrong port number
| Status: | Pending | Start date: | 09/22/2017 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 5.6 | |||
| Resolution: | Pull request: | |||
| Affected Versions: | OpenNebula 5.4 |
Description
On random occasions VM-s are started with wrong VNC port number:
In oned.conf
VNC_PORTS = [
START = 15900
# RESERVED = "6800, 6801, 6810:6820, 9869"
]
And VM with ID 2613 fails to boot with error message:
qemu-system-x86_64: -vnc 0.0.0.0:12613: Failed to start VNC server: Failed to bind socket: Address already in use
So sometimes OpenNebula tries to iniatie vnc with port 10000 +VMID, instead of 15900 +VMID as set in configuration.
Related issues
History
#1
Updated by Ruben S. Montero over 3 years ago
- Category set to Core & System
- Target version set to Release 5.6
#2
Updated by Ruben S. Montero over 3 years ago
- Related to Backlog #5125: Support for VNC/SPICE autoport rather than tracking in OpenNebula added