Sorry didn't notice the thread had split out in my client and you already had the answer!
On 03/12/2014 09:23, Stuart Green wrote: > > Is the machine CentOS? > > https://bugzilla.redhat.com/show_bug.cgi?id=1161288 > > On 02/12/2014 18:39, Glennie, Jonathan - 0443 - MITLL wrote: >> 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-boun...@redhat.com >> [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Glennie, Jonathan - >> 0443 - MITLL >> Sent: Tuesday, December 02, 2014 1:28 PM >> To: spacewalk-list@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 >> >> >> >> >> >> >> _______________________________________________ >> Spacewalk-list mailing list >> Spacewalk-list@redhat.com >> https://www.redhat.com/mailman/listinfo/spacewalk-list >> >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list
