[Rocks-Discuss] vncviewer connection refused

609 views
Skip to first unread message

Joe Kaiser

unread,
Apr 10, 2008, 1:02:59 PM4/10/08
to ROCKS List
Hi,

When installing worker nodes, the display is started and when I
attempt to connect via vncviewer I get the following:


VNC viewer for X version 4.0 - built Feb 21 2005 14:12:44
Copyright (C) 2002-2004 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.

Thu Apr 10 11:52:48 2008
main: unable to connect to host: Connection refused (111)

[1]+ Done vncviewer cmswn121:1


How is the mechanism started on the node and the server to get the
channel working?

Thanks,

Joe

--
++++++++++++++++++++++++++++++++++++++
Joe Kaiser

Godot isn't coming.
+++++++++++++++++++++++++++++++++++++

Greg Bruno

unread,
Apr 10, 2008, 1:27:22 PM4/10/08
to jlka...@fnal.gov, ROCKS List
On Thu, Apr 10, 2008 at 10:02 AM, Joe Kaiser <jlka...@fnal.gov> wrote:
> Hi,
>
> When installing worker nodes, the display is started and when I
> attempt to connect via vncviewer I get the following:
>
>
> VNC viewer for X version 4.0 - built Feb 21 2005 14:12:44
> Copyright (C) 2002-2004 RealVNC Ltd.
> See http://www.realvnc.com for information on VNC.
>
> Thu Apr 10 11:52:48 2008
> main: unable to connect to host: Connection refused (111)
>
> [1]+ Done vncviewer cmswn121:1
>
>
> How is the mechanism started on the node and the server to get the
> channel working?

it uses an ssh tunnel.

try:

# ssh cmswn121 -p 2200

if that works, then 'rocks-console cmswn121' should work.

- gb

Joe Kaiser

unread,
Apr 10, 2008, 2:14:53 PM4/10/08
to Greg Bruno, ROCKS List
> it uses an ssh tunnel.
>
> try:
>
> # ssh cmswn121 -p 2200
>
> if that works, then 'rocks-console cmswn121' should work.
>
> - gb
>

That works.

Greg Bruno

unread,
Apr 10, 2008, 2:50:20 PM4/10/08
to jlka...@fnal.gov, ROCKS List
On Thu, Apr 10, 2008 at 11:14 AM, Joe Kaiser <jlka...@fnal.gov> wrote:
> > it uses an ssh tunnel.
> >
> > try:
> >
> > # ssh cmswn121 -p 2200
> >
> > if that works, then 'rocks-console cmswn121' should work.
> >
> > - gb
> >
>
> That works.

after you login to the node with 'ssh cmswn121 -p 2200', send us the output of:

# ls /tmp/X*
# ps auwx | grep X

- gb

Joe Kaiser

unread,
Apr 14, 2008, 3:28:04 PM4/14/08
to Greg Bruno, ROCKS List

Hi,

Sorry it took so long.

bash-3.00# ls /tmp/X*
ls: /tmp/X*: No such file or directory

-bash-3.00# ps auxww | grep X
root 599 0.0 0.4 8784 5072 pts/0 S+ 14:24 0:00
//usr/bin/Xvnc :1 -nevershared -depth 16 -geometry 800x600
IdleTimeout=0 -auth /dev/null -once DisconnectClients=false
desktop=Rocks 0.0.0 installation on host 131.225.207.194
SecurityTypes=None
-bash-3.00#

Greg Bruno

unread,
Apr 14, 2008, 4:19:37 PM4/14/08
to jlka...@fnal.gov, ROCKS List
On Mon, Apr 14, 2008 at 12:28 PM, Joe Kaiser <jlka...@fnal.gov> wrote:
>
> Sorry it took so long.
>
> bash-3.00# ls /tmp/X*
> ls: /tmp/X*: No such file or directory
>
> -bash-3.00# ps auxww | grep X
> root 599 0.0 0.4 8784 5072 pts/0 S+ 14:24 0:00
> //usr/bin/Xvnc :1 -nevershared -depth 16 -geometry 800x600
> IdleTimeout=0 -auth /dev/null -once DisconnectClients=false
> desktop=Rocks 0.0.0 installation on host 131.225.207.194
> SecurityTypes=None
> -bash-3.00#

i'm guessing this is a headless node.

if so, you may want to try creating a 'pre' section in an
extend-compute.xml that looks like:

<pre>
vncconfig -display=:1 -set localhost=1
</pre>

then rebuild your distro and reinstall a compute node.

the above pre section should tell Xvnc on the installing node to
accept connections from the localhost. 'rocks-console' sends X events
to the installer via a ssh tunnel, so when Xvnc receives the events,
it thinks the events are coming from the localhost. setting
'localhost=1' tells Xvnc to accept VNC sessions only from the
localhost.

- gb

Reply all
Reply to author
Forward
0 new messages