X failure on server error=111 (fine yesterday)

X failure on server error=111 (fine yesterday)

Post by Tom » Sat, 17 Jun 2000 04:00:00



I need help badly on this one.

FontTransSocketUNIXConnect: can't connect: errno=111
failed to set default path 'unix:-1'
FATAL server ERROR:
could not open default font 'fixed'

I have had this one before on Redhat workstations but never have had any
luck fixing it. I always ended up reinstalling before.

Now it has happend to a secure web server and I really do not want to
re-install.
The odd thing is I did nothing to this machine yesterday to speak of. I
came in this morning and X will not start .

Any body with experience on this one?

Thanks,
Tom
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
system specs
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
RedHat 6.2
Matrox Melleniuim card

Made no changes from yesterday so I doubt it's hardware configuration
I have had this same error on a variety of hardware before.

 
 
 

X failure on server error=111 (fine yesterday)

Post by Reid Rivenburg » Sat, 17 Jun 2000 04:00:00


Quote: Tom  writes:

 > I need help badly on this one.  FontTransSocketUNIXConnect: can't
 > connect: errno=111 failed to set default path 'unix:-1' FATAL
 > server ERROR: could not open default font 'fixed'

 > I have had this one before on Redhat workstations but never have
 > had any luck fixing it. I always ended up reinstalling before.

 > Now it has happend to a secure web server and I really do not want
 > to re-install.  The odd thing is I did nothing to this machine
 > yesterday to speak of. I came in this morning and X will not start
 > .

 > Any body with experience on this one?

Not exactly, but sometimes strange things happen when /tmp fills up.
Is that the problem?

Reid

 
 
 

X failure on server error=111 (fine yesterday)

Post by Tom » Sat, 17 Jun 2000 04:00:00


The very first message I got this morning when I tried to start X was that
the /tmp was full and X crashed. I tossed some things from the /tmp dir and
rebooted several times, nothing. Since then it's been a slow decent into
computer Hell.
xfs will not keep running
the log says xfs: Cannot extablish any listening sockets
the x output is snivelling about not being able to load the font path or
find the default font 'fixed'
If you have any ideas I am all ears (eyes)
Tom


Quote:> Tom  writes:

>  > I need help badly on this one.  FontTransSocketUNIXConnect: can't
>  > connect: errno=111 failed to set default path 'unix:-1' FATAL
>  > server ERROR: could not open default font 'fixed'

>  > I have had this one before on Redhat workstations but never have
>  > had any luck fixing it. I always ended up reinstalling before.

>  > Now it has happend to a secure web server and I really do not want
>  > to re-install.  The odd thing is I did nothing to this machine
>  > yesterday to speak of. I came in this morning and X will not start
>  > .

>  > Any body with experience on this one?

> Not exactly, but sometimes strange things happen when /tmp fills up.
> Is that the problem?

> Reid

 
 
 

X failure on server error=111 (fine yesterday)

Post by Tom » Sat, 17 Jun 2000 04:00:00


Well here is the answer

I am an IDIOT

yesterday while logged in as root I threw some stuff in the TRASH

I filled my miserable little  / partition to the point where X could not
create another thing on it.

I don't know why I did not do a df before now,...... but there you are.

Thanks for your time,

Tom


Quote:> Tom  writes:

>  > I need help badly on this one.  FontTransSocketUNIXConnect: can't
>  > connect: errno=111 failed to set default path 'unix:-1' FATAL
>  > server ERROR: could not open default font 'fixed'

>  > I have had this one before on Redhat workstations but never have
>  > had any luck fixing it. I always ended up reinstalling before.

>  > Now it has happend to a secure web server and I really do not want
>  > to re-install.  The odd thing is I did nothing to this machine
>  > yesterday to speak of. I came in this morning and X will not start
>  > .

>  > Any body with experience on this one?

> Not exactly, but sometimes strange things happen when /tmp fills up.
> Is that the problem?

> Reid

 
 
 

X failure on server error=111 (fine yesterday)

Post by v3kt0 » Sun, 18 Jun 2000 04:00:00


You have a font path problem: your server is crashing because it cannot find
the default font.  Based on the error message, you are running a font server,
right?  The problem is that X cannot find the font server.  Instead of using
the "-1" for loop-back use port 7100 if using xfs ("unix/:7100") or
7101 if using xfstt (unix/:7101).  Change this in XF86Config.

