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

From: Sam Vilain (sam_at_vilain.net)
Date: Wed 22 Jan 2003 - 16:12:09 GMT


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.


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 Wed 22 Jan 2003 - 16:46:47 GMT by hypermail 2.1.3