Xlib: connection to ":0.0" refused by server

Xlib: connection to ":0.0" refused by server

Post by Margaret M. Ha » Wed, 14 Oct 1998 04:00:00



Hello!

We're setting up a bunch of Ultra 30's (Solaris 2.6), and seeing
some X errors.  In particular, when we fire up FrameMaker, it
will freeze with the following error:

Xlib: connection to ":0.0" refused by server
Xlib: Maximum number of clients reached

I realize this is probably an X tunable parameter, but not
knowing too too much about Solaris - not sure which one..

Anyone have any ideas??

Thanks!
Peggy

 
 
 

Xlib: connection to ":0.0" refused by server

Post by Doug McInty » Thu, 15 Oct 1998 04:00:00



Quote:>We're setting up a bunch of Ultra 30's (Solaris 2.6), and seeing
>some X errors.  In particular, when we fire up FrameMaker, it
>will freeze with the following error:
>Xlib: connection to ":0.0" refused by server
>Xlib: Maximum number of clients reached
>I realize this is probably an X tunable parameter, but not
>knowing too too much about Solaris - not sure which one..
>Anyone have any ideas??

Its more likely to be a security violation. Ie. the user that is
logged into the workstation isn't the one that is trying to run up
Frame maker on that display. By default, in Openwindows or CDE on
Solaris 2.6, the window system will set the logged in user up
correctly with the correct DISPLAY variable, and setup the right entry
in their ~/.Xauthority. If a user telnet's in, and tries to run
Framemaker on that system, without setting their DISPLAY back to their
proper screen, it'll fail to connect to the screen.

The solution, is make sure your DISPLAY variable is setup right, and
that your ~/.Xauthority is setup correctly. If you are running a the
user that is logged in, this should be all automatic for you.

You'll run into this alot when you 'su' and forget to exit out of the
root shell (running as root) and run the program. root doesn't have
permission by default to display to your X screen.

--

  Network Engineer/Tech Support/Jack of All Trades of Vector Internet
Due to circumstances beyond your control, you are master of your fate
and captain of your soul.

 
 
 

Xlib: connection to ":0.0" refused by server

Post by Peter C. Tribb » Thu, 15 Oct 1998 04:00:00




Quote:

> We're setting up a bunch of Ultra 30's (Solaris 2.6), and seeing
> some X errors.  In particular, when we fire up FrameMaker, it
> will freeze with the following error:

> Xlib: connection to ":0.0" refused by server
> Xlib: Maximum number of clients reached

I've seen this fairly often under 2.6 as well (not with FrameMaker,
just in normal use). I don't know if the client limit got smaller, or
whether I've just got more windows open than I used to (although I'm
having to consciously open less windows than before, so I suspect the
server). There are certainly a bunch of bug reports in sunsolve about
this.

Certain applications seem to create a lot of client connections that
don't get closed. Wabi in particular - we had to stop using it
completely, as it left the X server in this state about 1 time in
3. You can look in /proc/#####/fd (where ##### is the pid of the X
server) to see how many file descriptors the X server is using, as it
can run out.

--
-Peter Tribble
HGMP Computing Services
http://www.hgmp.mrc.ac.uk/~ptribble/

 
 
 

Xlib: connection to ":0.0" refused by server

Post by George Nussba » Thu, 15 Oct 1998 04:00:00


Try typing "xhosts +" (no quotes) at the command prompt.  Worked for
me...

George





>> We're setting up a bunch of Ultra 30's (Solaris 2.6), and seeing
>> some X errors.  In particular, when we fire up FrameMaker, it
>> will freeze with the following error:

>> Xlib: connection to ":0.0" refused by server
>> Xlib: Maximum number of clients reached

>I've seen this fairly often under 2.6 as well (not with FrameMaker,
>just in normal use). I don't know if the client limit got smaller, or
>whether I've just got more windows open than I used to (although I'm
>having to consciously open less windows than before, so I suspect the
>server). There are certainly a bunch of bug reports in sunsolve about
>this.

>Certain applications seem to create a lot of client connections that
>don't get closed. Wabi in particular - we had to stop using it
>completely, as it left the X server in this state about 1 time in
>3. You can look in /proc/#####/fd (where ##### is the pid of the X
>server) to see how many file descriptors the X server is using, as it
>can run out.

>--
>-Peter Tribble
>HGMP Computing Services
>http://www.hgmp.mrc.ac.uk/~ptribble/

 
 
 

Xlib: connection to ":0.0" refused by server

Post by Alan Coopersmi » Thu, 15 Oct 1998 04:00:00



>Try typing "xhosts +" (no quotes) at the command prompt.  Worked for
>me...

And it completely destroys your security, so unless there's a firewall
filtering out all X11 traffic between your desktop and anyone you don't
trust, you really really don't want to do it.

