[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference unxa::cde

Title:CDE on Digital UNIXonment - CDE
Notice:CDE on Digital UNIX - for CDE on VMS, please see Note 1.3
Moderator:UNXA::SYSTEM
Created:Tue Nov 23 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:660
Total number of notes:2674

606.0. "Dunix 4.0b -- "Failed to establish all listening sockets"" by ALFAXP::RETTERER () Tue Feb 18 1997 10:20

Howdy.

I have a customer who has upgraded a Alphastation 250 from Dunix 3.2g to 4.0b.
After the upgrade, the system fails to startup  the Xdisplay server.

She is using XDM instead of CDE for the moment.

In the file /usr/lib/X11/xdm/xdm-errors she gets the following error:

Fatal server error:
Failed to establish all listening sockets

Tue Feb.....
error (pid 660): Server unexpectedly died

Tue Feb....
error (pid 660): Server for display :0 can't be started


We tried to startup the Xserver by hand and get the same error.

I had her set the -core switch in the command line in the Xservers file
and we do get a core.

(dbx) where
>  0 __kill(0x3ffc0080338, 0x3ff00000008, 0x3ff80170a44, 0x3ffc0080c50,
0x3ffc0082590) [0x3ff800e7a50]
   1 (unknown)() [0x3ff8019764c]
   2 __tis_raise(0x3ff8010fb04, 0x3ffc0080c50, 0x3ff80159f44, 0x0,
0x3ff80170a6c) [0x3ff8010fb00]
   3 abort(0x300400c4c50, 0x0, 0x0, 0x0, 0xffffffff00000000) [0x3ff80170a68]
   4 (unknown)() [0x3000000fae0]
   5 FatalError(0x300400c0070, 0x14000a420, 0x2, 0x0, 0x0) [0x300000118f0]
   6 CreateWellKnownSockets(0x3ffbff17998, 0x0, 0x3ffbff00030, 0x1,
0x3ffbff17ac8) [0x3000000c080]
   7 dix_main(0x3ffbff17998, 0x140004760, 0x100000000, 0x14000e1c0, 0x100000006)
[0x3ffbff17af0]

And it appears that it is failing in the routine to create the listening socket
for the Xserver.

I verified that the file /tmp/.X11-unix/X0 does exist and is read/writable.
In fact we removed it so that It could create a new (fd) for the socket but
to no avail.  Subsequent attempts to start the Xserver creates the new file 
descriptor for the socket but it still fails to start.


I had her talk with the Dunix Network team and they emphatically state there
is not a problem with the network.

I of course, did my own checking in rc.config and /etc/hosts to make sure that 
localhost is defined etc...

I also changed the Xserver file to use the shared memory transport by specifying

  local:0 Local /usr/bin/X11/X -ac

I walked thru the Xdec sources and found the following code where a test is made
to see if the network is there enough to start:

    if ((_XSERVTransMakeAllCOTSServerListeners (port, &partial,
        &ListenTransCount, &ListenTransConns) >= 0) &&
        (ListenTransCount >= 1))
    {
        if (!PartialNetwork && partial)
        {
            FatalError ("Failed to establish all listening sockets");
        }
        else
        {
            ListenTransFds = (int *) malloc (ListenTransCount * sizeof (int));

            for (i = 0; i < ListenTransCount; i++)
            {
                int fd = _XSERVTransGetConnectionNumber (ListenTransConns[i]);
                
                ListenTransFds[i] = fd;
                WellKnownConnections |= (1L << fd);

                if (!_XSERVTransIsLocal (ListenTransConns[i]))
                {
                    DefineSelf (fd);
                }
            }
        }
    }


I know that the variable "partial" is a integer that holds the value returned
from the call to _XSERVTransMakeAllCOTSServerListeners but, I cannot find
where _XSERVTransMakeAllCOTSServerListeners is defined at.

This problem is a urgent issue for my customer and any help in resolving this
issue would be greatly appreciated. 

Thanks,

Rick Retterer
Workstation/Graphics Support
Alpharetta, GA.
[email protected]
343-0367
T.RTitleUserPersonal
Name
DateLines
606.1./Xdec -pnWRKSYS::RICHARDSONTue Feb 18 1997 12:073
    You need to start the Xserver with -pn so that this error is ignored.
    
    /Charlotte
606.2I have no hair left to pull out!ALFAXP::RETTERERTue Feb 18 1997 12:5723
According to the man pages for Xdec, isn't -pn the default value for the 
Xdec server?

# man Xdec

  -pn Permits the server to continue running if it fails to establish all of
      its well-known sockets, but establishes at least one. (Default)


As a side note, my customer was able to correct the problem by shutting 
down the system and turning off the power to it.  She had done this to 
connect a new disk drive to reinstall 4.0b on to.  By mistake, she typed
in the command to boot the old disk and it came up and the Xserver started.

Is that really weird or what?

I had her switch over to CDE and it came up ok as well and she was able to 
get logged in as if nothing ever was wrong.

I cannot tell you how much time I put into walking source code, trouble-shooting
cussing, discussing and pulling my hair out on this problem.

Rick R.