Bug 1322155

Summary:	Xorg socket conflict for VNC port 5901
Product:	Red Hat Enterprise Linux 7	Reporter:	Joe Wright <jwright>
Component:	tigervnc	Assignee:	Jan Grulich <jgrulich>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	7.2	CC:	mkolbas, tpelka
Target Milestone:	rc	Keywords:	Desktop, Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-04 01:30:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Joe Wright 2016-03-29 22:44:13 UTC

Description of problem:
- VNC will not start on port 5901 because of a socket conflict

Version-Release number of selected component (if applicable):
- tigervnc-server-1.3.1-3.el7
- xorg-x11-server-Xorg-1.17.2-10.el7

How reproducible:
- clean installation of RHEL 7.2 "server with GUI"
- clean installation of tigervnc-server
- configure unit file for vncserver@:1.service for user
- set vncpassword for user
- enable and start daemon
- daemon fails as follows:
Warning:<hostname>:1 is taken because of /tmp/.X11-unix/X1
Remove this file if there is no X server <hostname>:1
A VNC server is already running as :1


Actual results:
- vncserver will not start on this port

Expected results:
- vncserver starts on port 5901

Additional info:

Find display number:

if ((@ARGV > 0) && ($ARGV[0] =~ /^:(\d+)$/)) {
    $displayNumber = $1;
    shift(@ARGV);
    if (!&CheckDisplayNumber($displayNumber)) {
        die "A VNC server is already running as :$displayNumber\n";
    }
} elsif ((@ARGV > 0) && ($ARGV[0] !~ /^-/) && ($ARGV[0] !~ /^\+/)) {
    &Usage();
} else {
    $displayNumber = &GetDisplayNumber();
}

$vncPort = 5900 + $displayNumber;

Looks like its just dying instead of moving to the next display

Comment 4 Jan Grulich 2016-05-24 15:48:23 UTC

Fixed in tigervnc-1.3.1-6.el7.

Comment 8 errata-xmlrpc 2016-11-04 01:30:12 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2237.html