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 <[email protected]<mailto:[email protected]>> Reply-To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Tuesday, December 2, 2014 at 1:39 PM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> 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: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Glennie, Jonathan - 0443 - MITLL Sent: Tuesday, December 02, 2014 1:28 PM To: [email protected]<mailto:[email protected]> 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
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
