At this point clients are not communicating with Spacewalk, only Yum has been
used in the past for package installations and executed from the client end.
So at this point no clients are talking to Spacewalk, only OSA Dispatcher
talking to Jabber.
Regards
Andrew
-Original Message-
Fro
There are other ID's in the logs that are osad related. Looking at the logs
that's the one in the request when the conflict occurs:
[root@sdcvp-spacewalk01 jabberd]# osa-dispatcher -N -vvv
-->
<-- 134.178.145.92
<--
-->
<-- 134.178.145.92EXTERNALPLAINDIGEST-MD5
--> rhn-dispat
Am 11. September 2017 02:55:54 MESZ schrieb Andrew Bergman
:
>There are other ID's in the logs that are osad related. Looking at the
>logs that's the one in the request when the conflict occurs:
>
>[root@sdcvp-spacewalk01 jabberd]# osa-dispatcher -N -vvv
>--> to='sdcvp-spacewalk01.bom
Trust me, that was the first thing I tried ;)
-Original Message-
From: Robert Paschedag [mailto:robert.pasche...@web.de]
Sent: Monday, 11 September 2017 3:33 PM
To: spacewalk-list@redhat.com; Andrew Bergman; spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict"
Hmma hard one.
What errors do you get on the "client" side?
-Ursprüngliche Nachricht-
Von: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Andrew Bergman
Gesendet: Montag, 11. September 2017 07:43
An: spacewalk-list@redhat.com
Betreff:
