osdir.com


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Dbus daemon Issues


Colin,

Thank you for the reply. I should probably elaborate on our setup a little bit. It was a clean install of Ubuntu 16.04 on a server with dual NICs. I then installed the ltsp-server-standalone and gnome-session-flashback and configured the environment for users and thin\fat clients. Thin\Fat clients and user sessions all load without any issues, it's after about 15 users log in that I see the dbus-daemon spike and when I run dbus-monitor --system, I see the following errors...

error time=1516902042.457461 sender=org.freedesktop.DBus -> destination=:1.2076 error_name=org.freedesktop.DBus.Error.LimitsExceeded reply_serial=52599  string "The maximum number of pending replies per connection has been reached"

I tried your suggestion and rebooted the server and again today once we got to 15 users the dbus-daemon started flaking out. It's making our ltsp labs almost unusable until I can figure out how to resolve the dbus issue. Any help is much appreciated. Thanks! 

Regards,
Jeff 

Jeff Donaldson
Technology Director
Newark Charter School
jeff.donaldson at ncs.k12.de.us
(302) 369-2001 ext: 625


-----Original Message-----
From: ubuntu-users [mailto:ubuntu-users-bounces at lists.ubuntu.com] On Behalf Of Colin Watson
Sent: Wednesday, January 24, 2018 2:53 AM
To: ubuntu-users at lists.ubuntu.com
Subject: Re: Dbus daemon Issues

On Tue, Jan 23, 2018 at 08:45:16PM +0000, Donaldson Jeff wrote:
> This past summer I upgraded all of our 12.04 LTSP Servers to a clean 
> install of 16.04. As in the past, I added the following to the 
> /etc/init/dbus.conf file, limit nofile 65334 65334, right above the 
> expect fork line. Even with that in the dbus.conf, I have been having 
> issues when a large number of users\sessions are logged in causing the 
> dbus-daemon to spike the CPU to 100% and stop responding to calls.
> This then prevents any new users from logging in successfully. Have 
> any of you experienced this issue as well? Is there another file(s) in
> 16.04 that need to be edited?

Unless you're doing something quite complex, a clean install of 16.04 will be using systemd, not Upstart, so editing /etc/init/dbus.conf will have no effect.  (You can check this by seeing if the directory /run/systemd/system exists; if it is, then the system in question is using systemd.)

On systemd, the equivalent of what you're doing would be:

  mkdir -p /etc/systemd/system/dbus.service.d
  cat >/etc/systemd/system/dbus.service.d/nofile.conf <<EOF
  [Service]
  LimitNOFILE=65534
  EOF

The name of the file "nofile.conf" can be whatever you like, as long as it's in that directory and ends with ".conf".  The LimitNOFILE option is documented in systemd.exec(5).

Note that I'm not familiar with the particular problem you're having and haven't tested this at all, including whether it's still applicable in
16.04 or might have been fixed in some other way.  This is just a literal translation of your Upstart configuration to systemd.

-- 
Colin Watson                                       [cjwatson at ubuntu.com]

--
ubuntu-users mailing list
ubuntu-users at lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users