About this list Date view Thread view Subject view Author view Attachment view

From: b.mampaey_at_crelan.be
Date: Thu 23 Jan 2003 - 14:02:02 GMT


Hi again.

I have done some more testing, and here are the results :

10.1.5.54 is the ip of the computer from which I run exceed (the broadcast
chooser)
10.1.6.67 (hn139) is the ip of the main server
10.1.6.76 (hn151) is the ip of the vserver

1) When launching xdm normally (whithout chbind) on the main server,

      I get this whith netstat :
      tcp 0 0 *:32961 *:*
LISTEN
      tcp 0 0 hn139.crelan.:linuxconf *:*
LISTEN
      tcp 0 0 *:5801 *:*
LISTEN
      tcp 0 0 *:5901 *:*
LISTEN
      tcp 0 0 *:sunrpc *:*
LISTEN
      tcp 0 0 *:x11 *:*
LISTEN
      tcp 0 0 hn139.crelan.be:ftp *:*
LISTEN
      tcp 0 0 hn139.crelan.be:telnet *:*
LISTEN
      tcp 0 0 localhost:smtp *:*
LISTEN
      tcp 0 2 hn139.crelan.be:telnet 10.1.5.54:murray
ESTABLISHED
      tcp 0 0 hn139.crelan.be:5901 10.1.5.54:vfo
ESTABLISHED
      tcp 0 0 *:ssh *:*
LISTEN
      udp 0 0 *:xdmcp *:*
      udp 0 0 *:sunrpc *:*

and whith tcpdump -n -v -i eth0 port 177 :

15:34:12.464014 10.1.5.54.1118 > 255.255.255.255.177: [udp sum ok] udp 7
(ttl 128, id 45449, len 35)
15:34:12.506503 10.1.6.67.177 > 10.1.5.54.1118: [udp sum ok] udp 48 (DF)
(ttl 64, id 0, len 76)
15:34:14.476935 10.1.5.54.1118 > 255.255.255.255.177: [udp sum ok] udp 7
(ttl 128, id 45456, len 35)
15:34:14.518615 10.1.6.67.177 > 10.1.5.54.1118: [udp sum ok] udp 48 (DF)
(ttl 64, id 0, len 76)

so you see that the main server respond.

2) Now when launching xdm on the main server and the v server, but binded
to the ip (si ipv4root is different of 0) whith the command chbind --ip
eth0 rcxdm start

I get this on the main server netstat :

udp 0 0 hn139.crelan.be:xdmcp *:*

and this on the vserver

tcp 0 0 10.1.6.76:linuxconf *:* LISTEN
tcp 0 0 *:32965 *:* LISTEN
tcp 0 0 10.1.6.76:ftp *:* LISTEN
tcp 0 0 10.1.6.76:telnet *:* LISTEN
tcp 0 138 10.1.6.76:telnet 10.1.5.54:1124
ESTABLISHED
udp 0 0 10.1.6.76:echo *:*
udp 0 0 10.1.6.76:daytime *:*
udp 0 0 10.1.6.76:chargen *:*
udp 0 0 10.1.6.76:time *:*
udp 0 0 10.1.6.76:xdmcp *:*

and whith tcpdump i get :

15:40:53.087590 10.1.5.54.1127 > 255.255.255.255.177: [udp sum ok] udp 7
(ttl 128, id 46478, len 35)
15:40:53.346360 10.1.5.54.1128 > 255.255.255.255.177: [udp sum ok] udp 7
(ttl 128, id 46480, len 35)
15:40:55.346747 10.1.5.54.1128 > 255.255.255.255.177: [udp sum ok] udp 7
(ttl 128, id 46487, len 35)
15:40:59.352538 10.1.5.54.1128 > 255.255.255.255.177: [udp sum ok] udp 7
(ttl 128, id 46497, len 35)
15:41:07.374413 10.1.5.54.1128 > 255.255.255.255.177: [udp sum ok] udp 7
(ttl 128, id 46516, len 35)

So obviously there is no response from the servers...

3) When putting in the vserver Xservers file just the following line :

10.1.9.54:0 foreign

I do get the login prompt of xdm appearing in exceed when doing an init 5.
But still i can not pick it up from the broadcast chooser.

4) Has anyone succeeded in launching a xserver locally for a vserver?

So we could have the xserver of the main server on tty 7 (like it is
usually), and the xserver of the vserver on the tty 8. Allowing to change
from one to the other just by pressing ALT-F7 ALT-F8.

Thanks,

Benjamin

                                                                                                                                       
                      Sam Vilain
                      <sam_at_vilain.net> To: b.mampaey_at_crelan.be
                      Sent by: Sam cc: vserver_at_solucorp.qc.ca
                      Vilain Subject: Re: [vserver] xdmcp
                      <sv_at_vilain.net>
                                                                                                                                       
                                                                                                                                       
                      22/01/2003 17:12
                                                                                                                                       
                                                                                                                                       

