Re: [Spacewalk-list] OSAD can't connect to host and port - Fresh Install of Spacewalk 2.7

2018-01-07 Thread Robert Paschedag
- This was a fresh install and NO client works? - You don't see any osa-dispatcher or jabber errors in /var/log/messages? Which jabber DB backend do you use? Default BDB? Normally, I do not recommend just removing the jabber database but if really NO clients works on a fresh install, stop

Re: [Spacewalk-list] OSAD can't connect to host and port - Fresh Install of Spacewalk 2.7

2018-01-07 Thread Francis Lee Mondia
Hi Robert, It was not me on that original post but we had very similar issues. - Your clients do not show up as "online" for osad status? - YES - Scheduling a simple remote command for a client does NOT get picked up immediatly by the client? You have to login to the client and run "rhn_check"

Re: [Spacewalk-list] OSAD can't connect to host and port - Fresh Install of Spacewalk 2.7

2018-01-06 Thread Robert Paschedag
In your original post, you said, you can telnet to 5222 and run osad in *very* verbose mode and get connected. So.where do you have problems now? - Your clients do not show up as "online" for osad status? - Scheduling a simple remote command for a client does NOT get picked up immediatly

[Spacewalk-list] OSAD can't connect to host and port - Fresh Install of Spacewalk 2.7

2018-01-04 Thread Francis Lee Mondia
Hi, I'm still having the same issue per the original thread below. This is a fresh install of Spacewalk on CentOS 7, as was having the same issues with the legacy system that I inherited (upgraded to 2.6, CentOS 6.9) I can telnet the port from the client (5222) and OSA dispatcher service is