Description of problem: osad could not be started on Fedora client # systemctl start osad Job for osad.service failed because a fatal signal was delivered causing the control process to dump core. See "systemctl status osad.service" and "journalctl -xe" for details. # journalctl -xe -- Unit osad.service has begun starting up. Nov 22 05:32:06 <hostname> audit[10496]: AVC avc: denied { execmem } for pid=10496 comm="osad" scontext=system_u:system_r:osad_t:s0 tcontext=system_u:system_r:osad_t:s0 tclass=process permissive=0 Nov 22 05:32:06 <hostname> audit[10496]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=system_u:system_r:osad_t:s0 pid=10496 comm="osad" exe="/usr/bin/python3.5" sig=11 Nov 22 05:32:06 <hostname> kernel: osad[10496]: segfault at 0 ip 00007f5aec16082b sp 00007ffdfccced08 error 6 in libffi.so.6.0.2[7f5aec15b000+7000] Nov 22 05:32:06 <hostname> systemd[1]: Started Process Core Dump (PID 10497/UID 0). -- Subject: Unit systemd-coredump has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-coredump has finished starting up. -- -- The start-up result is done. Nov 22 05:32:06 <hostname> audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@22-10497-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 22 05:32:06 <hostname> systemd-coredump[10498]: Failed to compress /var/lib/systemd/coredump/.#core.osad.0.a3eb25840cdb4067bdc46bdf40bad164.10496.1479810726000000000000.lz4b246cc746aa5002f: Invalid argument Nov 22 05:32:06 <hostname> systemd-coredump[10498]: Failed to generate stack trace: invalid `Elf' handle Nov 22 05:32:06 <hostname> systemd-coredump[10498]: Process 10496 (osad) of user 0 dumped core. -- Subject: Process 10496 (osad) dumped core Version-Release number of selected component (if applicable): osad-5.11.74-1.fc24.noarch How reproducible: always Steps to Reproduce: 1. systemctl start osad on Fedora Additional info: setenforce 0 helps
I opened BZ for fedora https://bugzilla.redhat.com/show_bug.cgi?id=1425524
I was able to test the install of osad on a fresh Fedora 26 client system using Spacewalk 2.7 Client repo and there were no issues. osad started and I could schedule remote tasks that ran successfully. I am unable to test on a fresh Fedora 25 client system. I get error trying to rhnreg_ks to my server (f25 or rhel6) - "An unexpected OS error occurred: unsupported XML-RPC protocol"
Whatever SSL issue was causing the failure on Fedora 25 yesterday cleared itself up. Possibly a timing issue - time far enough out of sync on the two systems that SSL failed? - resolved itself, as other team members reported for similar failures to register their own client systems to their servers. Once that issue cleared, I was able to successfully install, start and test osad client on Fedora 25. Closing this bug as the selinux fix to Fedora is confirmed.