[Spacewalk-list] Interesting OSAD Problem

[Andy Ingham]

To close the circle, so to speak, be aware that selinux-policy-3.7.19-260 fixes this issue.

Once you've got that package updated, then, don't forget to go back and REMOVE the previously implemented workaround.

Do so with: semanage permissive -d osad_t

Verify via: semanage permissive -l

Reference:  https://bugzilla.redhat.com/show_bug.cgi?id=1161288

Andy

From: Andy Ingham <andy.ingham at duke.edu<mailto:andy.ingham at duke.edu>>
Date: Tuesday, December 2, 2014 at 1:56 PM
To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Subject: Re: [Spacewalk-list] Interesting OSAD Problem

Jon --

This topic came up about a month ago.

The quick and dirty workaround until this gets fixed:

semanage permissive -a osad_t

The background is at:  http://osdir.com/ml/spacewalk-list/2014-11/msg00090.html

Andy


From: <Glennie>, Jonathan - 0443 - MITLL <jrglenni at ll.mit.edu<mailto:jrglenni at ll.mit.edu>>
Reply-To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Date: Tuesday, December 2, 2014 at 1:39 PM
To: "spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>" <spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>>
Subject: Re: [Spacewalk-list] Interesting OSAD Problem

Actually it's somewhat a permissions problem.... Disabling selinux and restarting now lets the service start correctly.  Looks like I need to investigate what selinux is unhappy about.

From:spacewalk-list-bounces at redhat.com<mailto:spacewalk-list-bounces at redhat.com> [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Glennie, Jonathan - 0443 - MITLL
Sent: Tuesday, December 02, 2014 1:28 PM
To: spacewalk-list at redhat.com<mailto:spacewalk-list at redhat.com>
Subject: [Spacewalk-list] Interesting OSAD Problem

Hello All-

I'm having an interesting osad problem... osa-dispatcher starts fine on the server, but from a client, attempting to do a "service osad start" generates the "Unable to connect to jabber servers" log messages.  However, if I manually launch osad from the command line, either by running "osad _N -v -v -v -v" or simply typing "osad", everything launches just fine... I see the connection on the server side and I can successfully ping/push commands to it from the GUI.

What could be causing he difference in behavior?  I've checked and no matter what way the service is launched, it runs as root so I wouldn't think it's a permissions issue... Thanks for any help.

-Jon

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20141217/dfaa8aa5/attachment.htm>