RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 800048 - 20second vnc connection delay in rhel6 environment
Summary: 20second vnc connection delay in rhel6 environment
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: tigervnc
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Tim Waugh
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-05 16:44 UTC by gregrwm
Modified: 2014-10-23 14:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-23 14:29:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description gregrwm 2012-03-05 16:44:22 UTC 
Description of problem:  connecting vncviewer to Xvnc via rhel6/sshd portforward causes curious 20second delay before vnc password is requested.  no such delay via rhel4/sshd.

Version-Release number of selected component (if applicable):
kernel-2.6.32-220.4.1.el6.x86_64

How reproducible:  always

Steps to Reproduce:
1.  connect ssh -L5904:localhost:5909 to rhel4/sshd
1.  connect ssh -L5906:localhost:5909 to rhel6/sshd
2.  connect vncviewer via rhel4
2.  connect vncviewer via rhel6
  
Actual results:  connecting vncviewer via rhel6/sshd always get 20second delay before vncviewer requests password.  no such delay via rhel4/sshd.  doesn't matter whether Xvnc is rhel4/5/6.

Expected results:  no delay

Additional info:  i also see 20second delay launching virt-viewer inside rhel6 Xvnc, that transaction is entirely local to the rhel6 server, sshd is not a party to that transaction.  all Xvnc sessions are running twm.
Comment 2 gregrwm 2012-03-05 17:13:34 UTC 
run rhel6 kernel
run rhel4 in a chroot:
mount  --bind /tmp  /<rhel4>/tmp
mount --rbind /dev  /<rhel4>/dev
mount --rbind /sys  /<rhel4>/sys
mount --rbind /proc /<rhel4>/proc
run Xvnc in rhel4 chroot
connect vncviewer (via portforward via rhel6 sshd)
copy ~/.Xauthority from rhel4 to rhel6 home directory
launch xterm in (rhel4) Xvnc
launch xterm from within that xterm
launch DISPLAY=localhost:<display> from rhel6
launch xterm from within that xterm

the rhel4 xterms display immediately
the rhel6 xterms display after 20second delays.  why?
Comment 4 Suzanne Logcher 2012-03-07 21:28:46 UTC 
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.  It has been proposed for the next
release. If you would like it considered as an exception in the current
release, please ask your support representative.
Comment 5 RHEL Program Management 2012-09-07 05:38:24 UTC 
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 unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 7 Petr Lautrbach 2014-05-26 07:56:41 UTC 
Since the original report is alread two years old, I'd like to ask is it still an issue with the latest RHEL updates? 

According to comment #c2, sshd is only used as port forwarder. How? Is the portfowarding channel already established? Is there any delay when you try to connect to forwarded port using netcat/telnet?
Comment 8 gregrwm 2014-05-28 23:44:58 UTC 
the problem was obviated by using ubuntu vnc instead of rhel6.  sorry i no longer have rhel6 vnc handy for testing.
Note You need to log in before you can comment on or make changes to this bug.