Ah,
Error: Can't open display:
means there is not DISPLAY environment variable.
What happens when you
if [ -z ${DISPLAY+x} ]; then echo "DISPLAY is unset"; else echo "DISPLAY is set to '$DISPLAY'"; fi
Mine says:
[sas@myhost ~]$ if [ -z ${DISPLAY+x} ]; then echo "DISPLAY is unset"; else echo "DISPLAY is set to '$DISPLAY'"; fi DISPLAY is set to 'localhost:10.0'
If you see:
DISPLAY is unset
then there is no DISPLAY variable set to set it try:
export DISPLAY=localhost:0.0 echo "New Display is $DISPLAY "
Also how are you connecting to this Linux system? Putty from Windows? SSH from another Linux box?
for Putty:
in connection settings Connection > SSH > X11
Check X11 forwarding: [x] Enable X11 forwarding
Add to the "X display location" field: localhost:0.0
for command line SSH add the -X parameter to enable X11 Forwarding.
It looks like you do not have xterm installed. Just use xclock until it works then do the SAS install. I don't have xclock on my system but I do have xterm and gedit and a few others. Your machine will be different than mine.
If you are not using X11 forwarding locolhost:0.0 will not work You have to use the real IP address of the machine that will display the window like:
export DISPLAY=myhost.mycorp.com:0.0
Andy
Do not forget to restart your server after increasing user limits. Also, use xclock application to test the connection to your remote X11 server.
I tried rebooting servers, but still same error
Hello sasprofile,
Before the installation try:
id
Your userid should be 'sas'
ulimit -a
You should see the values you expected.
Next, on your Windows client install Xming or another X Windows Server
then in a command prompt type
ipconfig
Your Windows IP address will be after Ipv4 Address ......
Back on the Linux box type:
export DISPLAY=<ipv4 Address from previous step>:0
then
xterm
you should see a terminal appear on your Windows machine where you are running XMing
start the SAS Install from this terminal window.
If these steps don't all work the install will not work.
Andy
I already used export DISPLAY=localhost:0.0
As I already said, you can use xclock application to test the connection to your X11 server.
Sorry I dont know about xclock
Is it a desktop appln i need to install
It seems like you need to contact your Linux administrator and ask him/her to help you.
I don't usually set DISPLAY anymore. I use Putty with an X11 forwarding enabled. When you configure the Putty connection use;
Connection -> SSH -> X11 then check 'Enable X11 forwarding' and save the session. Then when I connect to Linux it sets DISPLAY for me.
[sas@myhost ~]$echo $DISPLAY localhost:10.0
and when I type
xterm
I see:
PuTTY X11 proxy: unable to connect to forwarded X server: Network error: Connection refused xterm: Xt error: Can't open display: localhost:10.0
Then I start Xming server on my Windows PC and type 'xterm' again I see the terminal. Once you have any X Windows client working the install should work. You can also start the install from your new xterm terminal window and it will already be an X Windows client with a working display.
If you are not using SSH + X11 forwarding you may need to give permission.
[sas@myhost ~]$ xhost +
access control disabled, clients can connect from any host
Then try again. xclock and xterm are just X11 client applications. xclock displays a clock face while xterm starts a new terminal window.
Andy
when i issue xterm it says command not found
Never mind, got it
still i have same issue....
I tried different ways but still same issue
[sas@kkg-node1 SASDepots]$ export DISPLAY=192.168.100.109:0.0
[sas@kkg-node1 SASDepots]$ xterm
-bash: xterm: command not found
[sas@kkg-node1 SASDepots]$
Usually the Linux host on which one installs SAS is headless. That means the X display is not attached to that machine. It is attached to the installer's pc. You mentioned XMing which gives away you are on a pc. This implies that the value of the DISPLAY variable must be the pc hostname or IP address, followed by the so-called seat nunmber, usually :0.0. A value of localhost:0.0 is bound to fail. Test with xclock or another X client app like xterm. As another reply indicated there is also X forwarding as part of the SSH protocol. In that case the host ís localhost but the seat usually a higher number like :10.0.
X authentication controls might be the next hurdle. For instance, if you logon with SSH and X forwarding to your normal account and than escalate to the SAS installer account you will introduce a new problem. X authentication may be obstructed. See for example http://www.snapdba.com/2013/02/ssh-x-11-forwarding-and-magic-cookies/ how this can be treated using the xauth command.
Hope this helps,
-- Jan
I tested all xclock, xterm and xforwarding..none of them helped
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.