Maximum number of clients reached

English Applications
#1

Has anyone seen this before?

Sometimes when I try to open a game, it’ll never open. This is the message I see at the end of the wine dump. I don’t think it’s wine giving this message, but the X system (I’m guessing). I saw it again when I tried to open the nvidia-settings app. Usually the solution is to close firefox; that works most of the time.

I never got this before until just recently (last few months). It happened in both 12.1 and also in 12.3 which I just installed. Any idea what this is about.

Oh, KDE 4.10.

Here’s some more info from wine.


Maximum number of clients reached err:winediag:x11drv_init_thread_data x11drv: Can't open display: :0. Please ensure that your X server is running and that $DISPLAY is set correctly.
Maximum number of clients reached err:winediag:x11drv_init_thread_data x11drv: Can't open display: :0. Please ensure that your X server is running and that $DISPLAY is set correctly.
Maximum number of clients reached err:winediag:x11drv_init_thread_data x11drv: Can't open display: :0. Please ensure that your X server is running and that $DISPLAY is set correctly.

Thanks.

#2

I found an probable reason why this is happening
source:- Xlib: Maximum number of clients reached

#3

Thanks for the link.

When I get that message again I’ll try checking to see how many sockets I have open. I did look in “/proc/823/fd” and I have a **** load of files, but I don’t know if it’s normal or not (see below). Maybe you can compare it with yours.

> sudo ls /proc/823/fd/
0    103  109  114  12   125  130  136  141  147  152  158  163  169  174  18   185  190  196  200  206  211  217  222  228  233  239  244  25  30  36  41  47  52  58  63  69  74  8   85  90  96
1    104  11   115  120  126  131  137  142  148  153  159  164  17   175  180  186  191  197  201  207  212  218  223  229  234  24   245  26  31  37  42  48  53  59  64  7   75  80  86  91  97
10   105  110  116  121  127  132  138  143  149  154  16   165  170  176  181  187  192  198  202  208  213  219  224  23   235  240  246  27  32  38  43  49  54  6   65  70  76  81  87  92  98
100  106  111  117  122  128  133  139  144  15   155  160  166  171  177  182  188  193  199  203  209  214  22   225  230  236  241  247  28  33  39  44  5   55  60  66  71  77  82  88  93  99
101  107  112  118  123  129  134  14   145  150  156  161  167  172  178  183  189  194  2    204  21   215  220  226  231  237  242  248  29  34  4   45  50  56  61  67  72  78  83  89  94
102  108  113  119  124  13   135  140  146  151  157  162  168  173  179  184  19   195  20   205  210  216  221  227  232  238  243  249  3   35  40  46  51  57  62  68  73  79  84  9   95

In any case, no solution was given.

#4

No some program is probably not written well. it is normal that /proc has those many files :-).
/proc

I don’t think it’s wine giving this message

Guess again. Whenever i search the web for this error wine related issues invariably show up. I guess this is some kind of resource issue where the virtual machines are requesting more resources than that are available on the system. Then again i might be wrong :frowning:

#5

Ah, think I might have found the culprit. Looks like it could be akonadi (see here).

Now after “killall /usr/bin/akonadi_agent_launcher”, I see this with same command:

> sudo ls /proc/823/fd
0  10  12  14  16  176  19  20  22  232  234  236  238  24   241  243  245  247  249  250  252  27  29  30  32  34  36  38  4   41  44  46  48  5   6  8
1  11  13  15  17  18   2   21  23  233  235  237  239  240  242  244  246  248  25   251  26   28  3   31  33  35  37  39  40  43  45  47  49  50  7  9

Much smaller…

I hope I don’t need this program… I want to remove it.

#6

You may need to search through these forums to determine whether akonadi is useful or not or how we can reduce it’s presumed ill effects.
Go to advanced search https://forums.opensuse.org/search.php
Keyword(s): akonadi
Sort Results by Date,Descending.

#7

Finally, I think I discovered the problem. It wasn’t Akonadi per-say. Akonadi has what it calls agents. For example, “mail filter agent”, “local folders”, etc. When I ran “akonadiconsole” I noticed I had hundreds of an agent called “personal contacts”, and I guess each one of these instances opened a socket to X. I don’t know why or how they got there, but I removed all of them and everything is ok now. Akonadi appears to be behaving itself.

#8

So wine/ game runs fine now ?

#9

Yep. I’m not having that issue anymore. I’m so happy I found the problem. Thanks for your help.

#10

I learnt few things too. thank you