[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
startx problem...
- From: mjn <mjn tc umn edu>
- To: redhat-install-list redhat com
- Subject: startx problem...
- Date: Mon, 22 May 2000 12:33:31 -0500 (CDT)
I am resubmitting this because my original post of this was during the
little burp the list had last week and I think it may have been over
looked...
Thanks...
________
The system is RH 6.1 w/XFCom_Rage128 1.3 and an Xpert99 video card
128MB
PIII 500
Up until this morning, my system was working fine. I'd login and do
startx from the line and E would come up just hunky dorey.
This morning I got into work and logged in, I issued startx and I got this
error message:
_XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListener: server already running
Fatal server error:
Cannot establish any listening sockets - Make sure an X server isn't
already running
...
Since I got this I have rebooted and still have the same problem. I have
check ps and found no X procs. I checked netstat and tcp port 6000 is
listening and nmap shows an open port on tcp 6000 X11.
I have tried disabling my firewall and starting x; no luck. I have turned
off portsentry and tried starting x; no luck. Neither of the port
configurations for this utils have changed in the last month. I guessed
that neither of these things would solve the problem as X had been working
fine since install.
I do not have a lock file in /tmp or in /var/lock or in /var/run. I am
stumped. XFS starts and stop without issue as well.
Let me deny(hopefully ;)) any fault of my own by relating this: The last
time I used E successfully was two days ago. At which time i was
modifying my portsentry, netsaint, and firewall init scripts(they come up
at start time without issue). When doing this I restarted multiple times
to ensure that the system would come up without a problem. And each of
those times i was able to startx successfully. Then the system was
shutdown while we had a power outage in our room; it was restarted
an hour or two later. Two days later, when i tried to login again for the
first time, i got these errors.
Anyone ever seen anything like this before? One question that i have is
whether or not there is a log for X. I had an incident last week where
all of my logs were deleted and I have been suffering through getting them
all reporting properly again. I would hope that, if it were the abcense of
a log file, the errors would reflect that. But I cannot make heads or
tails of this; nor can anyone else I have asked.
____________________________
Mike Neuharth
ADCS Technology Specialist
http://www.umn.edu/adcs
E-Mail : mjn tc umn edu
Page Mail : 6123065932 messaging sprintpcs com
http://nifty.dsl.visi.com/
____________________________
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]