ssh -X : connect /tmp/.X11-unix/X0: No such file or directory

ssh -X : connect /tmp/.X11-unix/X0: No such file or directory

[Ronald Fischer]

My setup so far (which is working well), was to use Xming as X-Server
and putty for logging into our Solaris hosts via ssh. Since I have
Cygwin installed, I thought I could use its ssh equally well, so I
exported the ssh key from putty to the format understood by ssh, and
used the following bash command to login to the Solaris host:

  DISPLAY=:0.0 TERM=xterm  ssh -p 22 -K -X -i MyPrivateKeyFile 
  MyUserName@SolarisHost

When I now try to start an X application, I get an error message like
this 

 connect /tmp/.X11-unix/X0: No such file or directory 
 XIO:  fatal IO error 131 (Connection reset by peer) on X server
 "SolarisHost:239.0"
       after 0 requests (0 known processed) with 0 events remaining.

Further investigation reveals the following:

(1) I start my putty login, and find that on the remote host DISPLAY is
set to (say): SolarisHost:261.0
Starting X applications works fine.

(2) I start my open ssh login from Cygwin, and find that the DISPLAY
variable is set to a different value, for example SolarisHost:239.0 .
Starting X applications does not work.

(3) In the latter shell, I export DISPLAY=SolarisHost:261.0 . Starting X
applications now works. 

The fact that each login produces a different value for DISPLAY, is
normal behaviour. Even when starting several putty sessions, each gets a
different value for DISPLAY, and X apps work in all of them.

It seems that by doing the ssh connection via putty, something is done
which is missing from my ssh started from Cygwin. 

BTW, I also tried to use -Y instead of -X in my ssh invocation, but with
no effect.

Ronald
-- 
Ronald Fischer <ronaldf@eml.cc>
+  If a packet hits a pocket on a socket on a port, 
+  and the bus is interrupted and the interrupt's not caught,
+  then the socket packet pocket has an error to report.
+		(cited after Peter van der Linden)


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/

Re: ssh -X : connect /tmp/.X11-unix/X0: No such file or directory

[Jon TURNEY]

On 20/04/2012 11:43, Ronald Fischer wrote:
> My setup so far (which is working well), was to use Xming as X-Server
> and putty for logging into our Solaris hosts via ssh. Since I have
> Cygwin installed, I thought I could use its ssh equally well, so I
> exported the ssh key from putty to the format understood by ssh, and
> used the following bash command to login to the Solaris host:
> 
>   DISPLAY=:0.0 TERM=xterm  ssh -p 22 -K -X -i MyPrivateKeyFile 
>   MyUserName@SolarisHost
> 
> When I now try to start an X application, I get an error message like
> this 
> 
>  connect /tmp/.X11-unix/X0: No such file or directory 
>  XIO:  fatal IO error 131 (Connection reset by peer) on X server
>  "SolarisHost:239.0"
>        after 0 requests (0 known processed) with 0 events remaining.

I think I know what's going on here.

cygwin ssh understands DISPLAY=:0.0 to mean to connect to the X server for
display 0 via a local (UNIX domain) socket, named /tmp/.X11-unix/X0

The Xming X server, not being a cygwin application, cannot listen on that socket.

The solution should be to use DISPLAY=localhost:0.0 instead, which means to
connect to the X server for display 0 via TCP/IP, which the Xming X server
should be listening on.

See FAQ 1.6 [1] for more details.

[1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#display-and-screen

-- 
Jon TURNEY
Volunteer Cygwin/X X Server maintainer

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/

Re: ssh -X : connect /tmp/.X11-unix/X0: No such file or directory

[Ronald Fischer]

On Fri, Apr 20, 2012, at 19:53, Jon TURNEY wrote:
> On 20/04/2012 11:43, Ronald Fischer wrote:
> > My setup so far (which is working well), was to use Xming as X-Server
> > and putty for logging into our Solaris hosts via ssh. Since I have
> > Cygwin installed, I thought I could use its ssh equally well, so I
> > exported the ssh key from putty to the format understood by ssh, and
> > used the following bash command to login to the Solaris host:
> > 
> >   DISPLAY=:0.0 TERM=xterm  ssh -p 22 -K -X -i MyPrivateKeyFile 
> >   MyUserName@SolarisHost
> > 
> > When I now try to start an X application, I get an error message like
> > this 
> > 
> >  connect /tmp/.X11-unix/X0: No such file or directory 
> >  XIO:  fatal IO error 131 (Connection reset by peer) on X server
> >  "SolarisHost:239.0"
> >        after 0 requests (0 known processed) with 0 events remaining.
> 
> I think I know what's going on here.
> 
> The solution should be to use DISPLAY=localhost:0.0 instead, which means
> to
> connect to the X server for display 0 via TCP/IP, which the Xming X
> server
> should be listening on.

Nice idea, but the result is, that I just get a different error message.
Now it becomes:

 connect localhost port 6000: Connection refused 
 X connection to SolarisHost:217.0 broken (explicit kill or server
 shutdown).

>From the FAQ, I see that port 6000 is the default. Could it be that I
need to specify somehow a non-standard port? 

Ronald
-- 
Ronald Fischer <ronaldf@eml.cc>
+  If a packet hits a pocket on a socket on a port, 
+  and the bus is interrupted and the interrupt's not caught,
+  then the socket packet pocket has an error to report.
+		(cited after Peter van der Linden)


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/