[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] x won't start on server



I don't know if this is the problem, but when I ran apt on a 3.1.1 install, it updated the bitstream fonts which then caused X to stop.  Removing the bitstream update restored X.

Dave Hopkins
> Jimmy,
> 
> SOrry, my mistake.  Port 7100 is the port you need to be looking for.
> 177 is for xdmcp (gdm-binary).
> 
> As you can see, there is something listening on 7100 like there
> should be.
> 
> Since restarting xfs, have you tried to bring up X again on the
> console ?
> 
> Jim.
> 
> 
> 
> On Mon, 1 Dec 2003, Jimmy Schwankl wrote:
> 
> > On Monday, December 1, 2003, at 12:07 PM, jam mcquil com wrote:
> > 
> > > It sounds like your XFS (X Font Server) isn't running.
> > >
> > > Try this on the server:
> > >
> > >     netstat -anp | grep ":177 "
> > >
> > > See if it shows that something is LISTENING on the port.
> > >
> > > If not, then try this:
> > >
> > >     service xfs restart
> > 
> > OK,  the first netstat command didn't show anything listening on port 
> > 177
> > 
> > issuing the service restart command gave:
> > 
> > xfs shutdown FAILED
> > xfs restart SUCCEEDED
> > 
> > still nothing from netstat on port 177, so I tried netstat -anp without 
> > narrowing the results with grep and got the following:
> > 
> > Active Internet connections (servers and established)
> > Proto Recv-Q Send-Q Local Address           Foreign Address         
> > State       PID/Program name
> > tcp        0      0 127.0.0.1:32768         0.0.0.0:*               
> > LISTEN      3613/xinetd
> > tcp        0      0 0.0.0.0:5900            0.0.0.0:*               
> > LISTEN      3613/xinetd
> > tcp        0      0 0.0.0.0:5901            0.0.0.0:*               
> > LISTEN      3613/xinetd
> > tcp        0      0 0.0.0.0:5902            0.0.0.0:*               
> > LISTEN      3613/xinetd
> > tcp        0      0 0.0.0.0:5903            0.0.0.0:*               
> > LISTEN      3613/xinetd
> > tcp        0      0 0.0.0.0:111             0.0.0.0:*               
> > LISTEN      3481/portmap
> > tcp        0      0 0.0.0.0:5904            0.0.0.0:*               
> > LISTEN      3613/xinetd
> > tcp        0      0 0.0.0.0:5905            0.0.0.0:*               
> > LISTEN      3613/xinetd
> > tcp        0      0 172.18.0.161:53         0.0.0.0:*               
> > LISTEN      3586/named
> > tcp        0      0 192.168.0.254:53        0.0.0.0:*               
> > LISTEN      3586/named
> > tcp        0      0 127.0.0.1:53            0.0.0.0:*               
> > LISTEN      3586/named
> > tcp        0      0 0.0.0.0:22              0.0.0.0:*               
> > LISTEN      3599/sshd
> > tcp        0      0 127.0.0.1:953           0.0.0.0:*               
> > LISTEN      3586/named
> > tcp        0      0 0.0.0.0:7100            0.0.0.0:*               
> > LISTEN      4036/xfs
> > tcp        0     48 172.18.0.161:22         172.18.0.212:60689      
> > ESTABLISHED 3946/sshd
> > udp        0      0 0.0.0.0:32768           0.0.0.0:*                   
> >          3586/named
> > udp        0      0 0.0.0.0:514             0.0.0.0:*                   
> >          3458/syslogd
> > udp        0      0 0.0.0.0:177             0.0.0.0:*                   
> >          3715/gdm-binary
> > udp        0      0 172.18.0.161:53         0.0.0.0:*                   
> >          3586/named
> > udp        0      0 192.168.0.254:53        0.0.0.0:*                   
> >          3586/named
> > udp        0      0 127.0.0.1:53            0.0.0.0:*                   
> >          3586/named
> > udp        0      0 0.0.0.0:67              0.0.0.0:*                   
> >          3647/dhcpd
> > udp        0      0 0.0.0.0:68              0.0.0.0:*                   
> >          3399/dhclient
> > udp        0      0 0.0.0.0:69              0.0.0.0:*                   
> >          3613/xinetd
> > udp        0      0 0.0.0.0:111             0.0.0.0:*                   
> >          3481/portmap
> > udp        0      0 172.18.0.161:123        0.0.0.0:*                   
> >          3632/ntpd
> > udp        0      0 192.168.0.254:123       0.0.0.0:*                   
> >          3632/ntpd
> > udp        0      0 127.0.0.1:123           0.0.0.0:*                   
> >          3632/ntpd
> > udp        0      0 0.0.0.0:123             0.0.0.0:*                   
> >          3632/ntpd
> > raw        0      0 0.0.0.0:1               0.0.0.0:*               7   
> >          3647/dhcpd
> > Active UNIX domain sockets (servers and established)
> > Proto RefCnt Flags       Type       State         I-Node PID/Program 
> > name    Path
> > unix  2      [ ACC ]     STREAM     LISTENING     3953   3656/gpm       
> >       /dev/gpmctl
> > unix  12     [ ]         DGRAM                    3154   3458/syslogd   
> >       /dev/log
> > unix  2      [ ACC ]     STREAM     LISTENING     4327   
> > 3715/gdm-binary     /tmp/.gdm_socket
> > unix  2      [ ACC ]     STREAM     LISTENING     45494  4036/xfs       
> >       /tmp/.font-unix/fs7100
> > unix  2      [ ]         DGRAM                    45497  4036/xfs
> > unix  2      [ ]         DGRAM                    5367   3715/gdm-binary
> > unix  2      [ ]         DGRAM                    4004   3683/verynice
> > unix  2      [ ]         DGRAM                    3968   3665/crond
> > unix  2      [ ]         DGRAM                    3889   3647/dhcpd
> > unix  2      [ ]         DGRAM                    3851   3632/ntpd
> > unix  2      [ ]         DGRAM                    3802   3613/xinetd
> > unix  2      [ ]         DGRAM                    3739   3586/named
> > unix  2      [ ]         DGRAM                    3326   3548/apmd
> > unix  2      [ ]         DGRAM                    3163   3462/klogd
> > unix  2      [ ]         STREAM     CONNECTED     3067   3399/dhclient
> > 
> > Everything with xfs in it *appears* to be listening, but none of them 
> > are associated with port 177.  That appears to be associated with gdm.
> > 
> > Let me know if I need to get on the chat and I'll see what I can 
> > arrange.
> > 
> > Thanks,
> > Jimmy
> > 
> > 
> > _______________________________________________
> > K12OSN mailing list
> > K12OSN redhat com
> > https://www.redhat.com/mailman/listinfo/k12osn
> > For more info see <http://www.k12os.org>
> > 
> 
> 
> _______________________________________________
> K12OSN mailing list
> K12OSN redhat com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]