Hi, we have a linux cluster (dual opteron) running sles9 AMD64 SP3. I can not use xterm. There is no error messages. Nothing happens. xlogo or other stuff is working. Any idea ? -- Bye, Peer _________________________________________________________ Max-Planck-Institut fuer Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705
Dear Peer, I am not sure about SLES9 but in recent SuSE Linux versions the xterm application is not part of the Xorg distribution but is provided in a separate package (e.g., xterm-208-14 in OpenSuSE 10.1). Could you please verify if the file /usr/X11R6/bin/xterm exists and/or if the xterm-* package is installed (rpm -qa | grep xterm)?. If it is installed and still you don't get a window, please look for execution errors in the following files: ~/.xsession-errors ~/.X.err /var/log/Xorg.*.log - José Luis On Fri, 28 Jul 2006 11:32:47 +0200, Dr.Peer-Joachim Koch <pkoch@bgc-jena.mpg.de> wrote:
Hi,
we have a linux cluster (dual opteron) running sles9 AMD64 SP3.
I can not use xterm. There is no error messages. Nothing happens. xlogo or other stuff is working.
Any idea ?
-- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
José Luis Ricardo Chávez schrieb:
Dear Peer,
I am not sure about SLES9 but in recent SuSE Linux versions the xterm application is not part of the Xorg distribution but is provided in a separate package (e.g., xterm-208-14 in OpenSuSE 10.1). Could you please verify if the file /usr/X11R6/bin/xterm > exists and/or if the xterm-* package is installed (rpm -qa | grep xterm)?. If it is installed and still you don't get a window, please look for execution errors in the following files:
ll /usr/X11R6/bin/xterm -rwxr-xr-x 1 root root 369112 Dec 2 2005 /usr/X11R6/bin/xterm rpm -qf /usr/X11R6/bin/xterm XFree86-4.3.99.902-43.71 nothing in the log's There is no /var/log/Xorg* But the xterm seem's to do something (error messages, but where) pkoch 17853 99.9 2.2 117800 90980 ? Rs 11:47 22:21 xterm Load is 1 - nothing running. Only the xterm ... Bye, Peer _________________________________________________________ Max-Planck-Institut fuer Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705
This is weird, if the DISPLAY variable is correctly set and the network services are up I would look for missing link libraries. What does 'ldd /usr/X11R6/bin/xterm' shows? - José Luis On Fri, 28 Jul 2006 12:11:48 +0200, Dr.Peer-Joachim Koch <pkoch@bgc-jena.mpg.de> wrote:
José Luis Ricardo Chávez schrieb:
Dear Peer,
I am not sure about SLES9 but in recent SuSE Linux versions the xterm application is not part of the Xorg distribution but is provided in a separate package (e.g., xterm-208-14 in OpenSuSE 10.1). Could you please verify if the file /usr/X11R6/bin/xterm > exists and/or if the xterm-* package is installed (rpm -qa | grep xterm)?. If it is installed and still you don't get a window, please look for execution errors in the following files:
ll /usr/X11R6/bin/xterm -rwxr-xr-x 1 root root 369112 Dec 2 2005 /usr/X11R6/bin/xterm
rpm -qf /usr/X11R6/bin/xterm XFree86-4.3.99.902-43.71
nothing in the log's
There is no /var/log/Xorg*
But the xterm seem's to do something (error messages, but where)
pkoch 17853 99.9 2.2 117800 90980 ? Rs 11:47 22:21 xterm Load is 1 - nothing running. Only the xterm ...
Bye, Peer
_________________________________________________________ Max-Planck-Institut fuer Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705
-- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Well, the behavior seem's to be related to (my ?) network wide settings. Using local account on my machine with ssh -X to_the_host -l username everything IS working. So it's not (only?) a problem of the xterm, but might be related to personal settings. However, the home is located on a NFS share. Can this be the reason ? (locking the same file ?) José Luis Ricardo Chávez schrieb:
This is weird, if the DISPLAY variable is correctly set and the network services are up I would look for missing link libraries. What does 'ldd /usr/X11R6/bin/xterm' shows?
- José Luis
-- Bye, Peer _________________________________________________________ Max-Planck-Institut fuer Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705
I rather think the problem is related to the way X Windows manages security. In principle, xauth stores a key in ~/.Xauthority whenever the user grants permission to a host (display) to connect to the X server but sometimes the user's key changes and the connection could not be stablished unless the .Xauthority file is deleted or recreated. I had forgotten that some time ago I had a similar problem while trying to set up my network (nfs) account after installing a new SuSE version. Cheers. - José Luis On Fri, 28 Jul 2006 13:41:07 +0200, Dr.Peer-Joachim Koch <pkoch@bgc-jena.mpg.de> wrote:
Well,
the behavior seem's to be related to (my ?) network wide settings.
Using local account on my machine with ssh -X to_the_host -l username everything IS working.
So it's not (only?) a problem of the xterm, but might be related to personal settings. However, the home is located on a NFS share.
Can this be the reason ? (locking the same file ?)
José Luis Ricardo Chávez schrieb:
This is weird, if the DISPLAY variable is correctly set and the network services are up I would look for missing link libraries. What does 'ldd /usr/X11R6/bin/xterm' shows?
- José Luis
-- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
What is the client that you are trying to open a window on ? Starting with about Suse 9.3, the X server by default starts with the option "-nolisten tcp", which means that the X server will not even listen for connections over TCP. So, if you did a default install of Suse 9.3-Suse 10.1 on a workstation, the default behavior of that workstation is to not listen for incoming X connections. Loggin in to a remote machine, setting the DISPLAY, and launching an application will result in "nothing" happening. Check your local X server by "ps -ef | grep X" - if you see something like this, you X server will not allow incoming connections. /usr/X11R6/bin/X -br -nolisten tcp :0 vt7 ssh will work, but the X you grew up with (at least us older guys :) will not... If you want to turn off this security feature, you will have to modify /usr/X11R6/lib/X11/xdm/Xservers # use such a line to enable the console login option in the kdm menu #:0 local@tty1 /usr/X11R6/bin/X vt7 # "reserve" means that the X server gets only started on request (only kdm) :0 local /usr/X11R6/bin/X -nolisten tcp -br vt7 Remove the "-nolisten tcp" option, and reboot... Kevin Kevin Gassiot Advanced Systems Group Visualization Systems Support Veritas DGC 10300 Town Park Dr. Houston, Texas 77072 832-351-8978 kevin_gassiot@veritasdgc.com José Luis Ricardo Chávez <ricardo@irsamc.ups-tlse.fr> 07/28/2006 07:31 AM To suse-amd64@suse.com cc Subject Re: [suse-amd64] xterm will not open a windows I rather think the problem is related to the way X Windows manages security. In principle, xauth stores a key in ~/.Xauthority whenever the user grants permission to a host (display) to connect to the X server but sometimes the user's key changes and the connection could not be stablished unless the .Xauthority file is deleted or recreated. I had forgotten that some time ago I had a similar problem while trying to set up my network (nfs) account after installing a new SuSE version. Cheers. - José Luis On Fri, 28 Jul 2006 13:41:07 +0200, Dr.Peer-Joachim Koch <pkoch@bgc-jena.mpg.de> wrote:
Well,
the behavior seem's to be related to (my ?) network wide settings.
Using local account on my machine with ssh -X to_the_host -l username everything IS working.
So it's not (only?) a problem of the xterm, but might be related to personal settings. However, the home is located on a NFS share.
Can this be the reason ? (locking the same file ?)
José Luis Ricardo Chávez schrieb:
This is weird, if the DISPLAY variable is correctly set and the network services are up I would look for missing link libraries. What does 'ldd /usr/X11R6/bin/xterm' shows?
- José Luis
-- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com
Hi, I tried both - nothing worked ! The X-Server was running with -nolisten tcp, BUT when I use a local account on my machine it's working ??!! I'll try on on monday .... Thanks and bye, Peer Kevin_Gassiot@veritasdgc.com schrieb:
What is the client that you are trying to open a window on ? Starting with about Suse 9.3, the X server by default starts with the option "-nolisten tcp", which means that the X server will not even listen for connections over TCP. So, if you did a default install of Suse 9.3-Suse 10.1 on a workstation, the default behavior of that workstation is to not listen for incoming X connections. Loggin in to a remote machine, setting the DISPLAY, and launching an application will result in "nothing" happening.
Check your local X server by "ps -ef | grep X" - if you see something like this, you X server will not allow incoming connections.
/usr/X11R6/bin/X -br -nolisten tcp :0 vt7
ssh will work, but the X you grew up with (at least us older guys :) will not...
If you want to turn off this security feature, you will have to modify /usr/X11R6/lib/X11/xdm/Xservers
# use such a line to enable the console login option in the kdm menu #:0 local@tty1 /usr/X11R6/bin/X vt7 # "reserve" means that the X server gets only started on request (only kdm)
:0 local /usr/X11R6/bin/X -nolisten tcp -br vt7
Remove the "-nolisten tcp" option, and reboot...
Kevin
Kevin Gassiot Advanced Systems Group Visualization Systems Support
Veritas DGC 10300 Town Park Dr. Houston, Texas 77072 832-351-8978 kevin_gassiot@veritasdgc.com
José Luis Ricardo Chávez <ricardo@irsamc.ups-tlse.fr> 07/28/2006 07:31 AM
To suse-amd64@suse.com cc
Subject Re: [suse-amd64] xterm will not open a windows
I rather think the problem is related to the way X Windows manages security. In principle, xauth stores a key in ~/.Xauthority whenever the user grants permission to a host (display) to connect to the X server but sometimes the user's key changes and the connection could not be stablished unless the .Xauthority file is deleted or recreated. I had forgotten that some time ago I had a similar problem while trying to set up my network (nfs) account after installing a new SuSE version.
Cheers.
- José Luis
On Fri, 28 Jul 2006 13:41:07 +0200, Dr.Peer-Joachim Koch <pkoch@bgc-jena.mpg.de> wrote:
Well,
the behavior seem's to be related to (my ?) network wide settings.
Using local account on my machine with ssh -X to_the_host -l username everything IS working.
So it's not (only?) a problem of the xterm, but might be related to personal settings. However, the home is located on a NFS share.
Can this be the reason ? (locking the same file ?)
José Luis Ricardo Chávez schrieb:
This is weird, if the DISPLAY variable is correctly set and the network services are up I would look for missing link libraries. What does 'ldd /usr/X11R6/bin/xterm' shows?
- José Luis
-- Mit freundlichem Gruss Peer-Joachim Koch _________________________________________________________ Max-Planck-Institut fuer Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705
Hi, currently I haven't found any solution. When I use a local account on my machine and make a ssh -X connection to the linux cluster everything is fine and working (even with -nolisten). But when I use my global (normal) account (home on nfs) xterm is not working. xclock will always work, so the connection to the X-Server seem's to work. Maybe I've to check the whole env. and look at all .* files. Bye, Peer Even when the Kevin_Gassiot@veritasdgc.com schrieb:
What is the client that you are trying to open a window on ? Starting with about Suse 9.3, the X server by default starts with the option "-nolisten tcp", which means that the X server will not even listen for connections over TCP. So, if you did a default install of Suse 9.3-Suse 10.1 on a workstation, the default behavior of that workstation is to not listen for incoming X connections. Loggin in to a remote machine, setting the DISPLAY, and launching an application will result in "nothing" happening.
Check your local X server by "ps -ef | grep X" - if you see something like this, you X server will not allow incoming connections.
/usr/X11R6/bin/X -br -nolisten tcp :0 vt7
ssh will work, but the X you grew up with (at least us older guys :) will not...
If you want to turn off this security feature, you will have to modify /usr/X11R6/lib/X11/xdm/Xservers
# use such a line to enable the console login option in the kdm menu #:0 local@tty1 /usr/X11R6/bin/X vt7 # "reserve" means that the X server gets only started on request (only kdm)
:0 local /usr/X11R6/bin/X -nolisten tcp -br vt7
Remove the "-nolisten tcp" option, and reboot...
Kevin
Kevin Gassiot Advanced Systems Group Visualization Systems Support
Veritas DGC 10300 Town Park Dr. Houston, Texas 77072 832-351-8978 kevin_gassiot@veritasdgc.com
José Luis Ricardo Chávez <ricardo@irsamc.ups-tlse.fr> 07/28/2006 07:31 AM
To suse-amd64@suse.com cc
Subject Re: [suse-amd64] xterm will not open a windows
I rather think the problem is related to the way X Windows manages security. In principle, xauth stores a key in ~/.Xauthority whenever the user grants permission to a host (display) to connect to the X server but sometimes the user's key changes and the connection could not be stablished unless the .Xauthority file is deleted or recreated. I had forgotten that some time ago I had a similar problem while trying to set up my network (nfs) account after installing a new SuSE version.
Cheers.
- José Luis
On Fri, 28 Jul 2006 13:41:07 +0200, Dr.Peer-Joachim Koch <pkoch@bgc-jena.mpg.de> wrote:
Well,
the behavior seem's to be related to (my ?) network wide settings.
Using local account on my machine with ssh -X to_the_host -l username everything IS working.
So it's not (only?) a problem of the xterm, but might be related to personal settings. However, the home is located on a NFS share.
Can this be the reason ? (locking the same file ?)
José Luis Ricardo Chávez schrieb:
This is weird, if the DISPLAY variable is correctly set and the network services are up I would look for missing link libraries. What does 'ldd /usr/X11R6/bin/xterm' shows?
- José Luis
-- Mit freundlichem Gruss Peer-Joachim Koch _________________________________________________________ Max-Planck-Institut fuer Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705
trying to install OpenSuse 10.1 x86_64 I am having problems doing a FTP install. Using 216.165.129.140 for address and /pub/opensuse/distribution/SL-10.1-OSS/inst-source but continually get red box with "file not found" is there another source that works? TIA
SUSE Linux ftp.suse.com: International Mirrors USA mirrors.kernel.org/suse/ (California, San Francisco) complete http://mirrors.kernel.org/suse/ (California, San Francisco) complete ftp://mirror.colorado.edu/pub/suse (Colorado, Boulder) i386, ia64, x86_64 mirror.storagetek.com/pub/systems/suse/ (Colorado, Louisville) complete ftp-linux.cc.gatech.edu/pub/suse/suse/ (Georgia, Atlanta) complete ftp.ale.org/pub/suse (Georgia, Atlanta) almost complete http://ftp.ale.org/pub/suse/ (Georgia, Atlanta) almost complete mirror.mcs.anl.gov/pub/suse/ (Illinois, Chicago) complete chuck.ucs.indiana.edu/linux/suse/suse/ (Indiana, Bloomington) i386, ppc, ppc64 trane.caset.buffalo.edu/pub/suse/ (New York, Buffalo) i386, x86_64 distro.ibiblio.org/pub/linux/distributions/suse/suse/ (North Carolina, Chapel Hill) axp, i386, ia64 linux.nssl.noaa.gov/suse/ (Oklahoma, Norman) almost complete http://linux.nssl.noaa.gov/suse/ (Oklahoma, Norman) almost complete ftp.oregonstate.edu/pub/suse/ (Oregon, Corvallis) complete http://suse.oregonstate.edu/ (Oregon, Corvallis) complete suse.mirror.upr.edu (Puerto Rico) almost complete http://suse.mirror.upr.edu (Puerto Rico) almost complete http://sunsite.utk.edu/ftp/pub/linux/suse/ (Tennessee, Knoxville) complete http://mirror.tamu.edu/suse/ (Texas, College Station) complete ftp.empiricalnetworks.com/pub/suse/i386/ (Texas, Grapevine) i386 http://mirror.usu.edu/mirrors/opensuse (Utah, Logan) i386, ppc, sparc suse.cs.utah.edu/pub/ (Utah, Salt Lake City) complete http://suse.cs.utah.edu/ (Utah, Salt Lake City) complete ftp://suse.mirrors.tds.net/pub/suse (Wisconsin, Madison) complete http://suse.mirrors.tds.net/pub/suse (Wisconsin, Madison) complete On Fri, 28 Jul 2006 16:22:48 +0200, Gilligan <dsnell@nycap.rr.com> wrote:
trying to install OpenSuse 10.1 x86_64
I am having problems doing a FTP install. Using 216.165.129.140 for address and /pub/opensuse/distribution/SL-10.1-OSS/inst-source but continually get red box with "file not found" is there another source that works?
TIA
-- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
Gilligan <dsnell@nycap.rr.com> writes:
trying to install OpenSuse 10.1 x86_64
I am having problems doing a FTP install. Using 216.165.129.140 for address and /pub/opensuse/distribution/SL-10.1-OSS/inst-source
the path looks wrong, remove the "-OSS"
but continually get red box with "file not found" is there another source that works?
Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (5)
-
Andreas Jaeger -
Dr.Peer-Joachim Koch -
Gilligan -
José Luis Ricardo Ch ávez -
Kevin_Gassiot＠veritasdgc.com