[SSSD] The Monitor returned an error [org.freedesktop.DBus.Error.NoReply]

Mathias Gug mathiaz at ubuntu.com
Tue Aug 25 01:45:06 UTC 2009


Hi,

While trying to start sssd 0.5.0 on an Ubuntu Karmic system, I've run
into the following error:

[sssd[dp]] [id_callback] (0): The Monitor returned an error
[org.freedesktop.DBus.Error.NoReply]
[sssd] [global_checks_handler] (0): Unknown child (2552) did exit
[sssd[nss]] [sss_dp_init] (0): Failed to connect to monitor services.
[sssd[nss]] [sss_process_init] (0): fatal error setting up backend connector
[sssd[be[files]]] [be_cli_init] (0): Failed to connect to monitor services.
[sssd[be[files]]] [be_process_init] (0): fatal error setting up server bus
[sssd[be[files]]] [main] (0): Could not initialize backend [5]
[sssd[pam]] [sss_dp_init] (0): Failed to connect to monitor services.
[sssd[pam]] [sss_process_init] (0): fatal error setting up backend connector
[sssd] [global_checks_handler] (0): Unknown child (2553) did exit
[sssd] [global_checks_handler] (0): Unknown child (2554) did exit
[sssd] [global_checks_handler] (0): Unknown child (2555) did exit
[sssd[nss]] [sss_dp_init] (0): Failed to connect to monitor services.
[sssd[nss]] [sss_process_init] (0): fatal error setting up backend connector
[sssd[pam]] [sss_dp_init] (0): Failed to connect to monitor services.
[sssd[pam]] [sss_process_init] (0): fatal error setting up backend connector
[sssd[be[files]]] [be_cli_init] (0): Failed to connect to monitor services.
[sssd[be[files]]] [be_process_init] (0): fatal error setting up server bus
[sssd[be[files]]] [main] (0): Could not initialize backend [5]
[sssd[nss]] [sss_dp_init] (0): Failed to connect to monitor services.
[sssd[nss]] [sss_process_init] (0): fatal error setting up backend connector
[sssd[pam]] [sss_dp_init] (0): Failed to connect to monitor services.
[sssd[pam]] [sss_process_init] (0): fatal error setting up backend connector
[...]

dbus is installed and running:

$ ps -ef | grep dbus
106       2382     1  0 21:27 ?        00:00:00 /bin/dbus-daemon --system

The sssd configuration is the example configuration with using the
LOCAL domain (/etc/sssd/sssd.conf):

[services]
description = Local Service Configuration
activeServices = nss, dp, pam
# Number of times services should attempt to reconnect in the
# event of a Data Provider crash or restart before they give up
reconnection_retries = 3

[services/nss]
description = NSS Responder Configuration
# the following prevents sssd for searching for the root user/group in
# all domains (you can add here a comma separated list of system accounts are
# always going to be /etc/passwd users, or that you want to filter out)
filterGroups = root
filterUsers = root

[services/dp]
description = Data Provider Configuration

[services/pam]
description = PAM Responder Configuration

[services/monitor]
description = Service Monitor Configuration
#if a backend is particularly slow you can raise this timeout here
sbusTimeout = 30

[domains]
description = Domains served by SSSD
domains = LOCAL

[domains/LOCAL]
description = LOCAL migration domain
enumerate = 3
minId = 500
magicPrivateGroups = FALSE
legacy = TRUE

provider = files

-- 
Mathias Gug
Ubuntu Developer  http://www.ubuntu.com



More information about the sssd-devel mailing list