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

[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 by the client? You have to login
  to the client and run "rhn_check" to execute the task?

Robert

Am 05.01.2018 um 02:50 schrieb 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 running on both the server and client.
> 
> Any thoughts? Let me know what information you need to help troubleshoot
> this.
> 
> Original Thread:
> https://www.redhat.com/archives/spacewalk-list/2017-February/msg00028.html
> 
> Kind regards,
> Francis
> 
> 
> ___
> Spacewalk-list mailing list
> Spacewalk-list@redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
> 

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

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

[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" to execute the task? - YES

I would have thought it was resolved in 2.7 but it appears not the case and
others are reporting more or less the same.

Any thoughts?

Kind regards,
Francis


On Sun, Jan 7, 2018 at 11:15 AM, Robert Paschedag 
wrote:

> 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 by the client? You have to login
>   to the client and run "rhn_check" to execute the task?
>
> Robert
>
> Am 05.01.2018 um 02:50 schrieb 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 running on both the server and client.
> >
> > Any thoughts? Let me know what information you need to help troubleshoot
> > this.
> >
> > Original Thread:
> > https://www.redhat.com/archives/spacewalk-list/2017-
> February/msg00028.html
> >
> > Kind regards,
> > Francis
> >
> >
> > ___
> > Spacewalk-list mailing list
> > Spacewalk-list@redhat.com
> > https://www.redhat.com/mailman/listinfo/spacewalk-list
> >
>
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

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

[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 jabber and
osa-dispatcher on the server, remove (rm -rf /var/lib/jabber/db/*) the
jabber database (in case of BDB) and restart the osad on the clients.

In case, everything is setup correctly (FQDN, correct SSL cert als for
jabberd), this should just work.

Robert

Am 07.01.2018 um 20:48 schrieb 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" to execute the task? - YES
> 
> I would have thought it was resolved in 2.7 but it appears not the case
> and others are reporting more or less the same. 
> 
> Any thoughts?
> 
> Kind regards,
> Francis
> 
> 
> On Sun, Jan 7, 2018 at 11:15 AM, Robert Paschedag
> mailto:robert.pasche...@web.de>> wrote:
> 
> 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 by the client? You have to login
>   to the client and run "rhn_check" to execute the task?
> 
> Robert
> 
> Am 05.01.2018 um 02:50 schrieb 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 running on both the server and client.
> >
> > Any thoughts? Let me know what information you need to help
> troubleshoot
> > this.
> >
> > Original Thread:
> >
> https://www.redhat.com/archives/spacewalk-list/2017-February/msg00028.html
> 
> 
> >
> > Kind regards,
> > Francis
> >
> >
> > ___
> > Spacewalk-list mailing list
> > Spacewalk-list@redhat.com 
> > https://www.redhat.com/mailman/listinfo/spacewalk-list
> 
> >
> 
> 

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list