--
________________________________________________________________________

Univ. of California at Berkeley         http://soar.Berkeley.EDU/~alanc/

 
 
 

Xlib: connection to ":0.0" refused by server

Post by Margaret M. Ha » Thu, 15 Oct 1998 04:00:00


Hey all!

Thanks for answering so far.. I have to *test out* the xhost + theory,
but that cannot be the final solution for security reasons.. Is there
a file that I can configure to up the number of descriptors allowed
for the Xserver?? =)

Thank you again!
Peggy

: Try typing "xhosts +" (no quotes) at the command prompt.  Worked for
: me...

: George




: >>
: >> We're setting up a bunch of Ultra 30's (Solaris 2.6), and seeing
: >> some X errors.  In particular, when we fire up FrameMaker, it
: >> will freeze with the following error:
: >>
: >> Xlib: connection to ":0.0" refused by server
: >> Xlib: Maximum number of clients reached
: >
: >I've seen this fairly often under 2.6 as well (not with FrameMaker,
: >just in normal use). I don't know if the client limit got smaller, or
: >whether I've just got more windows open than I used to (although I'm
: >having to consciously open less windows than before, so I suspect the
: >server). There are certainly a bunch of bug reports in sunsolve about
: >this.
: >
: >Certain applications seem to create a lot of client connections that
: >don't get closed. Wabi in particular - we had to stop using it
: >completely, as it left the X server in this state about 1 time in
: >3. You can look in /proc/#####/fd (where ##### is the pid of the X
: >server) to see how many file descriptors the X server is using, as it
: >can run out.
: >
: >--
: >-Peter Tribble
: >HGMP Computing Services
: >http://www.hgmp.mrc.ac.uk/~ptribble/

 
 
 

Xlib: connection to ":0.0" refused by server

Post by arno.. » Fri, 16 Oct 1998 04:00:00



Quote:> Xlib: connection to ":0.0" refused by server
> Xlib: Maximum number of clients reached
> I realize this is probably an X tunable parameter, but not
> knowing too too much about Solaris - not sure which one..
> Anyone have any ideas??

I had the same problem on Sparc 20s running Solaris 2.5. After
a lot of searching on the SUNsolve cds asking SUN support and
hassling our development people I found out there is a fixed
limit in the number of clients that are allowed to connect to
the Xserver. On 2.5 there is no way to increase this.

We simply had to reduce the number of clients - a huge pain in
the *- and live with it.

I must admit that we have a huge amount of clients running and
a lot of open windows. xwininfo -root -children gave an output
of 4000+ lines. If you have a different scenario there still  
may be a problem with the server.

Regards
Arnold

--
----
On my planet to rest is to rest - to cease using energy. To me it is
illogical to run up and down on green grass, using energy instead of
saving it.  Spock "Shore Leave", Stardate 3028.2

Arnold Greyling
Siemens Ltd, Private bag X71, Halfway House, 1685  South Africa        
Tel. ++27 82 557 2579 ++27 11 652 2587

X.400: C=ZA;A=TELKOM400;P=SCN;O=Siemens; OU1=JNB1;OU2=P3;S=arnoldg  

 
 
 

Xlib: connection to ":0.0" refused by server

Post by George Nussba » Fri, 16 Oct 1998 04:00:00


Which is precisely what we have  :)




>>Try typing "xhosts +" (no quotes) at the command prompt.  Worked for
>>me...

>And it completely destroys your security, so unless there's a firewall
>filtering out all X11 traffic between your desktop and anyone you don't
>trust, you really really don't want to do it.

>--
>________________________________________________________________________

>Univ. of California at Berkeley         http://soar.Berkeley.EDU/~alanc/


 
 
 

1. Xlib: connection to ":0.0" refused by server

Hi there,

please somebody help me ....

I am user zazen and root at the same time (lousy root :-))
I cannot log in the Xserver anymore as user zazen (others are fine)
and if I su to zazen and want to start a X application : the following
happens:



Xlib: connection to ":0.0" refused by server
Xlib: Invalid MIT-MAGIC-COOKIE-1 key
Error: Can't open display: :0

Please could somebody show me the direction to correct this?
TIA

Jean-Philippe

2. Adaptec MFM/RLL --> SCSI bridge board support

3. nfssys call (NIS+, keylogin, keylogout)

4. can't run anything under su (Xlib: connection to ":0.0" refused by server)

5. NEED alittle HELP

6. Xlib: connection to "0.0" refused by server

7. simple daemon source

8. Xlib: connection to ":0.0" refused by server

9. Xlib: connection to ":0.0" refused by server ERROR

10. Xlib: connection to ":0.0" refused by server

11. Xlib: connection to "0.0" refused by server