Bug 562669
| Summary: | service vncserver start only starts one display | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Saar <saar.maoz> | ||||||
| Component: | tigervnc | Assignee: | Tim Waugh <twaugh> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | 6.0 | CC: | ofourdan, ovasik, psklenar | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | tigervnc-1.1.0-9.el6 | Doc Type: | Bug Fix | ||||||
| Doc Text: |
When more than one display was configured in /etc/sysconfig/vncservers, the vncserver initscript would stop on error. This meant a problem with one display would prevent other displays from being started.
The initscript now attempts to start each configured display.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2014-10-14 04:38:44 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 782183, 949522, 994246 | ||||||||
| Attachments: |
|
||||||||
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was erroneously denied for the current release of Red Hat Enterprise Linux. The error has been fixed and this request has been re-proposed for the current release. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Since RHEL 5 is now in production phase 2 (only important/critical issues are addressed) and this is not important issue, I'm moving this ticket to RHEL-6 because issue is still present there. *** Bug 768405 has been marked as a duplicate of this bug. *** Created attachment 882346 [details]
Here is the change I plan to make
Created attachment 882360 [details]
Here is the change I plan to make (sorry, missed a bit in the last one)
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. http://rhn.redhat.com/errata/RHBA-2014-1412.html |
Assuming in /etc/sysconfig/vncservers you have 2 displays configured, they are running and are actively being used. Adding a 3rd display, and typing: # service vncserver start Starting VNC server: 1:root A VNC server is already running as :1 [FAILED] fails... This is because in /etc/rc.d/init.d/vncserver: for display in ${VNCSERVERS} do NOSERV= echo -n "${display} " unset BASH_ENV ENV DISP="${display%%:*}" export USER="${display##*:}" export VNCUSERARGS="${VNCSERVERARGS[${DISP}]}" runuser -l ${USER} -c "cd ~${USER} && [ -f .vnc/passwd ] && vncserver :${DISP} ${VNCUSERARGS}" RETVAL=$? ==>> [ "$RETVAL" -ne 0 ] && break done There is an exit from the loop upon the first error. If you comment out that line, the output looks more reasonable: # service vncserver start Starting VNC server: 1:root A VNC server is already running as :1 2:root A VNC server is already running as :2 3:root A VNC server is already running as :3 4:root New 'mynode:4 (root)' desktop is mynode:4 Start should follow through for all displays. you could do restart, but that kills all currently used displays which is bad.