On Jun 19, 2012, at 5:20 PM, Stephen Gallagher wrote: On Tue, 2012-06-19 at 15:15 +0000, Steve Traylen wrote: On Jun 19, 2012, at 3:29 PM, Stephen Gallagher wrote:
On Tue, 2012-06-19 at 13:09 +0000, Steve Traylen wrote: sssd does not want to start for me on RHEL5. # rpm -q sssd sssd-1.5.1-49.el5_8.1 on both RHEL5 and SLC5 results in # /usr/sbin/sssd -i -d 8 Aborted This is both with our sssd.conf which is working fine over on RHEL6 but also for the default sssd.conf that comes with the package. The end of an strace is here: http://pastie.org/4114307 , if I delete the 'var/lib/sss/db/config.ldb file then it is created again before the 'Aborted' happens. Nothing is logged to syslog or sssd.log. Any ideas. Could you do the following: yum install gdb debuginfo-install sssd gdb /usr/sbin/sssd at the gdb console: run -i -d 8 When it dies: bt full Send all the output of that bt full, please. Back trace as below... I also now realize when I thought I was using RHEL earlier I was not , I have yet to confirm this on RHEL, will try to do so. Can you please confirm what version of SSSD you are running. Also, what version of libldb and libtevent. If it's not RHEL, what platform are you running on? Sure SLC 5.8 which is meant to binary to compatible : Staring with a new machine now, installing sssd.x86_64 0:1.5.1-49.el5_8.1 pulled in the following deps: c-ares.x86_64 0:1.6.0-5.el5 cyrus-sasl-gssapi.x86_64 0:2.1.22-5.el5_4.3 libcollection.x86_64 0:0.6.0-10.el5 libdhash.x86_64 0:0.4.2-10.el5 libini_config.x86_64 0:0.6.1-10.el5 libipa_hbac.x86_64 0:1.5.1-49.el5_8.1 libldb.x86_64 0:0.9.10-33.el5 libpath_utils.x86_64 0:0.2.1-10.el5 libref_array.x86_64 0:0.1.1-10.el5 libtalloc.x86_64 0:2.0.1-11.el5 libtalloc-compat1.x86_64 0:2.0.1-11.el5 libtdb.x86_64 0:1.2.1-6.el5 libtevent.x86_64 0:0.9.8-10.el5 openldap24-libs.x86_64 0:2.4.23-5.el5 sssd-client.x86_64 0:1.5.1-49.el5_8.1 ]# rpm -q libtevent libldb libtevent-0.9.8-10.el5 libldb-0.9.10-33.el5 # service sssd start Starting sssd: /bin/bash: line 1: 4305 Aborted /usr/sbin/sssd -f -D [FAILED] /var/log/sssd/sssd.log is completely empty, nothing is ever written. True with -d 10 as well. I've checked there are no AVC entries in the audit.log in case its and selinux thing. The default sssd.conf just contiains: [sssd] config_file_version = 2 services = nss, pam [nss] [pam] but it looks to be irrelevant, starting the service does not update the access time on sssd.conf.
_______________________________________________ sssd-devel mailing list sssd-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/sssd-devel
