This is pretty easy to understand and replicate, but there is a number of moving parts. Improve this answer. The followup question: Why doesn't sysdig see it? Assuming you meant strace. You say that you straced the ssh server sshd. You need to strace the ssh client running on local, ssh. Shouldn't both strace and sysdig see it? It won't see it when you run it on the ssh server command sshd. Add a comment. Sign up or log in Sign up using Google. Sign up using Facebook.
Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Making Agile work for data science. Stack Gives Back Featured on Meta. New post summary designs on greatest hits now, everywhere else eventually.
Linked Related 1. Hot Network Questions. Question feed. Asked 4 years, 3 months ago. Active 2 years, 9 months ago. Viewed 8k times. Improve this question. Tom Tom 13 1 1 silver badge 4 4 bronze badges. Please edit your question to include exactly how you are ssh'ing to the remote host - including any command line options — steeldriver. I believe those messages are not related to the X11 issue at all. If they are, it is not obvious. Please do provide the details, both the ssh command line and the command you execute on the remote system that starts an X11 application.
Add a comment. Active Oldest Votes. Improve this answer. Dave Dave 26 4 4 bronze badges. Thanks this works perfectly! The catch: That fallback behaviour doesn't happen when ssh is redirecting a connection from the remote side, so you are getting that error. It doesn't try the fallback connection to TCP localhost.
Like other answers mention, you can also export that variable interactively from your shell prompt:. You can also store this setting more permanently by adding that line to your login shell profile initialization script e. Note: Some shells have a different initialization script for login and non-login sessions. For instance, with bash you could write that line to the non-login script, i. If you do, be careful not to override any custom value that might have been set by ssh.
That would be the case if you were hopping first into your host via ssh and then hopping again into another host thus nesting your X11 forwarding. If your display host happens to be macOS , make sure you have XQuartz running.
This error message is telling you the ssh tunnel is working, but it can't figure out how to connect to the X server on your side of the tunnel. In the good old days, Mac OS X used to start XQuartz for you, but we have apparently abandoned this nice little feature in the macOS version of terminal.
I just had the same problem. The confusing thing is that you get the no-such-file error on the remote machine, but actually this file is missing on the local display machine. Just to see what would happen, I manually created the missing file fifo, actually , on the display machine, like this:.
I don't know if this is relevant or not, but my display machine is not Linux, it's Windows with cygwin and VcXsrv. The remote machine is Linux. I ran into this problem using the Windows Subsystem for Linux. To test if you have a GUI, execute xclock on the client.
I used Xserver. Now try ssh'ing into the server, then running xclock. That's because the server is trying to connect to itself to display the GUI. So if it's on a LAN, you would just put in your computer's name. If you are connecting to a server on the WAN, then you need to specify your router's external IP and have the proper port forwarded. If it was working fine and stopped working without any proper reason, Probably it could be an uncontrolled X instance running in the background.
Please close that using task manager. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Ask Question.
0コメント