You could also get you xserver back up by simply reinstating the default font
paths in XF86Config if you are having other problems with your font server.


>I need help badly on this one.

>FontTransSocketUNIXConnect: can't connect: errno=111
>failed to set default path 'unix:-1'
>FATAL server ERROR:
>could not open default font 'fixed'

>I have had this one before on Redhat workstations but never have had any
>luck fixing it. I always ended up reinstalling before.

>Now it has happend to a secure web server and I really do not want to
>re-install.
>The odd thing is I did nothing to this machine yesterday to speak of. I
>came in this morning and X will not start .

>Any body with experience on this one?

>Thanks,
>Tom
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>system specs
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>RedHat 6.2
>Matrox Melleniuim card

>Made no changes from yesterday so I doubt it's hardware configuration
>I have had this same error on a variety of hardware before.

 
 
 

X failure on server error=111 (fine yesterday)

Post by Anthon » Mon, 19 Jun 2000 04:00:00




Quote:> I need help badly on this one.

> FontTransSocketUNIXConnect: can't connect: errno=111 failed to set
> default path 'unix:-1' FATAL server ERROR: could not open default font
> 'fixed'

The usual cause of "fixed font trouble" is xfs (X Fonts Server,
not SGI filesystem) some how stopped.

Restart the xfs server.  XFree 4.x no longer need xfs.

 
 
 

X failure on server error=111 (fine yesterday)

Post by Reid Rivenburg » Mon, 19 Jun 2000 04:00:00


Quote: Tom  writes:

 > Well here is the answer I am an IDIOT

 > yesterday while logged in as root I threw some stuff in the TRASH

 > I filled my miserable little / partition to the point where X could
 > not create another thing on it.

 > I don't know why I did not do a df before now,...... but there you
 > are.

 > Thanks for your time,

 > Tom

Well, glad to hear my shot in the dark was actually correct!  I've
heard other stories about people running out of space on /tmp or /, so
it seemed possible....

Reid

 
 
 

X failure on server error=111 (fine yesterday)

Post by <a.. » Fri, 23 Jun 2000 04:00:00



Quote:>  Tom  writes:

>  > Well here is the answer I am an IDIOT

>  > yesterday while logged in as root I threw some stuff in the TRASH

>  > I filled my miserable little / partition to the point where X could
>  > not create another thing on it.

>  > I don't know why I did not do a df before now,...... but there you
>  > are.

>  > Thanks for your time,

>  > Tom

> Well, glad to hear my shot in the dark was actually correct!  I've
> heard other stories about people running out of space on /tmp or /, so
> it seemed possible....

> Reid

ok, but what about this one?

# xinit

_X11TransSocketUNIXConnect: Can't connect: errno = 111
giving up.
xinit:  Connection refused (errno 111):  unable to connect to X
server
xinit:  No such process (errno 3):  Server error.
#

 
 
 

X failure on server error=111 (fine yesterday)

Post by Reid Rivenburg » Fri, 23 Jun 2000 04:00:00


Quote: amo  writes:

 > ok, but what about this one?

 > # xinit

 > _X11TransSocketUNIXConnect: Can't connect: errno = 111 giving up.
 > xinit: Connection refused (errno 111): unable to connect to X
 > server xinit: No such process (errno 3): Server error.
 > #

Um, you got me on that one.  That's all it prints?

Reid

 
 
 

X failure on server error=111 (fine yesterday)

Post by <a.. » Sun, 25 Jun 2000 04:00:00



Quote:>  amo  writes:

>  > ok, but what about this one?

>  > # xinit

>  > _X11TransSocketUNIXConnect: Can't connect: errno = 111 giving up.
>  > xinit: Connection refused (errno 111): unable to connect to X
>  > server xinit: No such process (errno 3): Server error.
>  > #

> Um, you got me on that one.  That's all it prints?

> Reid

Yes, sometimes it is. It depends...

fatal:~# xinit
xinit:  Server error.
fatal:~# xinit

_X11TransSocketUNIXConnect: Can't connect: errno = 111
giving up.
xinit:  Connection refused (errno 111):  unable to connect to X server
xinit:  No such process (errno 3):  Server error.
fatal:~#

 
 
 

X failure on server error=111 (fine yesterday)

Post by Hal Burgi » Sun, 25 Jun 2000 04:00:00




