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 <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

Reply via email to