Re: How to Fix D-Bus Service Failures
Abdullah Yıldız <[email protected]> Sat, 8 Mar 2025 13:26:06 +0300
| Newsgroups | gmane.comp.freedesktop.dbus |
|---|---|
| Message-ID | <CABvne69daf602TVA-rdmRY2nYmtz9ZpBavaLsdKdYBY7qwa8WQ@mail.gmail.com> |
--000000000000de18f4062fd22cc9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Simon, Thank you for your detailed response and support. I shared my answers inline below. On Fri, Mar 7, 2025 at 6:00=E2=80=AFPM Simon McVittie <smcv-ZGY8ohtN/[email protected]> = wrote: > > On Fri, 07 Mar 2025 at 17:29:10 +0300, Abdullah Y=C4=B1ld=C4=B1z wrote: > > Mar 05 07:46:08 compute-server xdg-desktop-por[35472]: error: > > GDBus.Error:org.freedesktop.DBus.Error.LimitsExceeded: The maximum > > number of active connections has been reached > > Mar 05 07:46:18 compute-server dbus[1350]: [system] Failed to activate > > service 'org.freedesktop.hostname1': timed out > > Mar 05 07:46:24 compute-server dbus[1350]: [system] Connection has not > > authenticated soon enough, closing it (auth_timeout=3D30000ms, elapsed: > > 30006ms) > > This is your system bus. There is normally one per bootable system: > at least one per kernel, but whole-system containers that behave like > a full system from init upwards, like lxc, Incus or systemd-nspawn, > sometimes have their own. It is intended to be for users to talk to > system services, and for system services to talk to each other. > > > This is what I observe when I check /usr/share/dbus-1/session.conf > > This is configuration for your session bus (not the same thing), sometime= s > referred to as the user bus. There is normally one per (system,uid) > pair. It is intended to be for unprivileged programs running as the user > to talk to each other. > > Configuration files/directories with "system" in the name are for the > system bus, configuration files/directories with "session" in the name > are for the session bus (user bus), and neither affects the other bus. > > > I want to understand that overriding some of the D-Bus specific values > > (as shown below) would help to fix the issue: > > > > <busconfig> > > <!-- default for this is 900 --> > > <limit name=3D"max_completed_connections">32768</limit> > > <!-- default for this is 92 --> > > <limit name=3D"max_incomplete_connections">1000</limit> > > <!-- default for this is 100000 --> > > <limit name=3D"max_connections_per_user">150000</limit> > > </busconfig> > > It probably would, but only if you override them in the right place. > > The system bus limits can be overridden by writing a file into > /etc/dbus-1/system.d/*.conf (local configuration by the sysadmin) > or /usr/share/dbus-1/system.d/*.conf (configuration by OS vendor or > packages, e.g. from RPM or dpkg). Their defaults are hard-coded into > the dbus-daemon, but for convenient reference there is a commented-out > list of default values in /usr/share/dbus-1/system.conf (although I now > notice that some of them are out of date). > In /usr/share/dbus-1/, there are no commented-out default values available except session.conf: $ grep -r "limit" /usr/share/dbus-1/ /usr/share/dbus-1/interfaces/org.freedesktop.PackageKit.Transaction.xml: whilst it is running. There is no limit to the number of times thi= s /usr/share/dbus-1/interfaces/org.freedesktop.PackageKit.Transaction.xml: This option is only really interesting on embedded devices with a limited amount of /usr/share/dbus-1/interfaces/org.freedesktop.PackageKit.Transaction.xml: The tree does not have any depth or bredth limits, although it should be kept /usr/share/dbus-1/interfaces/org.freedesktop.PackageKit.xml: The maximum number of past transactions to return, or 0 for no limit. /usr/share/dbus-1/interfaces/org.freedesktop.portal.NetworkMonitor.xml: the default connection that is subject ot limitations /usr/share/dbus-1/session.conf: <!-- For the session bus, override the default relatively-low limits /usr/share/dbus-1/session.conf: with essentially infinite limits, since the bus is just running /usr/share/dbus-1/session.conf: to worry about. In some cases, we do set the limits lower than /usr/share/dbus-1/session.conf: "all available memory" if exceeding the limit is almost certainly a bug, /usr/share/dbus-1/session.conf: having the bus enforce a limit is nicer than a huge memory leak. But the /usr/share/dbus-1/session.conf: intent is that these limits should never be hit. --> /usr/share/dbus-1/session.conf: <!-- the memory limits are 1G instead of say 4G because they can't exceed 32-bit signed int max --> /usr/share/dbus-1/session.conf: <limit name=3D"max_incoming_bytes">1000000000</limit> /usr/share/dbus-1/session.conf: <limit name=3D"max_incoming_unix_fds">250000000</limit> /usr/share/dbus-1/session.conf: <limit name=3D"max_outgoing_bytes">1000000000</limit> /usr/share/dbus-1/session.conf: <limit name=3D"max_outgoing_unix_fds">250000000</limit> /usr/share/dbus-1/session.conf: <limit name=3D"max_message_size">1000000000</limit> /usr/share/dbus-1/session.conf: limit is also relatively low --> /usr/share/dbus-1/session.conf: <limit name=3D"service_start_timeout">120000</limit> /usr/share/dbus-1/session.conf: <limit name=3D"auth_timeout">240000</limit= > /usr/share/dbus-1/session.conf: <limit name=3D"pending_fd_timeout">150000</limit> /usr/share/dbus-1/session.conf: <limit name=3D"max_completed_connections">900</limit> /usr/share/dbus-1/session.conf: <limit name=3D"max_incomplete_connections">92</limit> /usr/share/dbus-1/session.conf: <limit name=3D"max_connections_per_user">100000</limit> /usr/share/dbus-1/session.conf: <limit name=3D"max_pending_service_starts">10000</limit> /usr/share/dbus-1/session.conf: <limit name=3D"max_names_per_connection">50000</limit> /usr/share/dbus-1/session.conf: <limit name=3D"max_match_rules_per_connection">50000</limit> /usr/share/dbus-1/session.conf: <limit name=3D"max_replies_per_connection">50000</limit> > These are arbitrary limits intended to prevent denial of service attacks. > > For example, increasing the maximum number of completed connections > might could look like this: > > $ sudo tee /etc/dbus-1/system.d/local-max-connections.conf <<EOF > <busconfig> > <limit name=3D"max_completed_connections">32768</limit> > </busconfig> > EOF > > If your system is massively multi-user, then, yes, you can expect to need > to increase the arbitrary limits. The defaults are suitable for a system > with perhaps 10 concurrent users - more if they are only running small > text-based environments, but perhaps fewer if they are all running full > GUI sessions. > > > Mar 05 07:46:08 compute-server xdg-desktop-por[35472]: error: > > GDBus.Error:org.freedesktop.DBus.Error.LimitsExceeded: The maximum > > number of active connections has been reached > > This indicates that either max_completed_connections is not high enough, > or a malicious or buggy process is opening lots of connections. > The default on the system bus is to allow 2048 completed (active) > connections, with each user limited to 256 connections, so that users > cannot carry out a denial-of-service on the whole system unless at least > 8 users work together to achieve it. Is there a way to check what the default is for the system bus as it (i.e., max_completed_connections) is not visible at both /etc/bus-1 and /usr/share/dbus-1/? > > The default on the session bus is 100000, and the session bus normally > only allows connections from one user, so the limit on connections per > user is also 100000. This is defined as 900 in /usr/share/dbus-1/session.conf as shown in the above code snippet. > > > Mar 05 07:46:18 compute-server dbus[1350]: [system] Failed to activate > > service 'org.freedesktop.hostname1': timed out > > This could indicate that service_start_timeout is not high enough, > although it's perhaps more likely to be a side-effect of running out > of connection quota. The default on the system bus is 25000 (25 seconds). > The default on the session bus is 120000 (120 seconds). Is there a way to check what the default is for the system bus as it (i.e., service_start_timeout) is not visible at both /etc/bus-1 and /usr/share/dbus-1/? > > > Mar 05 07:46:24 compute-server dbus[1350]: [system] Connection has not > > authenticated soon enough, closing it (auth_timeout=3D30000ms, elapsed: > > 30006ms) > > This could indicate that auth_timeout is not high enough, or it could > indicate extremely high load that results in client connections not > getting scheduled promptly, or it could indicate a malicious or buggy > client. The default on the system bus is 30000, meaning 30 seconds > (system.conf says it's 5000, but that's actually wrong). The default > on the session bus is 240000 (240 seconds). Is it possible to have this error as a side-effect of the connection issues= ? > > > <!-- default for this is 900 --> > > <limit name=3D"max_completed_connections">32768</limit> > > Where are you getting that default from? The default in dbus is > 2048 for the system bus, and 100000 for the session bus. > Does something else on your system set it to 900? max_completed_connections is defined as 900 in /usr/share/dbus-1/session.conf as shown in the above code snippet. > > > <!-- default for this is 92 --> > > <limit name=3D"max_incomplete_connections">1000</limit> > > Where are you getting that default from? The default in dbus is 64. > Does something else on your system set it to 92? max_incomplete_connections is defined as 92 in /usr/share/dbus-1/session.conf as shown in the above code snippet. > > > <!-- default for this is 100000 --> > > <limit name=3D"max_connections_per_user">150000</limit> > > </busconfig> > > The default for the system bus is 256. The default for the session > bus is 100000, but the error messages you quoted are for the system bus. max_connections_per_user is defined as 100000 in /usr/share/dbus-1/session.conf as shown in the above code snippet. > > It never makes sense to set max_connections_per_user higher than > max_completed_connections, and if you do that on the system bus, it's an > easy denial of service attack: a malicious user could use up all of the > connection quota on their own, preventing other users from connecting. Is it possible that our D-Bus service is corrupted (as we never did any modifications on these files)? > > smcv --=20 "Bu mesaj (ve ekleri) gizli bilgi i=C3=A7ermektedir ve sadece g=C3=B6nderil= en ki=C5=9Fiye=20 y=C3=B6neliktir. Bu e-mailin muhatab=C4=B1 de=C4=9Filseniz veya i=C3=A7eri= =C4=9Fi ile ilginiz yoksa,=20 Yeditepe =C3=9Cniversitesinin onay=C4=B1 olmaks=C4=B1z=C4=B1n bu mesaj=C4= =B1n okunmas=C4=B1,=20 de=C4=9Fi=C5=9Ftirilmesi, kopyalanmas=C4=B1, =C3=BC=C3=A7=C3=BCnc=C3=BC ki= =C5=9Filere a=C3=A7=C4=B1klanmas=C4=B1, yay=C4=B1nlanmas=C4=B1,=20 if=C5=9Fa edilmesi veya iletilmesi yasakt=C4=B1r. Bu mesaj=C4=B1n g=C3=B6nd= erilmek istendi=C4=9Fi=20 ki=C5=9Fi de=C4=9Filseniz (ya da bu e-posta'y=C4=B1 yanl=C4=B1=C5=9Fl=C4=B1= kla ald=C4=B1ysan=C4=B1z), l=C3=BCtfen=20 yollayan ki=C5=9Fiyi hemen haberdar ediniz ve mesaj=C4=B1 sisteminizden der= hal=20 siliniz. E-mail iletiminin g=C3=BCvenli veya hatas=C4=B1z oldu=C4=9Funun ga= rantisi=20 olmad=C4=B1=C4=9F=C4=B1ndan ge=C3=A7 veya eksik iletim veya i=C3=A7erik ve = bilgilerde eksiklik,=20 kay=C4=B1p, de=C4=9Fi=C5=9Fiklik veya vir=C3=BCs olabilir. Bu nedenle, bu m= esaj=C4=B1n iletiminden=20 dolay=C4=B1, Yeditepe =C3=9Cniversitesi , i=C3=A7erikteki hata, eksiklik, d= o=C4=9Frulu=C4=9Fun ve=20 gizlili=C4=9Fin ihlalinden veya bu yolla bilgi payla=C5=9F=C4=B1m=C4=B1, il= etimi, depolanmas=C4=B1=20 gibi herhangi bir kullan=C4=B1m=C4=B1ndan hi=C3=A7bir =C5=9Fekilde sorumlu = de=C4=9Fildir. Bu mesaj=C4=B1n=20 i=C3=A7eri=C4=9Fi yazar=C4=B1na ait olup, =C3=9Cniversitemizin g=C3=B6r=C3= =BC=C5=9Flerini i=C3=A7ermeyebilir. Bu=20 mesaj=C4=B1n i=C3=A7eri=C4=9Finde ge=C3=A7en =C3=9Cniversitemizin ad veya n= an=C4=B1ma yarat=C4=B1lan fikri ve=20 s=C4=B1nai haklar =C3=9Cniversitemize ait olup, maddi ve manevi t=C3=BCm ha= klar=C4=B1=20 sakl=C4=B1d=C4=B1r.=E2=80=9D =E2=80=9CThis Message (including any attachments) contains confidential=20 information and is intended only for the individual named. If you are not= =20 the named adressee or not related with the content of this Message, you are= =20 forbidden to read, disseminate, distribute, copy, reproduce or modify this= =20 mail by Yeditepe University. Please notfy the sender immediately if you=20 have received this e-mail by mistake and delete this e-mail from your=20 system. E-mail transmisson can not be guaranteed to be secure or error-free= =20 as the mail may arrive late or incomplete or the information could be=20 intercepted, corrupted, lost, destroyed, amended, , or contain viruses.=20 Yeditepe University therefore does not accept liability for any errors,=20 loss of integrity or confidentiality or ommissions in the contents of this= =20 Message or for the information transmission, reception, storage of use of= =20 such in any way whatsoever, which arise as a result of e-mail transmission.= =20 Any opinions expressed in this message are those of the author and may not= =20 necessarily reflect the opinions of Our University. Copyright in documents=20 created by or on behalf of our University remains vested in us, and we=20 assert all of our moral and intellectual property rights." --000000000000de18f4062fd22cc9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi Simon,<br><br>Thank you for your detailed response and = support. I shared my answers inline below.<br><br>On Fri, Mar 7, 2025 at 6:= 00=E2=80=AFPM Simon McVittie <<a href=3D"mailto:smcv-ZGY8ohtN/[email protected]">smcv= @collabora.com</a>> wrote:<br>><br>> On Fri, 07 Mar 2025 at 17:29:= 10 +0300, Abdullah Y=C4=B1ld=C4=B1z wrote:<br>> > Mar 05 07:46:08 com= pute-server xdg-desktop-por[35472]: error:<br>> > GDBus.Error:org.fre= edesktop.DBus.Error.LimitsExceeded: The maximum<br>> > number of acti= ve connections has been reached<br>> > Mar 05 07:46:18 compute-server= dbus[1350]: [system] Failed to activate<br>> > service 'org.free= desktop.hostname1': timed out<br>> > Mar 05 07:46:24 compute-serv= er dbus[1350]: [system] Connection has not<br>> > authenticated soon = enough, closing it (auth_timeout=3D30000ms, elapsed:<br>> > 30006ms)<= br>><br>> This is your system bus. There is normally one per bootable= system:<br>> at least one per kernel, but whole-system containers that = behave like<br>> a full system from init upwards, like lxc, Incus or sys= temd-nspawn,<br>> sometimes have their own. It is intended to be for use= rs to talk to<br>> system services, and for system services to talk to e= ach other.<br>><br>> > This is what I observe when I check /usr/sh= are/dbus-1/session.conf<br>><br>> This is configuration for your sess= ion bus (not the same thing), sometimes<br>> referred to as the user bus= . There is normally one per (system,uid)<br>> pair. It is intended to be= for unprivileged programs running as the user<br>> to talk to each othe= r.<br>><br>> Configuration files/directories with "system" = in the name are for the<br>> system bus, configuration files/directories= with "session" in the name<br>> are for the session bus (user= bus), and neither affects the other bus.<br>><br>> > I want to un= derstand that overriding some of the D-Bus specific values<br>> > (as= shown below) would help to fix the issue:<br>> ><br>> > <bu= sconfig><br>> > =C2=A0<!-- default for this is 900 --><br>&g= t; > =C2=A0<limit name=3D"max_completed_connections">327= 68</limit><br>> > =C2=A0<!-- default for this is 92 --><b= r>> > =C2=A0<limit name=3D"max_incomplete_connections"&g= t;1000</limit><br>> > =C2=A0<!-- default for this is 100000 = --><br>> > =C2=A0<limit name=3D"max_connections_per_user&q= uot;>150000</limit><br>> > </busconfig><br>><br>>= ; It probably would, but only if you override them in the right place.<br>&= gt;<br>> The system bus limits can be overridden by writing a file into<= br>> /etc/dbus-1/system.d/*.conf (local configuration by the sysadmin)<b= r>> or /usr/share/dbus-1/system.d/*.conf (configuration by OS vendor or<= br>> packages, e.g. from RPM or dpkg). Their defaults are hard-coded int= o<br>> the dbus-daemon, but for convenient reference there is a commente= d-out<br>> list of default values in /usr/share/dbus-1/system.conf (alth= ough I now<br>> notice that some of them are out of date).<br>><br><b= r>In /usr/share/dbus-1/, there are no commented-out default values availabl= e except session.conf:<br><br><font face=3D"monospace">$ grep -r "limi= t" /usr/share/dbus-1/<br>/usr/share/dbus-1/interfaces/org.freedesktop.= PackageKit.Transaction.xml: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0whilst= it is running. There is no limit to the number of times this<br>/usr/share= /dbus-1/interfaces/org.freedesktop.PackageKit.Transaction.xml: =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0This option is only really interestin= g on embedded devices with a limited amount of<br>/usr/share/dbus-1/interfa= ces/org.freedesktop.PackageKit.Transaction.xml: =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0The tree does not have any depth or bredth limits, alt= hough it should be kept<br>/usr/share/dbus-1/interfaces/org.freedesktop.Pac= kageKit.xml: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0The maximum nu= mber of past transactions to return, or 0 for no limit.<br>/usr/share/dbus-= 1/interfaces/org.freedesktop.portal.NetworkMonitor.xml: =C2=A0 =C2=A0 =C2= =A0 =C2=A0the default connection that is subject ot limitations<br>/usr/sha= re/dbus-1/session.conf: =C2=A0<!-- For the session bus, override the def= ault relatively-low limits <br>/usr/share/dbus-1/session.conf: =C2=A0 =C2= =A0 =C2=A0 with essentially infinite limits, since the bus is just running = <br>/usr/share/dbus-1/session.conf: =C2=A0 =C2=A0 =C2=A0 to worry about. In= some cases, we do set the limits lower than <br>/usr/share/dbus-1/session.= conf: =C2=A0 =C2=A0 =C2=A0 "all available memory" if exceeding th= e limit is almost certainly a bug, <br>/usr/share/dbus-1/session.conf: =C2= =A0 =C2=A0 =C2=A0 having the bus enforce a limit is nicer than a huge memor= y leak. But the <br>/usr/share/dbus-1/session.conf: =C2=A0 =C2=A0 =C2=A0 in= tent is that these limits should never be hit. --><br>/usr/share/dbus-1/= session.conf: =C2=A0<!-- the memory limits are 1G instead of say 4G beca= use they can't exceed 32-bit signed int max --><br>/usr/share/dbus-1= /session.conf: =C2=A0<limit name=3D"max_incoming_bytes">100= 0000000</limit><br>/usr/share/dbus-1/session.conf: =C2=A0<limit na= me=3D"max_incoming_unix_fds">250000000</limit><br>/usr/s= hare/dbus-1/session.conf: =C2=A0<limit name=3D"max_outgoing_bytes&q= uot;>1000000000</limit><br>/usr/share/dbus-1/session.conf: =C2=A0&= lt;limit name=3D"max_outgoing_unix_fds">250000000</limit>= ;<br>/usr/share/dbus-1/session.conf: =C2=A0<limit name=3D"max_messa= ge_size">1000000000</limit><br>/usr/share/dbus-1/session.conf= : =C2=A0 =C2=A0 =C2=A0 limit is also relatively low --><br>/usr/share/db= us-1/session.conf: =C2=A0<limit name=3D"service_start_timeout"= >120000</limit> =C2=A0<br>/usr/share/dbus-1/session.conf: =C2=A0&l= t;limit name=3D"auth_timeout">240000</limit><br>/usr/sha= re/dbus-1/session.conf: =C2=A0<limit name=3D"pending_fd_timeout&quo= t;>150000</limit><br>/usr/share/dbus-1/session.conf: =C2=A0<lim= it name=3D"max_completed_connections">900</limit><br>/us= r/share/dbus-1/session.conf: =C2=A0<limit name=3D"max_incomplete_co= nnections">92</limit><br>/usr/share/dbus-1/session.conf: =C2= =A0<limit name=3D"max_connections_per_user">100000</limi= t><br>/usr/share/dbus-1/session.conf: =C2=A0<limit name=3D"max_p= ending_service_starts">10000</limit><br>/usr/share/dbus-1/ses= sion.conf: =C2=A0<limit name=3D"max_names_per_connection">5= 0000</limit><br>/usr/share/dbus-1/session.conf: =C2=A0<limit name= =3D"max_match_rules_per_connection">50000</limit><br>/us= r/share/dbus-1/session.conf: =C2=A0<limit name=3D"max_replies_per_c= onnection">50000</limit></font><br><br>> These are arbitra= ry limits intended to prevent denial of service attacks.<br>><br>> Fo= r example, increasing the maximum number of completed connections<br>> m= ight could look like this:<br>><br>> =C2=A0 =C2=A0 $ sudo tee /etc/db= us-1/system.d/local-max-connections.conf <<EOF<br>> =C2=A0 =C2=A0 = <busconfig><br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 <limit name=3D&quo= t;max_completed_connections">32768</limit><br>> =C2=A0 =C2= =A0 </busconfig><br>> =C2=A0 =C2=A0 EOF<br>><br>> If your sy= stem is massively multi-user, then, yes, you can expect to need<br>> to = increase the arbitrary limits. The defaults are suitable for a system<br>&g= t; with perhaps 10 concurrent users - more if they are only running small<b= r>> text-based environments, but perhaps fewer if they are all running f= ull<br>> GUI sessions.<br>><br>> > Mar 05 07:46:08 compute-serv= er xdg-desktop-por[35472]: error:<br>> > GDBus.Error:org.freedesktop.= DBus.Error.LimitsExceeded: The maximum<br>> > number of active connec= tions has been reached<br>><br>> This indicates that either max_compl= eted_connections is not high enough,<br>> or a malicious or buggy proces= s is opening lots of connections.<br>> The default on the system bus is = to allow 2048 completed (active)<br>> connections, with each user limite= d to 256 connections, so that users<br>> cannot carry out a denial-of-se= rvice on the whole system unless at least<br>> 8 users work together to = achieve it.<div><br></div><div>Is there a way to check what the default=C2= =A0is for the system bus as it (i.e., max_completed_connections) is not vis= ible at both /etc/bus-1 and=C2=A0/usr/share/dbus-1/?<br></div><div><br>>= <div>> The default on the session bus is 100000, and the session bus nor= mally<br>> only allows connections from one user, so the limit on connec= tions per<br>> user is also 100000.</div><div><br></div><div>This is def= ined as 900 in /usr/share/dbus-1/session.conf as shown in the above code sn= ippet.</div><div><br>><br>> > Mar 05 07:46:18 compute-server dbus[= 1350]: [system] Failed to activate<br>> > service 'org.freedeskto= p.hostname1': timed out<br>><br>> This could indicate that servic= e_start_timeout is not high enough,<br>> although it's perhaps more = likely to be a side-effect of running out<br>> of connection quota. The = default on the system bus is 25000 (25 seconds).<br>> The default on the= session bus is 120000 (120 seconds).</div><div><br></div><div>Is there a w= ay to check what the default=C2=A0is for the system bus as it (i.e., servic= e_start_timeout) is not visible at both /etc/bus-1 and=C2=A0/usr/share/dbus= -1/?</div><div><br>><br>> > Mar 05 07:46:24 compute-server dbus[13= 50]: [system] Connection has not<br>> > authenticated soon enough, cl= osing it (auth_timeout=3D30000ms, elapsed:<br>> > 30006ms)</div><div>= ><br>> This could indicate that auth_timeout is not high enough, or i= t could<br>> indicate extremely high load that results in client connect= ions not<br>> getting scheduled promptly, or it could indicate a malicio= us or buggy<br>> client. The default on the system bus is 30000, meaning= 30 seconds<br>> (system.conf says it's 5000, but that's actuall= y wrong).=C2=A0 The default<br>> on the session bus is 240000 (240 secon= ds).</div><div><br></div><div>Is it possible to have this error as a side-e= ffect of the connection issues?</div><div><br>><br>> > =C2=A0<!= -- default for this is 900 --><br>> > =C2=A0<limit name=3D"= ;max_completed_connections">32768</limit><br>><br>> Whe= re are you getting that default from? The default in dbus is<br>> 2048 f= or the system bus, and 100000 for the session bus.<br>> Does something e= lse on your system set it to 900?</div><div><br></div><div>max_completed_co= nnections is defined as 900 in /usr/share/dbus-1/session.conf as shown in t= he above code snippet.<br></div><div><br>><br>> > =C2=A0<!-- de= fault for this is 92 --><br>> > =C2=A0<limit name=3D"max_i= ncomplete_connections">1000</limit><br>><br>> Where are= you getting that default from? The default in dbus is 64.<br>> Does som= ething else on your system set it to 92?</div><div><br></div><div>max_incom= plete_connections is defined as 92 in /usr/share/dbus-1/session.conf as sho= wn in the above code snippet.<br></div><div><br>><br>> > =C2=A0<= ;!-- default for this is 100000 --><br>> > =C2=A0<limit name=3D= "max_connections_per_user">150000</limit><br>> > &= lt;/busconfig><br>><br>> The default for the system bus is 256. Th= e default for the session<br>> bus is 100000, but the error messages you= quoted are for the system bus.</div><div><br></div><div>max_connections_pe= r_user is defined as 100000=C2=A0in /usr/share/dbus-1/session.conf as shown= in the above code snippet.<br></div><div><br>><br>> It never makes s= ense to set max_connections_per_user higher than<br>> max_completed_conn= ections, and if you do that on the system bus, it's an<br>> easy den= ial of service attack: a malicious user could use up all of the<br>> con= nection quota on their own, preventing other users from connecting.</div><d= iv><br></div><div>Is it possible that our D-Bus service is corrupted (as we= never did any modifications on these files)?</div><div><br>><br>> = =C2=A0 =C2=A0 smcv</div></div></div> <br> <font face=3D"Arial" color=3D"Gray" size=3D"1" style=3D"background-color:rg= b(255,255,255)">"Bu mesaj (ve ekleri) gizli bilgi i=C3=A7ermektedir ve= sadece g=C3=B6nderilen ki=C5=9Fiye y=C3=B6neliktir. Bu e-mailin muhatab=C4= =B1 de=C4=9Filseniz veya i=C3=A7eri=C4=9Fi ile ilginiz yoksa, Yeditepe =C3= =9Cniversitesinin onay=C4=B1 olmaks=C4=B1z=C4=B1n bu mesaj=C4=B1n okunmas= =C4=B1, de=C4=9Fi=C5=9Ftirilmesi, kopyalanmas=C4=B1, =C3=BC=C3=A7=C3=BCnc= =C3=BC ki=C5=9Filere a=C3=A7=C4=B1klanmas=C4=B1, yay=C4=B1nlanmas=C4=B1, if= =C5=9Fa edilmesi veya iletilmesi yasakt=C4=B1r. Bu mesaj=C4=B1n g=C3=B6nder= ilmek istendi=C4=9Fi ki=C5=9Fi de=C4=9Filseniz (ya da bu e-posta'y=C4= =B1 yanl=C4=B1=C5=9Fl=C4=B1kla ald=C4=B1ysan=C4=B1z), l=C3=BCtfen yollayan = ki=C5=9Fiyi hemen haberdar ediniz ve mesaj=C4=B1 sisteminizden derhal silin= iz. E-mail iletiminin g=C3=BCvenli veya hatas=C4=B1z oldu=C4=9Funun garanti= si olmad=C4=B1=C4=9F=C4=B1ndan ge=C3=A7 veya eksik iletim veya i=C3=A7erik = ve bilgilerde eksiklik, kay=C4=B1p, de=C4=9Fi=C5=9Fiklik veya vir=C3=BCs ol= abilir. Bu nedenle, bu mesaj=C4=B1n iletiminden dolay=C4=B1, Yeditepe =C3= =9Cniversitesi , i=C3=A7erikteki hata, eksiklik, do=C4=9Frulu=C4=9Fun ve gi= zlili=C4=9Fin ihlalinden veya bu yolla bilgi payla=C5=9F=C4=B1m=C4=B1, ilet= imi, depolanmas=C4=B1 gibi herhangi bir kullan=C4=B1m=C4=B1ndan hi=C3=A7bir= =C5=9Fekilde sorumlu de=C4=9Fildir. Bu mesaj=C4=B1n i=C3=A7eri=C4=9Fi yaza= r=C4=B1na ait olup, =C3=9Cniversitemizin g=C3=B6r=C3=BC=C5=9Flerini i=C3=A7= ermeyebilir.<br><br>Bu mesaj=C4=B1n i=C3=A7eri=C4=9Finde ge=C3=A7en =C3=9Cn= iversitemizin ad veya nan=C4=B1ma yarat=C4=B1lan fikri ve s=C4=B1nai haklar= =C3=9Cniversitemize ait olup, maddi ve manevi t=C3=BCm haklar=C4=B1 sakl= =C4=B1d=C4=B1r.=E2=80=9D<br></font><br style=3D"color:rgb(34,34,34);font-fa= mily:arial,sans-serif;background-color:rgb(255,255,255)"><font face=3D"Aria= l" color=3D"Gray" size=3D"1" style=3D"background-color:rgb(255,255,255)">= =E2=80=9CThis Message (including any attachments) contains confidential inf= ormation and is intended only for the individual named. If you are not the = named adressee or not related with the content of this Message, you are for= bidden to read, disseminate, distribute, copy, reproduce or modify this mai= l by Yeditepe University. Please notfy the sender immediately if you have r= eceived this e-mail by mistake and delete this e-mail from your system. E-m= ail transmisson can not be guaranteed to be secure or error-free as the mai= l may arrive late or incomplete or the information could be intercepted, co= rrupted, lost, destroyed, amended, , or contain viruses. Yeditepe Universit= y therefore does not accept liability for any errors, loss of integrity or = confidentiality or ommissions in the contents of this Message or for the in= formation transmission, reception, storage of use of such in any way whatso= ever, which arise as a result of e-mail transmission. Any opinions expresse= d in this message are those of the author and may not necessarily reflect t= he opinions of Our University.<br><br>Copyright in documents created by or = on behalf of our University remains vested in us, and we assert all of our = moral and intellectual property rights."</font> --000000000000de18f4062fd22cc9--