>Yes, sometimes it is. It depends...

>fatal:~# xinit
>xinit:  Server error.
>fatal:~# xinit

>_X11TransSocketUNIXConnect: Can't connect: errno = 111
>giving up.
>xinit:  Connection refused (errno 111):  unable to connect to X server
>xinit:  No such process (errno 3):  Server error.
>fatal:~#

Try

 xinit 2> error.txt

and see if that grabs more of it.

--
Hal B

--

 
 
 

X failure on server error=111 (fine yesterday)

Post by <a.. » Tue, 27 Jun 2000 04:00:00



> >fatal:~# xinit

> >_X11TransSocketUNIXConnect: Can't connect: errno = 111
> >giving up.
> >xinit:  Connection refused (errno 111):  unable to connect to X server
> >xinit:  No such process (errno 3):  Server error.
> >fatal:~#

> Try

>  xinit 2> error.txt

> and see if that grabs more of it.

> --

No, it doesn't.
Thanks
 
 
 

X failure on server error=111 (fine yesterday)

Post by Rick Pasot » Tue, 27 Jun 2000 04:00:00


My problem is similar but none of the suggestions I've seen have panned
out for me. I upgraded my debian system via apt-get to the potato
packages xfree86-common and xserver-svga and now I get:

'X: server socket directory has suspicious ownership, aborting.'

And then:

_X11TransSocketUNIXConnect: Can't connect: errno = 111
giving up.
xinit:  Connection refused (errno 111):  unable to connect to X server
xinit:  No such process (errno 3):  Server error.

Where is the server socket directory and what ownership should it have?

--
"Democracy is the art of running the circus from the monkey cage."
                -- H. L. Mencken

 
 
 

X failure on server error=111 (fine yesterday)

Post by Hal Burgi » Tue, 27 Jun 2000 04:00:00



>My problem is similar but none of the suggestions I've seen have panned
>out for me. I upgraded my debian system via apt-get to the potato
>packages xfree86-common and xserver-svga and now I get:

>'X: server socket directory has suspicious ownership, aborting.'

>And then:

>_X11TransSocketUNIXConnect: Can't connect: errno = 111
>giving up.
>xinit:  Connection refused (errno 111):  unable to connect to X server
>xinit:  No such process (errno 3):  Server error.

>Where is the server socket directory and what ownership should it have?

Here on RH it is in /tmp:

 /tmp/.X11-unix:
 srwxrwxrwx    1 root     root            0 May 29 12:19 X0=

and tmp itself is:

 drwxrwxrwt    6 root     root        10240 Jun 26 10:22 ./

--
Hal B

--

 
 
 

X failure on server error=111 (fine yesterday)

Post by Jerry Peter » Tue, 27 Jun 2000 04:00:00


Did you check the permissions on the directory? Mine is in
/tmp/.X11-unix/

        Jerry


> My problem is similar but none of the suggestions I've seen have panned
> out for me. I upgraded my debian system via apt-get to the potato
> packages xfree86-common and xserver-svga and now I get:
> 'X: server socket directory has suspicious ownership, aborting.'
> And then:
> _X11TransSocketUNIXConnect: Can't connect: errno = 111
> giving up.
> xinit:  Connection refused (errno 111):  unable to connect to X server
> xinit:  No such process (errno 3):  Server error.
> Where is the server socket directory and what ownership should it have?
> --
> "Democracy is the art of running the circus from the monkey cage."
>            -- H. L. Mencken


 
 
 

1. deny 192.168.0.106:137 111.111.111.111:137

my firewalls denies myriads of this requests from a single nt-client
(192.168.0.106). Anyone has an idea what this is about ?

any known virus, trojan, bot .. whatever ?
the system states itself as virusfree with the newest virusdefs.

thnx,
peter

--
peter pilsl

http://www.goldfisch.at

2. Serial access for an user

3. errno=111 / Fatal Server Error

4. AIX 1.3 support for 9515 monitor?

5. x11 server error 111 and 3

6. Accessing X-Windows

7. username@111.111.111.111, Is this working?

8. A question about a hard drive and RAM upgrade.

9. NFS client error: portmap error 111

10. execve failure and X errror 111

11. Unable to connect to X server (errno = 111)

12. use sendto() to send UDP, get error 111, connection refused, why?

13. ERROR 111