[Freeipa-users] IPA wont start, all services fail

[Alexander Bokovoy]

On Wed, 20 Jan 2016, Simpson Lachlan wrote:
>> -----Original Message-----
>> From: Alexander Bokovoy [mailto:abokovoy at redhat.com]
>> Sent: Thursday, 21 January 2016 8:44 AM
>> To: Simpson Lachlan
>> Cc: tbordaz at redhat.com; freeipa-users at redhat.com
>> Subject: Re: [Freeipa-users] IPA wont start, all services fail
>>
>> On Wed, 20 Jan 2016, Simpson Lachlan wrote:
>> >> -----Original Message-----
>> >>
>> >> Is there any coredump available with 389-ds crashing? I've asked you
>> >> to use
>> >> http://www.port389.org/docs/389ds/FAQ/faq.html#debugging-crashes to
>> enable coredumps for 389-ds in one of previous discussions, was it done?
>> >> You seemed to get diverted to winbindd core (which was expected to
>> >> coredump as 389-ds was not available), but if you see 389-ds
>> >> disappearing in several hours without any logging, this means there
>> >> was a crash and we'd like to see the coredump of it.
>> >
>> >Hi Alex,
>> >
>> >I did perform the "Debugging Crashes" steps when you asked, but there
>> >are still no core dumps in /var/log/dirsrv/slapd-INSTANCENAME.
>> Well, perhaps it takes longer to get a crash than what you are expecting.
>>
>> >> You can check also /var/log/audit/audit.log to see if there is a
>> >> trace of a crash. It may take different ways but one crash type is following:
>> >
>> >> type=ANOM_ABEND msg=audit(1453212583.746:2337): auid=4294967295
>> >> uid=983
>> >> gid=980 ses=4294967295 subj=system_u:system_r:dirsrv_t:s0 pid=26079
>> >> comm="ns-slapd" exe="/usr/sbin/ns-slapd" sig=11
>> >
>> >There are no instances of ns-slap in the audit.log, there are a dozen
>> >sig=11s, all of them relate to a "memory violation" in httpd_t, and all
>> >references to dirsrv look like this:
>> >
>> >type=SERVICE_STOP msg=audit(1453174960.933:209): pid=1 uid=0
>> >auid=4294967295 ses=4294967295 subj=kernel
>> >msg='unit=dirsrv at UNIX-CO-ORG-AU comm="systemd"
>> >exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=?
>> >res=success'
>> What are the memory violation for httpd_t? Can you show exact line from
>> audit.log?
>
>
>
>type=ANOM_ABEND msg=audit(1452818553.235:5394): auid=4294967295 uid=48 gid=48 ses=4294967295 subj=system_u:system_r:httpd_t:s0 pid=32704 comm="httpd" reason="memory violation" sig=11
>type=ANOM_ABEND msg=audit(1452818553.258:5395): auid=4294967295 uid=48 gid=48 ses=4294967295 subj=system_u:system_r:httpd_t:s0 pid=32707 comm="httpd" reason="memory violation" sig=11
>type=ANOM_ABEND msg=audit(1452962463.319:1390): auid=4294967295 uid=991 gid=987 ses=4294967295 subj=kernel pid=12939 comm="httpd" reason="memory violation" sig=11
>type=ANOM_ABEND msg=audit(1453071013.594:2471): auid=0 uid=0 gid=0 ses=202 subj=kernel pid=17888 comm="systemd-tty-ask" reason="memory violation" sig=11
>type=ANOM_ABEND msg=audit(1453161444.878:732): auid=4294967295 uid=48 gid=48 ses=4294967295 subj=kernel pid=15219 comm="httpd" reason="memory violation" sig=11
>type=ANOM_ABEND msg=audit(1453162831.092:807): auid=4294967295 uid=991 gid=987 ses=4294967295 subj=kernel pid=17619 comm="httpd" reason="memory violation" sig=11
>type=ANOM_ABEND msg=audit(1453167608.043:869): auid=4294967295 uid=48 gid=48 ses=4294967295 subj=kernel pid=19188 comm="httpd" reason="memory violation" sig=11
>type=ANOM_ABEND msg=audit(1453167608.281:870): auid=4294967295 uid=48 gid=48 ses=4294967295 subj=kernel pid=19191 comm="httpd" reason="memory violation" sig=11
>type=ANOM_ABEND msg=audit(1453174424.305:167): auid=4294967295 uid=48 gid=48 ses=4294967295 subj=kernel pid=13075 comm="httpd" reason="memory violation" sig=11
>type=ANOM_ABEND msg=audit(1453174424.337:168): auid=4294967295 uid=48 gid=48 ses=4294967295 subj=kernel pid=13078 comm="httpd" reason="memory violation" sig=11
>type=ANOM_ABEND msg=audit(1453174959.183:205): auid=4294967295 uid=991 gid=987 ses=4294967295 subj=kernel pid=14220 comm="httpd" reason="memory violation" sig=11
>type=ANOM_ABEND msg=audit(1453174959.183:206): auid=4294967295 uid=991 gid=987 ses=4294967295 subj=kernel pid=14203 comm="httpd" reason="memory violation" sig=11
>type=ANOM_ABEND msg=audit(1453325222.755:1226): auid=4294967295 uid=48 gid=48 ses=4294967295 subj=kernel pid=14716 comm="httpd" reason="memory violation" sig=11
>type=ANOM_ABEND msg=audit(1453325222.825:1227): auid=4294967295 uid=48 gid=48 ses=4294967295 subj=kernel pid=14713 comm="httpd" reason="memory violation" sig=11
>type=ANOM_ABEND msg=audit(1453325558.988:1244): auid=4294967295 uid=991 gid=987 ses=4294967295 subj=kernel pid=18340 comm="httpd" reason="memory violation" sig=11
>type=ANOM_ABEND msg=audit(1453325558.988:1245): auid=4294967295 uid=991 gid=987 ses=4294967295 subj=kernel pid=18357 comm="httpd" reason="memory violation" sig=11
Ok, I see two problems above and they may be related to recently fixed
issue with python-cryptography's use of python-cffi. However, this issue
should not affect CentOS 7.2 as the broken python-cryptography code is
not in RHEL 7.2 at all, so I'm a bit puzzled.

-- 
/ Alexander Bokovoy