[SSSD-users] Problems with sssd 1.11.1 on ubuntu 13.10

Lukas Slebodnik lslebodn at redhat.com
Wed Oct 23 08:40:50 UTC 2013


On (23/10/13 10:15), Melvin Williams wrote:
>Thanks for the quick reply. Yes I had trailing spaces. Removing them
>partially solved the problem. Now the starting process ends with:
>
>(Wed Oct 23 10:06:14 2013) [sssd] [sbus_dispatch] (0x4000): dbus conn:
>0x2285bc0
>(Wed Oct 23 10:06:14 2013) [sssd] [sbus_dispatch] (0x0080): Connection is
>not open for dispatching.
>(Wed Oct 23 10:06:14 2013) [sssd] [sss_child_handler] (0x2000): waitpid
>failed [10]: Keine Kind-Prozesse
>(Wed Oct 23 10:06:14 2013) [sssd] [mt_svc_exit_handler] (0x0040): Child
>[JAEGER] exited with code [3]
                           ^^^
Return code 3 mean that backend provider cannot be initialized.

Could you send your configuration file?
How did you configure sssd with ad provider? (manualy or with some tool?)

Could you put "debug_level = 0x7770" into domain section and attach
log file sssd_<ndomain_name>.log

LS

>(Wed Oct 23 10:06:14 2013) [sssd] [mt_svc_exit_handler] (0x0010): Process
>[JAEGER], definitely stopped!
>(Wed Oct 23 10:06:14 2013) [sssd] [monitor_quit] (0x0040): Returned with: 1
>(Wed Oct 23 10:06:14 2013) [sssd] [monitor_quit] (0x0020): Terminating
>[nss][6416]
>(Wed Oct 23 10:06:14 2013) [sssd] [monitor_quit] (0x0020): Couldn't kill
>[nss][6416]: [Kein passender Prozess gefunden]
>(Wed Oct 23 10:06:14 2013) [sssd] [monitor_quit] (0x0020): Terminating
>[pam][6415]
>(Wed Oct 23 10:06:14 2013) [sssd] [monitor_quit] (0x0020): Couldn't kill
>[pam][6415]: [Kein passender Prozess gefunden]
>(Wed Oct 23 10:06:14 2013) [sssd] [sbus_remove_watch] (0x2000):
>0x227a360/0x2272a30
>
>
>Any hint?
>
>
>2013/10/23 Lukas Slebodnik <lslebodn at redhat.com>
>
>> On (23/10/13 09:47), Melvin Williams wrote:
>> >I have installed sssd 1.11.1 from the repository on Ubuntu 13.10. First of
>> >all when I tried to start sssd with the "emurate = true" option in the
>> >domain section I get the following error:
>> >
>> > [sssd] [confdb_get_domain_internal] (0x0010): Invalid value for enumerate
>> >
>> >So I commented this out. Now I tried to start via command line:  sssd -d
>> > 0xFFF0 -f
>> >
>> >Doing so I found this in my error logs:
>> >
>> >[load_backend_module] (0x0010): Unable to load ad  module with path
>> >(/usr/lib/x86_64-linux-gnu/sssd/libsss_ad .so), error:
>> >/usr/lib/x86_64-linux-gnu/sssd/libsss_ad .so
>> >
>> >There is a space in the library name "libsss_ad .so". Is this the name the
>> >program is looking for? If so there must be a typo or something like this
>> >in the code. If not and it is a configuration matter could someone please
>> >tell me how to fix this issue.
>> >
>> >Regards
>>
>> It looks like problem with parsing configuration file /etc/sssd/sssd.conf.
>> (Bug in libini)
>>
>> https://git.fedorahosted.org/cgit/ding-libs.git/commit/?id=7a2eb259b2e22ce5e2395fbf578b5fef57667489
>>
>> Do you have any trailing white spaces on line with id_provider?
>> id_provider = ad
>>
>> Regards,
>> LS
>> _______________________________________________
>> sssd-users mailing list
>> sssd-users at lists.fedorahosted.org
>> https://lists.fedorahosted.org/mailman/listinfo/sssd-users
>>

>_______________________________________________
>sssd-users mailing list
>sssd-users at lists.fedorahosted.org
>https://lists.fedorahosted.org/mailman/listinfo/sssd-users



More information about the sssd-users mailing list