On Thu, 23 Jan 2003 02:11, b.mampaey_at_crelan.be wrote:
> 1. is xdm visible in `ps'? (sorry, have to ask :-)) Any error
> messages in /var/log/* ?
> Yes, xdm is running.
> As for the /var/log/xdm.errors here is what it says
> xdm error (pid 17473): error 98 binding socket address 177

Ah, yes, error 98. ``Address already in use'' (include/asm-i386/errno.h
in kernel source). Something is already bound to that socket. Perhaps it
is a stale network socket in TIME_WAIT status; otherwise, it could be xdm
in the main server binding to 0.0.0.0; effectively locking it for all the
interfaces on the machine.

I never really kept up with the solution for the SAMBA udp problem; Perhaps

someone else on this list [anyone? :-)] can suggest whether you are
seeing a manifestation of the same thing.

> xdm error (pid 17473): Cannot open randomFile "/dev/mem", errno = 2

>From xdm(1x):

       DisplayManager.randomFile
              A file to checksum to generate the seed of autho­
              rization keys. This should be a file that changes
              frequently. The default is /dev/mem.

/dev/mem is a bad choice for this under a vserver. Perhaps /dev/urandom
would be better, if it works. Otherwise just any file subject to change -
/var/log/wtmp or even /var/log/xdm.log :-).

> xdm error (pid 17475): server reserve cannot be executed
> xdm error (pid 17481): server reserve cannot be executed
> xdm error (pid 17508): server reserve cannot be executed
> xdm error (pid 17639): server reserve cannot be executed
> xdm error (pid 17647): server reserve cannot be executed
> xdm error (pid 17473): Server for display :1 terminated unexpectedly: 1
> xdm error (pid 17659): server reserve cannot be executed
> xdm error (pid 17473): Server for display :1 terminated unexpectedly: 1
> xdm error (pid 17668): server reserve cannot be executed
> xdm error (pid 17473): Server for display :1 terminated unexpectedly: 1
> xdm error (pid 17681): server reserve cannot be executed
> xdm error (pid 17473): Server for display :1 terminated unexpectedly: 1
> xdm error (pid 17473): Display :1 is being disabled
> xdm error (pid 17480): server open failed for :5, giving up
> xdm error (pid 17473): Display :5 cannot be opened
> xdm error (pid 17507): server open failed for :4, giving up
> xdm error (pid 17473): Display :4 cannot be opened
> xdm error (pid 17638): server open failed for :3, giving up
> xdm error (pid 17473): Display :3 cannot be opened
> xdm error (pid 17646): server open failed for :2, giving up
> xdm error (pid 17473): Display :2 cannot be opened

I think these are from syntax errors in the Xservers file. You'll have to
search for some working examples; it seems to be trying to run a program
called `reserve'. Try omitting the `reserve' word from the lines.

> 2. can you see the network socket xdm is listening on with `netstat
> -a'?
>
> No it is not listening. Maybe because of the first line of the
> xdm.errors log.

try `netstat -an | grep 177' after fixing above problems

> 3. does your Xservers file (/etc/X11/xdm/Xservers or
> /usr/X11R6/lib/X11/xdm/Xservers) specify no-listen tcp?
>
> I'm not sure what you mean by that. Here is my /etc/X11/xdm/Xservers file

:
> :0 local /usr/X11R6/bin/X :0 vt7
> :1 local reserve /usr/X11R6/bin/X :1 vt8
> :2 local reserve /usr/X11R6/bin/X :2 vt9
> :3 local reserve /usr/X11R6/bin/X :3 vt10
> :4 local reserve /usr/X11R6/bin/X :4 vt11
> :5 local reserve /usr/X11R6/bin/X :5 vt12

It seems the answer is no. The default version with Debian is:

:0 local /usr/X11R6/bin/X vt7 -dpi 100 -nolisten tcp

which disables network connections.

Check your syntax in the Xserver(1) man page, if present on your system.

> > Are you trying to see it via xdmcp broadcast, or via an XDM
> > client/chooser or X-Terminal that allows you to specify a hostname?
> Via xdmcp broadcast (I am using Exceed).
> PS : I'am using SuSE SLES 8 based on United Linux.

OK. So, from your master server on the

Other useful commands are ``fuser 177/tcp'' or ``fuser 177/udp'', to see
which process has a port open. Also ``tcpdump -n port 177'' will show you
XDMCP network traffic.

Good luck,

--
Sam Vilain, sam_at_vilain.net

Ambition is the curse of the political class. - anon.

This email and any attached files are confidential and may be legally privileged.If you are not the intended recipient, any disclosure, reproduction, copying, distribution, or other dissemination or use of this communication is strictly prohibited. If you have received this transmission in error please notify the sender immediately and then delete this email.Email transmission cannot be guaranteed to be secure or error free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore is in no way liable for any errors or omissions in the content of this message, which may arise as a result of email transmission. If verification is required, please request a hard copy.


About this list Date view Thread view Subject view Author view Attachment view
[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Thu 23 Jan 2003 - 14:33:39 GMT by hypermail 2.1.3