Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Andrew Bergman]

RESOLVED

Log messages from jabber during the conflict failure:

Sep 12 03:32:41 spacewalk jabberd/c2s[12995]: [12] [SUBNET1.92, port=36942] 
connect
Sep 12 03:32:41 spacewalk jabberd/c2s[12995]: [12] traditional.digest 
authentication succeeded: rhn-dispatcher-sat@/superclient SUBNET1.92:36942 TLS
Sep 12 03:32:41 spacewalk jabberd/c2s[12995]: [12] requesting session: 
jid=rhn-dispatcher-sat@ spacewalk-fqdn.censored /superclient
Sep 12 03:32:41 spacewalk jabberd/c2s[12995]: [10] [SUBNET2.224, port=53106] 
disconnect jid=rhn-dispatcher-sat@ spacewalk-fqdn.censored /superclient, 
packets: 622, bytes: 26215
Sep 12 03:32:41 spacewalk jabberd/sm[12987]: session replaced: 
jid=rhn-dispatcher-sat@ spacewalk-fqdn.censored /superclient
Sep 12 03:32:53 spacewalk jabberd/c2s[12995]: [10] [SUBNET2.224, port=53124] 
connect
Sep 12 03:32:53 spacewalk jabberd/c2s[12995]: [10] traditional.digest 
authentication succeeded: rhn-dispatcher-sat@/superclient SUBNET2.224:53124 TLS
Sep 12 03:32:53 spacewalk jabberd/c2s[12995]: [10] requesting session: 
jid=rhn-dispatcher-sat@ spacewalk-fqdn.censored /superclient
Sep 12 03:32:53 spacewalk jabberd/c2s[12995]: [12] [SUBNET1.92, port=36942] 
disconnect jid=rhn-dispatcher-sat@ spacewalk-fqdn.censored /superclient, 
packets: 23, bytes: 1503
Sep 12 03:32:53 spacewalk jabberd/sm[12987]: session replaced: 
jid=rhn-dispatcher-sat@spacewalk-fqdn.censored/superclient

I noted something odd, there are two IP addresses talking here to jabber, 
SUBNET1.92 (yes censored) is the spacewalk server, SUBNET2.224 is an IP I have 
never heard of.  An nslookup shows it as another spacewalk server that I had 
not been told about.  Turns out it was the proof of concept.  

I log in and look at the rhn.conf file and somehow, even though it has a 
different hostname to production, it has been configured with all the addresses 
for its spacewalk install as the production hostname.  So two osa-dispatchers 
have been talking to the production spacewalk jabber!!!

Unbelievable.

Shut down the PoC and all is well again.

Cheers

Andrew Bergman

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Andrew Bergman
Sent: Tuesday, 12 September 2017 1:14 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

I just removed the jabber RPM, reinstalled with a clean slate, ran 
spacewalk-setup-jabberd

Jabberd runs fine using the SSL cert I provided built with the FQDN, but again, 
osa-dispatcher fails with same error.

Maybe I should reinstall osa-dispatcher?

Regards

Andrew 

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paschedag, Robert
Sent: Monday, 11 September 2017 5:09 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

Okay...thenwhat error do you get, when you try to setup jabberd from 
scratch (via the setup script) and ".dist" files?



-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 08:39
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

There is no clients using this - I adopted this spacewalk server which had been 
built by someone who did not understand Spacewalk/Satellite.  It was a 
glorified yum repository with a pretty front end.  Most functionality didn't 
work and it wasn't even receiving updates properly.

I fixed all that up and now am at the point of getting OSA Dispatcher and OSAD 
working on clients when I discover that since I upgraded to 2.6 OSA Dispatcher 
has failed to start.

None of the clients have OSAD installed and nor can they hit port 5222 due to 
firewall rules.

The only error we get is when we try to start OSA Dispatcher.

Regards

Andrew

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paschedag, Robert
Sent: Monday, 11 September 2017 4:35 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

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: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

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" error [SEC=UNCLASSIFIED]

[Robert Paschedag]

Am 12. September 2017 05:13:36 MESZ schrieb Andrew Bergman 
<andrew.berg...@bom.gov.au>:
>I just removed the jabber RPM, reinstalled with a clean slate, ran
>spacewalk-setup-jabberd
>
>Jabberd runs fine using the SSL cert I provided built with the FQDN,
>but again, osa-dispatcher fails with same error.
>
>Maybe I should reinstall osa-dispatcher?
>
>Regards
>
>Andrew 
>
>-Original Message-
>From: spacewalk-list-boun...@redhat.com
>[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paschedag,
>Robert
>Sent: Monday, 11 September 2017 5:09 PM
>To: spacewalk-list@redhat.com
>Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error
>[SEC=UNCLASSIFIED]
>
>Okay...thenwhat error do you get, when you try to setup jabberd
>from scratch (via the setup script) and ".dist" files?
>
>
>
>-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 08:39
>An: spacewalk-list@redhat.com
>Betreff: Re: [Spacewalk-list] OSA Dispatcher "conflict" error
>[SEC=UNCLASSIFIED]
>
>There is no clients using this - I adopted this spacewalk server which
>had been built by someone who did not understand Spacewalk/Satellite. 
>It was a glorified yum repository with a pretty front end.  Most
>functionality didn't work and it wasn't even receiving updates
>properly.
>
>I fixed all that up and now am at the point of getting OSA Dispatcher
>and OSAD working on clients when I discover that since I upgraded to
>2.6 OSA Dispatcher has failed to start.
>
>None of the clients have OSAD installed and nor can they hit port 5222
>due to firewall rules.
>
>The only error we get is when we try to start OSA Dispatcher.
>
>Regards
>
>Andrew
>
>-Original Message-
>From: spacewalk-list-boun...@redhat.com
>[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paschedag,
>Robert
>Sent: Monday, 11 September 2017 4:35 PM
>To: spacewalk-list@redhat.com
>Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error
>[SEC=UNCLASSIFIED]
>
>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: Re: [Spacewalk-list] OSA Dispatcher "conflict" error
>[SEC=UNCLASSIFIED]
>
>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" error
>[SEC=UNCLASSIFIED]
>
>Am 11. September 2017 02:55:54 MESZ schrieb Andrew Bergman
><andrew.berg...@bom.gov.au>:
>>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.gov.au' xmlns='jabber:client'
>>xmlns:stream='https://emea01.safelinks.protection.outlook.com/?url=http
>>%3A%2F%2Fetherx.jabber.org%2Fstreams=02%7C01%7CPaschedag.Netlution
>>%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc21
>>6b81f62d%7C0%7C0%7C636407058161574802=bE%2BPcIfY6%2BOZfhh5AYInJpu
>>z5vUHs3JSU5rcJdv5OX0%3D=0' version='1.0'>
>>
>><-- 'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Faffinix.com%2Fjabber%2Faddress=02%7C01%7CPaschedag.Netlution%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636407058161574802=hgOOLVQoxgPD1o%2BQVX%2Bs2UbkpW6PXKRFGgOxdwq8NeI%3D=0'
>>>134.178.145.92>'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>>er.org%2Ffeatures%2Fiq-auth=02%7C01%7CPaschedag.Netlution%40swr.de
>>%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%
>>7C0%7C0%7C636407058161574802=eO6CwoaOmrVZdY2uSR6WgvYPlGtgzDPuoS%2
>>BanJk8stU%3D=0'  />>'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>>er.org%2Ffeatures%2Fiq-register=02%7C01%7CPaschedag.Netlution%40sw
>>r.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f
>>62d%7C0%7C0%7C636407058161574802=4p%2BrR4rREwE02sakNKJFw2PQmUwQyt
>>LD0sdcXlj1Ov0%3D=0'  />>'urn:ietf:params:xml:ns:xmpp-tls' >
>>
>><-- 
>&

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Robert Paschedag]

Am 12. September 2017 05:13:36 MESZ schrieb Andrew Bergman 
<andrew.berg...@bom.gov.au>:
>I just removed the jabber RPM, reinstalled with a clean slate, ran
>spacewalk-setup-jabberd
>
>Jabberd runs fine using the SSL cert I provided built with the FQDN,
>but again, osa-dispatcher fails with same error.
>
>Maybe I should reinstall osa-dispatcher?
>
>Regards
>
>Andrew 
>
>-Original Message-
>From: spacewalk-list-boun...@redhat.com
>[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paschedag,
>Robert
>Sent: Monday, 11 September 2017 5:09 PM
>To: spacewalk-list@redhat.com
>Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error
>[SEC=UNCLASSIFIED]
>
>Okay...thenwhat error do you get, when you try to setup jabberd
>from scratch (via the setup script) and ".dist" files?
>
>
>
>-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 08:39
>An: spacewalk-list@redhat.com
>Betreff: Re: [Spacewalk-list] OSA Dispatcher "conflict" error
>[SEC=UNCLASSIFIED]
>
>There is no clients using this - I adopted this spacewalk server which
>had been built by someone who did not understand Spacewalk/Satellite. 
>It was a glorified yum repository with a pretty front end.  Most
>functionality didn't work and it wasn't even receiving updates
>properly.
>
>I fixed all that up and now am at the point of getting OSA Dispatcher
>and OSAD working on clients when I discover that since I upgraded to
>2.6 OSA Dispatcher has failed to start.
>
>None of the clients have OSAD installed and nor can they hit port 5222
>due to firewall rules.
>
>The only error we get is when we try to start OSA Dispatcher.
>
>Regards
>
>Andrew
>
>-Original Message-
>From: spacewalk-list-boun...@redhat.com
>[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paschedag,
>Robert
>Sent: Monday, 11 September 2017 4:35 PM
>To: spacewalk-list@redhat.com
>Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error
>[SEC=UNCLASSIFIED]
>
>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: Re: [Spacewalk-list] OSA Dispatcher "conflict" error
>[SEC=UNCLASSIFIED]
>
>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" error
>[SEC=UNCLASSIFIED]
>
>Am 11. September 2017 02:55:54 MESZ schrieb Andrew Bergman
><andrew.berg...@bom.gov.au>:
>>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.gov.au' xmlns='jabber:client'
>>xmlns:stream='https://emea01.safelinks.protection.outlook.com/?url=http
>>%3A%2F%2Fetherx.jabber.org%2Fstreams=02%7C01%7CPaschedag.Netlution
>>%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc21
>>6b81f62d%7C0%7C0%7C636407058161574802=bE%2BPcIfY6%2BOZfhh5AYInJpu
>>z5vUHs3JSU5rcJdv5OX0%3D=0' version='1.0'>
>>
>><-- 'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Faffinix.com%2Fjabber%2Faddress=02%7C01%7CPaschedag.Netlution%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636407058161574802=hgOOLVQoxgPD1o%2BQVX%2Bs2UbkpW6PXKRFGgOxdwq8NeI%3D=0'
>>>134.178.145.92>'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>>er.org%2Ffeatures%2Fiq-auth=02%7C01%7CPaschedag.Netlution%40swr.de
>>%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%
>>7C0%7C0%7C636407058161574802=eO6CwoaOmrVZdY2uSR6WgvYPlGtgzDPuoS%2
>>BanJk8stU%3D=0'  />>'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>>er.org%2Ffeatures%2Fiq-register=02%7C01%7CPaschedag.Netlution%40sw
>>r.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f
>>62d%7C0%7C0%7C636407058161574802=4p%2BrR4rREwE02sakNKJFw2PQmUwQyt
>>LD0sdcXlj1Ov0%3D=0'  />>'urn:ietf:params:xml:ns:xmpp-tls' >
>>
>><-- 
>&

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Andrew Bergman]

I just removed the jabber RPM, reinstalled with a clean slate, ran 
spacewalk-setup-jabberd

Jabberd runs fine using the SSL cert I provided built with the FQDN, but again, 
osa-dispatcher fails with same error.

Maybe I should reinstall osa-dispatcher?

Regards

Andrew 

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paschedag, Robert
Sent: Monday, 11 September 2017 5:09 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

Okay...thenwhat error do you get, when you try to setup jabberd from 
scratch (via the setup script) and ".dist" files?



-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 08:39
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

There is no clients using this - I adopted this spacewalk server which had been 
built by someone who did not understand Spacewalk/Satellite.  It was a 
glorified yum repository with a pretty front end.  Most functionality didn't 
work and it wasn't even receiving updates properly.

I fixed all that up and now am at the point of getting OSA Dispatcher and OSAD 
working on clients when I discover that since I upgraded to 2.6 OSA Dispatcher 
has failed to start.

None of the clients have OSAD installed and nor can they hit port 5222 due to 
firewall rules.

The only error we get is when we try to start OSA Dispatcher.

Regards

Andrew

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paschedag, Robert
Sent: Monday, 11 September 2017 4:35 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

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: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

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" error [SEC=UNCLASSIFIED]

Am 11. September 2017 02:55:54 MESZ schrieb Andrew Bergman 
<andrew.berg...@bom.gov.au>:
>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.gov.au' xmlns='jabber:client'
>xmlns:stream='https://emea01.safelinks.protection.outlook.com/?url=http
>%3A%2F%2Fetherx.jabber.org%2Fstreams=02%7C01%7CPaschedag.Netlution
>%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc21
>6b81f62d%7C0%7C0%7C636407058161574802=bE%2BPcIfY6%2BOZfhh5AYInJpu
>z5vUHs3JSU5rcJdv5OX0%3D=0' version='1.0'>
>
><-- 'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Faffinix.com%2Fjabber%2Faddress=02%7C01%7CPaschedag.Netlution%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636407058161574802=hgOOLVQoxgPD1o%2BQVX%2Bs2UbkpW6PXKRFGgOxdwq8NeI%3D=0'
>>134.178.145.92'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>er.org%2Ffeatures%2Fiq-auth=02%7C01%7CPaschedag.Netlution%40swr.de
>%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%
>7C0%7C0%7C636407058161574802=eO6CwoaOmrVZdY2uSR6WgvYPlGtgzDPuoS%2
>BanJk8stU%3D=0'  />'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>er.org%2Ffeatures%2Fiq-register=02%7C01%7CPaschedag.Netlution%40sw
>r.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f
>62d%7C0%7C0%7C636407058161574802=4p%2BrR4rREwE02sakNKJFw2PQmUwQyt
>LD0sdcXlj1Ov0%3D=0'  />'urn:ietf:params:xml:ns:xmpp-tls' >
>
><-- 
>
>--> to='sdcvp-spacewalk01.bom.gov.au' xmlns='jabber:client'
>xmlns:stream='https://emea01.safelinks.protection.outlook.com/?url=http
>%3A%2F%2Fetherx.jabber.org%2Fstreams=02%7C01%7CPaschedag.Netlution
>%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc21
>6b81f62d%7C0%7C0%7C636407058161574802=bE%2BPcIfY6%2BOZfhh5AYInJpu
>z5vUHs3JSU5rcJdv5OX0%3D=0' version='1.0'>
>
><-- 'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Faffinix.com%2Fjabber%2Faddress=02%

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Paschedag, Robert]

Okay...thenwhat error do you get, when you try to setup jabberd from 
scratch (via the setup script) and ".dist" files?



-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 08:39
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

There is no clients using this - I adopted this spacewalk server which had been 
built by someone who did not understand Spacewalk/Satellite.  It was a 
glorified yum repository with a pretty front end.  Most functionality didn't 
work and it wasn't even receiving updates properly.

I fixed all that up and now am at the point of getting OSA Dispatcher and OSAD 
working on clients when I discover that since I upgraded to 2.6 OSA Dispatcher 
has failed to start.

None of the clients have OSAD installed and nor can they hit port 5222 due to 
firewall rules.

The only error we get is when we try to start OSA Dispatcher.

Regards

Andrew

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paschedag, Robert
Sent: Monday, 11 September 2017 4:35 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

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: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

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" error [SEC=UNCLASSIFIED]

Am 11. September 2017 02:55:54 MESZ schrieb Andrew Bergman 
<andrew.berg...@bom.gov.au>:
>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.gov.au' xmlns='jabber:client'
>xmlns:stream='https://emea01.safelinks.protection.outlook.com/?url=http
>%3A%2F%2Fetherx.jabber.org%2Fstreams=02%7C01%7CPaschedag.Netlution
>%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc21
>6b81f62d%7C0%7C0%7C636407058161574802=bE%2BPcIfY6%2BOZfhh5AYInJpu
>z5vUHs3JSU5rcJdv5OX0%3D=0' version='1.0'>
>
><-- 'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Faffinix.com%2Fjabber%2Faddress=02%7C01%7CPaschedag.Netlution%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636407058161574802=hgOOLVQoxgPD1o%2BQVX%2Bs2UbkpW6PXKRFGgOxdwq8NeI%3D=0'
>>134.178.145.92'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>er.org%2Ffeatures%2Fiq-auth=02%7C01%7CPaschedag.Netlution%40swr.de
>%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%
>7C0%7C0%7C636407058161574802=eO6CwoaOmrVZdY2uSR6WgvYPlGtgzDPuoS%2
>BanJk8stU%3D=0'  />'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>er.org%2Ffeatures%2Fiq-register=02%7C01%7CPaschedag.Netlution%40sw
>r.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f
>62d%7C0%7C0%7C636407058161574802=4p%2BrR4rREwE02sakNKJFw2PQmUwQyt
>LD0sdcXlj1Ov0%3D=0'  />'urn:ietf:params:xml:ns:xmpp-tls' >
>
><-- 
>
>--> to='sdcvp-spacewalk01.bom.gov.au' xmlns='jabber:client'
>xmlns:stream='https://emea01.safelinks.protection.outlook.com/?url=http
>%3A%2F%2Fetherx.jabber.org%2Fstreams=02%7C01%7CPaschedag.Netlution
>%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc21
>6b81f62d%7C0%7C0%7C636407058161574802=bE%2BPcIfY6%2BOZfhh5AYInJpu
>z5vUHs3JSU5rcJdv5OX0%3D=0' version='1.0'>
>
><-- 'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Faffinix.com%2Fjabber%2Faddress=02%7C01%7CPaschedag.Netlution%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636407058161574802=hgOOLVQoxgPD1o%2BQVX%2Bs2UbkpW6PXKRFGgOxdwq8NeI%3D=0'
>>134.178.145.92'urn:ietf:params:xml:ns:xmpp-sasl'
>>EXTERNALPLAIN
>>DIGEST-MD5xmlns =
>'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>er.org%2Ffeatures%2Fiq-auth=02%7C01%7CPaschedag.Netlution%40swr.de
>%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%
>7C0%7C0%7C636407058161574802=eO6CwoaOmrVZdY2uSR6WgvYPlGtgzDPuoS%2
>BanJk8st

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Paschedag, Robert]

Or maybe the best way is really to wipe all and reinstall spacewalk from 
scratch. You could first extract the list of "clients" currently registered 
there, setup spacewalk (all should be running then  ), create activation keys 
and force a re-registration on every client.

On every client

rhnreg_ks --force --activationkey= 
--serverUrl=https:///XMLRPC

But this case would be my personal final destination.



-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 08:39
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

There is no clients using this - I adopted this spacewalk server which had been 
built by someone who did not understand Spacewalk/Satellite.  It was a 
glorified yum repository with a pretty front end.  Most functionality didn't 
work and it wasn't even receiving updates properly.

I fixed all that up and now am at the point of getting OSA Dispatcher and OSAD 
working on clients when I discover that since I upgraded to 2.6 OSA Dispatcher 
has failed to start.

None of the clients have OSAD installed and nor can they hit port 5222 due to 
firewall rules.

The only error we get is when we try to start OSA Dispatcher.

Regards

Andrew

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paschedag, Robert
Sent: Monday, 11 September 2017 4:35 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

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: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

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" error [SEC=UNCLASSIFIED]

Am 11. September 2017 02:55:54 MESZ schrieb Andrew Bergman 
<andrew.berg...@bom.gov.au>:
>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.gov.au' xmlns='jabber:client'
>xmlns:stream='https://emea01.safelinks.protection.outlook.com/?url=http
>%3A%2F%2Fetherx.jabber.org%2Fstreams=02%7C01%7CPaschedag.Netlution
>%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc21
>6b81f62d%7C0%7C0%7C636407058161574802=bE%2BPcIfY6%2BOZfhh5AYInJpu
>z5vUHs3JSU5rcJdv5OX0%3D=0' version='1.0'>
>
><-- 'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Faffinix.com%2Fjabber%2Faddress=02%7C01%7CPaschedag.Netlution%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636407058161574802=hgOOLVQoxgPD1o%2BQVX%2Bs2UbkpW6PXKRFGgOxdwq8NeI%3D=0'
>>134.178.145.92'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>er.org%2Ffeatures%2Fiq-auth=02%7C01%7CPaschedag.Netlution%40swr.de
>%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%
>7C0%7C0%7C636407058161574802=eO6CwoaOmrVZdY2uSR6WgvYPlGtgzDPuoS%2
>BanJk8stU%3D=0'  />'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>er.org%2Ffeatures%2Fiq-register=02%7C01%7CPaschedag.Netlution%40sw
>r.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f
>62d%7C0%7C0%7C636407058161574802=4p%2BrR4rREwE02sakNKJFw2PQmUwQyt
>LD0sdcXlj1Ov0%3D=0'  />'urn:ietf:params:xml:ns:xmpp-tls' >
>
><-- 
>
>--> to='sdcvp-spacewalk01.bom.gov.au' xmlns='jabber:client'
>xmlns:stream='https://emea01.safelinks.protection.outlook.com/?url=http
>%3A%2F%2Fetherx.jabber.org%2Fstreams=02%7C01%7CPaschedag.Netlution
>%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc21
>6b81f62d%7C0%7C0%7C636407058161574802=bE%2BPcIfY6%2BOZfhh5AYInJpu
>z5vUHs3JSU5rcJdv5OX0%3D=0' version='1.0'>
>
><-- 'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Faffinix.com%2Fjabber%2Faddress=02%7C01%7CPaschedag.Netlution%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636407058161574802=hgOOLVQoxgPD1o%2BQVX%2Bs2UbkpW6PXKRFGgOxdwq8NeI%3D=0'
>>134.178.145.92'urn:ietf:params:xml:ns:xmpp-sasl'
>>EXTERNALPLAIN
>>DIGEST-MD5xmlns =
>'http

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Andrew Bergman]

There is no clients using this - I adopted this spacewalk server which had been 
built by someone who did not understand Spacewalk/Satellite.  It was a 
glorified yum repository with a pretty front end.  Most functionality didn't 
work and it wasn't even receiving updates properly.

I fixed all that up and now am at the point of getting OSA Dispatcher and OSAD 
working on clients when I discover that since I upgraded to 2.6 OSA Dispatcher 
has failed to start.

None of the clients have OSAD installed and nor can they hit port 5222 due to 
firewall rules.

The only error we get is when we try to start OSA Dispatcher.

Regards

Andrew

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paschedag, Robert
Sent: Monday, 11 September 2017 4:35 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

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: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

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" error [SEC=UNCLASSIFIED]

Am 11. September 2017 02:55:54 MESZ schrieb Andrew Bergman 
<andrew.berg...@bom.gov.au>:
>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.gov.au' xmlns='jabber:client'
>xmlns:stream='https://emea01.safelinks.protection.outlook.com/?url=http
>%3A%2F%2Fetherx.jabber.org%2Fstreams=02%7C01%7CPaschedag.Netlution
>%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc21
>6b81f62d%7C0%7C0%7C636407058161574802=bE%2BPcIfY6%2BOZfhh5AYInJpu
>z5vUHs3JSU5rcJdv5OX0%3D=0' version='1.0'>
>
><-- 'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Faffinix.com%2Fjabber%2Faddress=02%7C01%7CPaschedag.Netlution%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636407058161574802=hgOOLVQoxgPD1o%2BQVX%2Bs2UbkpW6PXKRFGgOxdwq8NeI%3D=0'
>>134.178.145.92'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>er.org%2Ffeatures%2Fiq-auth=02%7C01%7CPaschedag.Netlution%40swr.de
>%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%
>7C0%7C0%7C636407058161574802=eO6CwoaOmrVZdY2uSR6WgvYPlGtgzDPuoS%2
>BanJk8stU%3D=0'  />'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>er.org%2Ffeatures%2Fiq-register=02%7C01%7CPaschedag.Netlution%40sw
>r.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f
>62d%7C0%7C0%7C636407058161574802=4p%2BrR4rREwE02sakNKJFw2PQmUwQyt
>LD0sdcXlj1Ov0%3D=0'  />'urn:ietf:params:xml:ns:xmpp-tls' >
>
><-- 
>
>--> to='sdcvp-spacewalk01.bom.gov.au' xmlns='jabber:client'
>xmlns:stream='https://emea01.safelinks.protection.outlook.com/?url=http
>%3A%2F%2Fetherx.jabber.org%2Fstreams=02%7C01%7CPaschedag.Netlution
>%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc21
>6b81f62d%7C0%7C0%7C636407058161574802=bE%2BPcIfY6%2BOZfhh5AYInJpu
>z5vUHs3JSU5rcJdv5OX0%3D=0' version='1.0'>
>
><-- 'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Faffinix.com%2Fjabber%2Faddress=02%7C01%7CPaschedag.Netlution%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636407058161574802=hgOOLVQoxgPD1o%2BQVX%2Bs2UbkpW6PXKRFGgOxdwq8NeI%3D=0'
>>134.178.145.92'urn:ietf:params:xml:ns:xmpp-sasl'
>>EXTERNALPLAIN
>>DIGEST-MD5xmlns =
>'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>er.org%2Ffeatures%2Fiq-auth=02%7C01%7CPaschedag.Netlution%40swr.de
>%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%
>7C0%7C0%7C636407058161574802=eO6CwoaOmrVZdY2uSR6WgvYPlGtgzDPuoS%2
>BanJk8stU%3D=0'  />'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>er.org%2Ffeatures%2Fiq-register=02%7C01%7CPaschedag.Netlution%40sw
>r.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f
>62d%7C0%7C0%7C636407058161574802=4p%2BrR4rREwE02sakNKJFw2PQmUwQyt
>LD0sdcXlj1Ov0%3D=0'  />
>
>--> 'jabber:iq:auth' >rhn-dispatcher-sat
>
><-- 'jabber:iq:auth' >rhn-dispatcher-sat/>

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Paschedag, Robert]

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: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

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" error [SEC=UNCLASSIFIED]

Am 11. September 2017 02:55:54 MESZ schrieb Andrew Bergman 
<andrew.berg...@bom.gov.au>:
>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.gov.au' xmlns='jabber:client'
>xmlns:stream='https://emea01.safelinks.protection.outlook.com/?url=http
>%3A%2F%2Fetherx.jabber.org%2Fstreams=02%7C01%7CPaschedag.Netlution
>%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc21
>6b81f62d%7C0%7C0%7C636407058161574802=bE%2BPcIfY6%2BOZfhh5AYInJpu
>z5vUHs3JSU5rcJdv5OX0%3D=0' version='1.0'>
>
><-- 'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Faffinix.com%2Fjabber%2Faddress=02%7C01%7CPaschedag.Netlution%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636407058161574802=hgOOLVQoxgPD1o%2BQVX%2Bs2UbkpW6PXKRFGgOxdwq8NeI%3D=0'
>>134.178.145.92'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>er.org%2Ffeatures%2Fiq-auth=02%7C01%7CPaschedag.Netlution%40swr.de
>%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%
>7C0%7C0%7C636407058161574802=eO6CwoaOmrVZdY2uSR6WgvYPlGtgzDPuoS%2
>BanJk8stU%3D=0'  />'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>er.org%2Ffeatures%2Fiq-register=02%7C01%7CPaschedag.Netlution%40sw
>r.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f
>62d%7C0%7C0%7C636407058161574802=4p%2BrR4rREwE02sakNKJFw2PQmUwQyt
>LD0sdcXlj1Ov0%3D=0'  />'urn:ietf:params:xml:ns:xmpp-tls' >
>
><-- 
>
>--> to='sdcvp-spacewalk01.bom.gov.au' xmlns='jabber:client'
>xmlns:stream='https://emea01.safelinks.protection.outlook.com/?url=http
>%3A%2F%2Fetherx.jabber.org%2Fstreams=02%7C01%7CPaschedag.Netlution
>%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc21
>6b81f62d%7C0%7C0%7C636407058161574802=bE%2BPcIfY6%2BOZfhh5AYInJpu
>z5vUHs3JSU5rcJdv5OX0%3D=0' version='1.0'>
>
><-- 'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Faffinix.com%2Fjabber%2Faddress=02%7C01%7CPaschedag.Netlution%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636407058161574802=hgOOLVQoxgPD1o%2BQVX%2Bs2UbkpW6PXKRFGgOxdwq8NeI%3D=0'
>>134.178.145.92'urn:ietf:params:xml:ns:xmpp-sasl'
>>EXTERNALPLAIN
>>DIGEST-MD5xmlns = 
>'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>er.org%2Ffeatures%2Fiq-auth=02%7C01%7CPaschedag.Netlution%40swr.de
>%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%
>7C0%7C0%7C636407058161574802=eO6CwoaOmrVZdY2uSR6WgvYPlGtgzDPuoS%2
>BanJk8stU%3D=0'  />'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb
>er.org%2Ffeatures%2Fiq-register=02%7C01%7CPaschedag.Netlution%40sw
>r.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f
>62d%7C0%7C0%7C636407058161574802=4p%2BrR4rREwE02sakNKJFw2PQmUwQyt
>LD0sdcXlj1Ov0%3D=0'  />
>
>--> 'jabber:iq:auth' >rhn-dispatcher-sat
>
><-- 'jabber:iq:auth' >rhn-dispatcher-sat/>
>
>--> 'jabber:iq:auth'
>>rhn-dispatcher-satsuperclient>>e004d72e248acb5f9ffd8db5be2655993c7ed389>>
>
><-- 
>
>--> 'jabber:iq:roster'  />
>
><-- 'jabber:iq:roster' >jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/>subscription='both' />
>
>--> 
>
>--> 'jabber:iq:roster'  />
>
><-- to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>from='osad-441293a...@sdcvp-spacewalk01.bom.gov.au/osad'>'urn:xmpp:delay'  stamp='2017-09-08T06:06:05Z'
>from='osad-441293a...@sdcvp-spacewalk01.bom.gov.au/osad' />
>
><-- 'jabber:iq:roster' >jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/>subscription='both' />
>
><-- to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>from='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au/osad'&g

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Andrew Bergman]

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" error [SEC=UNCLASSIFIED]

Am 11. September 2017 02:55:54 MESZ schrieb Andrew Bergman 
<andrew.berg...@bom.gov.au>:
>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.gov.au' xmlns='jabber:client'
>xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
>
><-- >134.178.145.92'http://jabber.org/features/iq-auth'  />'http://jabber.org/features/iq-register'  />'urn:ietf:params:xml:ns:xmpp-tls' >
>
><-- 
>
>--> to='sdcvp-spacewalk01.bom.gov.au' xmlns='jabber:client'
>xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
>
><-- >134.178.145.92'urn:ietf:params:xml:ns:xmpp-sasl'
>>EXTERNALPLAIN
>>DIGEST-MD5xmlns = 'http://jabber.org/features/iq-auth'  />'http://jabber.org/features/iq-register'  />
>
>--> 'jabber:iq:auth' >rhn-dispatcher-sat
>
><-- 'jabber:iq:auth' >rhn-dispatcher-sat/>
>
>--> 'jabber:iq:auth'
>>rhn-dispatcher-satsuperclient>>e004d72e248acb5f9ffd8db5be2655993c7ed389>>
>
><-- 
>
>--> 'jabber:iq:roster'  />
>
><-- 'jabber:iq:roster' >jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/>subscription='both' />
>
>--> 
>
>--> 'jabber:iq:roster'  />
>
><-- to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>from='osad-441293a...@sdcvp-spacewalk01.bom.gov.au/osad'>'urn:xmpp:delay'  stamp='2017-09-08T06:06:05Z'
>from='osad-441293a...@sdcvp-spacewalk01.bom.gov.au/osad' />
>
><-- 'jabber:iq:roster' >jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/>subscription='both' />
>
><-- to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>from='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au/osad'>'urn:xmpp:delay'  stamp='2017-09-08T06:06:53Z'
>from='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au/osad' />
>
>--> 'jabber:iq:roster'  />
>
><-- 'jabber:iq:roster' >jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/>subscription='both' />
>
>--> 'jabber:iq:roster'  />
>
><-- 'jabber:iq:roster' >jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/>subscription='both' />
>
>--> 'jabber:iq:roster'  />
>
><-- />
>
>Spacewalk 17712 2017/09/11 00:52:44 -00:00: ('Received an error stanza:
>', />)
>Spacewalk 17712 2017/09/11 00:52:44 -00:00: ('Received an conflict.
>Restarting with new credentials.',)
>Spacewalk 17712 2017/09/11 00:52:44 -00:00: ('Error caught:',)
>
>ERROR: unhandled exception occurred: (can't write str to text stream).
>
>Regards
>
>Andrew
>
>
>-Original Message-
>From: spacewalk-list-boun...@redhat.com 
>[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paschedag, 
>Robert
>Sent: Friday, 8 September 2017 5:44 PM
>To: spacewalk-list@redhat.com
>Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error 
>[SEC=UNCLASSIFIED]
>
>Hi Andrew,
>
>it is this "id" that looks odd (to me)
>
>>>to='rhn-dispatcher-sat@FQDN-censored-address/superclient'
>>>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'>>=
>
>And later set to another id
>
>>>to='rhn-dispatcher-sat@FQDN-censored-address/superclient'
>>>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'>>=
>
>All of "my" spacewalk clients are registered with a name starting with 
>"osad-<10hexdigits>@"
>
>I never saw such a weired id.
>
>That's why I asked, if there are multiple IDs used within jabber.
>
>Also we never spoke about your spacewalk clients. Do they connect 
>"correctly" to your server? Do they experience any errors? Can you 
>execute remote scripts (triggered immediately via osad)?
>
>Robert
>
>
>-Ursprüngliche Nachricht-
>Von: spacewalk-list-boun...@redhat.com
>[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Andrew 
>Bergman
>Gesendet: Freitag, 8. September 2017 08:08
>An: spacewalk-list@redhat.com
>Betreff: Re: [Spacewalk-list] OSA Dispatcher "conflict" error 
>[SEC=UNCLASSIFIED]
>
>No issues it seems:
>
>
>Sep  8 06:04:55 censored-address jabbe

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

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

<-- 134.178.145.92

<-- 

--> 

<-- 134.178.145.92EXTERNALPLAINDIGEST-MD5

--> rhn-dispatcher-sat

<-- rhn-dispatcher-sat

--> rhn-dispatcher-satsupercliente004d72e248acb5f9ffd8db5be2655993c7ed389

<-- 

--> 

<-- 

--> 

--> 

<-- 

<-- 

<-- 

--> 

<-- 

--> 

<-- 

--> 

<-- 

Spacewalk 17712 2017/09/11 00:52:44 -00:00: ('Received an error stanza: ', 
)
Spacewalk 17712 2017/09/11 00:52:44 -00:00: ('Received an conflict. Restarting 
with new credentials.',)
Spacewalk 17712 2017/09/11 00:52:44 -00:00: ('Error caught:',)

ERROR: unhandled exception occurred: (can't write str to text stream).

Regards

Andrew


-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paschedag, Robert
Sent: Friday, 8 September 2017 5:44 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

Hi Andrew,

it is this "id" that looks odd (to me)

>>to='rhn-dispatcher-sat@FQDN-censored-address/superclient'
>>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'>=

And later set to another id

>>to='rhn-dispatcher-sat@FQDN-censored-address/superclient'
>>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'>=

All of "my" spacewalk clients are registered with a name starting with 
"osad-<10hexdigits>@"

I never saw such a weired id.

That's why I asked, if there are multiple IDs used within jabber.

Also we never spoke about your spacewalk clients. Do they connect "correctly" 
to your server? Do they experience any errors? Can you execute remote scripts 
(triggered immediately via osad)?

Robert


-Ursprüngliche Nachricht-
Von: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Andrew Bergman
Gesendet: Freitag, 8. September 2017 08:08
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

No issues it seems:


Sep  8 06:04:55 censored-address jabberd/sm[21702]: starting up Sep  8 06:04:55 
censored-address jabberd/sm[21702]: process id is 21702, written to 
/var/lib/jabberd/pid/sm.pid Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
loading 'db' storage module Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
initialised storage driver 'db'
Sep  8 06:04:55 censored-address jabberd/sm[21702]: modules search path: 
/usr/lib64/jabberd Sep  8 06:04:55 censored-address jabberd/sm[21702]: module 
'status' added to chain 'sess-start' (order 0 index 0 seq 0) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'status' added to chain 'sess-end' 
(order 0 index 0 seq 1) Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
module 'iq-last' added to chain 'sess-end' (order 1 index 1 seq 0) Sep  8 
06:04:55 censored-address jabberd/sm[21702]: module 'validate' added to chain 
'in-sess' (order 0 index 2 seq 0) Sep  8 06:04:55 censored-address 
jabberd/sm[21702]: module 'status' added to chain 'in-sess' (order 1 index 0 
seq 2) Sep  8 06:04:55 censored-address jabberd/sm[21702]: module 'privacy' 
added to chain 'in-sess' (order 2 index 3 seq 0) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'roster' added to chain 'in-sess' 
(order 3 index 4 seq 0) Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
module 'vacation' added to chain 'in-sess' (order 4 index 5 seq 0) Sep  8 
06:04:55 censored-address jabberd/sm[21702]: module 'iq-vcard' added to chain 
'in-sess' (order 5 index 6 seq 0) Sep  8 06:04:55 censored-address 
jabberd/sm[21702]: module 'iq-ping' added to chain 'in-sess' (order 6 index 7 
seq 0) Sep  8 06:04:55 censored-address jabberd/sm[21702]: module 'iq-private' 
added to chain 'in-sess' (order 7 index 8 seq 0) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'disco' added to chain 'in-sess' 
(order 8 index 9 seq 0) Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
module 'amp' added to chain 'in-sess' (order 9 index 10 seq 0) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'offline' added to chain 'in-sess' 
(order 10 index 11 seq 0) Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
module 'announce' added to chain 'in-sess' (order 11 index 12 seq 0) Sep  8 
06:04:55 censored-address jabberd/sm[21702]: module 'presence' added to chain 
'in-sess' (order 12 index 13 seq 0) Sep  8 06:04:55 censored-address 
jabberd/sm[21702]: module 'deliver' added to chain 'in-sess' (order 13 index 14 
seq 0) Sep  8 06:04:55 censored-address jabberd/sm[21702]: module 'session' 
added to chain 'in-router' (order 0 index 15 seq 0) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'vali

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Andrew Bergman]

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-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Paschedag, Robert
Sent: Friday, 8 September 2017 5:44 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

Hi Andrew,

it is this "id" that looks odd (to me)

>>to='rhn-dispatcher-sat@FQDN-censored-address/superclient'
>>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'>=

And later set to another id

>>to='rhn-dispatcher-sat@FQDN-censored-address/superclient'
>>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'>=

All of "my" spacewalk clients are registered with a name starting with 
"osad-<10hexdigits>@"

I never saw such a weired id.

That's why I asked, if there are multiple IDs used within jabber.

Also we never spoke about your spacewalk clients. Do they connect "correctly" 
to your server? Do they experience any errors? Can you execute remote scripts 
(triggered immediately via osad)?

Robert


-Ursprüngliche Nachricht-
Von: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Andrew Bergman
Gesendet: Freitag, 8. September 2017 08:08
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

No issues it seems:


Sep  8 06:04:55 censored-address jabberd/sm[21702]: starting up Sep  8 06:04:55 
censored-address jabberd/sm[21702]: process id is 21702, written to 
/var/lib/jabberd/pid/sm.pid Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
loading 'db' storage module Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
initialised storage driver 'db'
Sep  8 06:04:55 censored-address jabberd/sm[21702]: modules search path: 
/usr/lib64/jabberd Sep  8 06:04:55 censored-address jabberd/sm[21702]: module 
'status' added to chain 'sess-start' (order 0 index 0 seq 0) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'status' added to chain 'sess-end' 
(order 0 index 0 seq 1) Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
module 'iq-last' added to chain 'sess-end' (order 1 index 1 seq 0) Sep  8 
06:04:55 censored-address jabberd/sm[21702]: module 'validate' added to chain 
'in-sess' (order 0 index 2 seq 0) Sep  8 06:04:55 censored-address 
jabberd/sm[21702]: module 'status' added to chain 'in-sess' (order 1 index 0 
seq 2) Sep  8 06:04:55 censored-address jabberd/sm[21702]: module 'privacy' 
added to chain 'in-sess' (order 2 index 3 seq 0) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'roster' added to chain 'in-sess' 
(order 3 index 4 seq 0) Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
module 'vacation' added to chain 'in-sess' (order 4 index 5 seq 0) Sep  8 
06:04:55 censored-address jabberd/sm[21702]: module 'iq-vcard' added to chain 
'in-sess' (order 5 index 6 seq 0) Sep  8 06:04:55 censored-address 
jabberd/sm[21702]: module 'iq-ping' added to chain 'in-sess' (order 6 index 7 
seq 0) Sep  8 06:04:55 censored-address jabberd/sm[21702]: module 'iq-private' 
added to chain 'in-sess' (order 7 index 8 seq 0) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'disco' added to chain 'in-sess' 
(order 8 index 9 seq 0) Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
module 'amp' added to chain 'in-sess' (order 9 index 10 seq 0) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'offline' added to chain 'in-sess' 
(order 10 index 11 seq 0) Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
module 'announce' added to chain 'in-sess' (order 11 index 12 seq 0) Sep  8 
06:04:55 censored-address jabberd/sm[21702]: module 'presence' added to chain 
'in-sess' (order 12 index 13 seq 0) Sep  8 06:04:55 censored-address 
jabberd/sm[21702]: module 'deliver' added to chain 'in-sess' (order 13 index 14 
seq 0) Sep  8 06:04:55 censored-address jabberd/sm[21702]: module 'session' 
added to chain 'in-router' (order 0 index 15 seq 0) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'validate' added to chain 
'in-router' (order 1 index 2 seq 1) Sep  8 06:04:55 censored-address 
jabberd/sm[21702]: module 'presence' added to chain 'in-router' (order 2 index 
13 seq 1) Sep  8 06:04:55 censored-address jabberd/sm[21702]: module 'privacy' 
added to chain 'in-router' (order 3 index 3 seq 1) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'privacy' added to chain 
'out-router' (order 0 index 3 seq 2) Sep  8 06:04:55 censored-address 
jabberd/sm[21702]: module 'iq-last' added to chain 'pkt-sm' (order 0 index 1 
seq 1) Sep  8 06:04:55 censored-address jabberd/sm[21702]: module 'iq-ping' 
added to ch

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Paschedag, Robert]

Hi Andrew,

it is this "id" that looks odd (to me)

>>to='rhn-dispatcher-sat@FQDN-censored-address/superclient'
>>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'>=

And later set to another id

>>to='rhn-dispatcher-sat@FQDN-censored-address/superclient'
>>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'>=

All of "my" spacewalk clients are registered with a name starting with 
"osad-<10hexdigits>@"

I never saw such a weired id.

That's why I asked, if there are multiple IDs used within jabber.

Also we never spoke about your spacewalk clients. Do they connect "correctly" 
to your server? Do they experience any errors? Can you execute remote scripts 
(triggered immediately via osad)?

Robert


-Ursprüngliche Nachricht-
Von: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] Im Auftrag von Andrew Bergman
Gesendet: Freitag, 8. September 2017 08:08
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

No issues it seems:


Sep  8 06:04:55 censored-address jabberd/sm[21702]: starting up Sep  8 06:04:55 
censored-address jabberd/sm[21702]: process id is 21702, written to 
/var/lib/jabberd/pid/sm.pid Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
loading 'db' storage module Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
initialised storage driver 'db'
Sep  8 06:04:55 censored-address jabberd/sm[21702]: modules search path: 
/usr/lib64/jabberd Sep  8 06:04:55 censored-address jabberd/sm[21702]: module 
'status' added to chain 'sess-start' (order 0 index 0 seq 0) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'status' added to chain 'sess-end' 
(order 0 index 0 seq 1) Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
module 'iq-last' added to chain 'sess-end' (order 1 index 1 seq 0) Sep  8 
06:04:55 censored-address jabberd/sm[21702]: module 'validate' added to chain 
'in-sess' (order 0 index 2 seq 0) Sep  8 06:04:55 censored-address 
jabberd/sm[21702]: module 'status' added to chain 'in-sess' (order 1 index 0 
seq 2) Sep  8 06:04:55 censored-address jabberd/sm[21702]: module 'privacy' 
added to chain 'in-sess' (order 2 index 3 seq 0) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'roster' added to chain 'in-sess' 
(order 3 index 4 seq 0) Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
module 'vacation' added to chain 'in-sess' (order 4 index 5 seq 0) Sep  8 
06:04:55 censored-address jabberd/sm[21702]: module 'iq-vcard' added to chain 
'in-sess' (order 5 index 6 seq 0) Sep  8 06:04:55 censored-address 
jabberd/sm[21702]: module 'iq-ping' added to chain 'in-sess' (order 6 index 7 
seq 0) Sep  8 06:04:55 censored-address jabberd/sm[21702]: module 'iq-private' 
added to chain 'in-sess' (order 7 index 8 seq 0) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'disco' added to chain 'in-sess' 
(order 8 index 9 seq 0) Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
module 'amp' added to chain 'in-sess' (order 9 index 10 seq 0) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'offline' added to chain 'in-sess' 
(order 10 index 11 seq 0) Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
module 'announce' added to chain 'in-sess' (order 11 index 12 seq 0) Sep  8 
06:04:55 censored-address jabberd/sm[21702]: module 'presence' added to chain 
'in-sess' (order 12 index 13 seq 0) Sep  8 06:04:55 censored-address 
jabberd/sm[21702]: module 'deliver' added to chain 'in-sess' (order 13 index 14 
seq 0) Sep  8 06:04:55 censored-address jabberd/sm[21702]: module 'session' 
added to chain 'in-router' (order 0 index 15 seq 0) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'validate' added to chain 
'in-router' (order 1 index 2 seq 1) Sep  8 06:04:55 censored-address 
jabberd/sm[21702]: module 'presence' added to chain 'in-router' (order 2 index 
13 seq 1) Sep  8 06:04:55 censored-address jabberd/sm[21702]: module 'privacy' 
added to chain 'in-router' (order 3 index 3 seq 1) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'privacy' added to chain 
'out-router' (order 0 index 3 seq 2) Sep  8 06:04:55 censored-address 
jabberd/sm[21702]: module 'iq-last' added to chain 'pkt-sm' (order 0 index 1 
seq 1) Sep  8 06:04:55 censored-address jabberd/sm[21702]: module 'iq-ping' 
added to chain 'pkt-sm' (order 1 index 7 seq 1) Sep  8 06:04:55 
censored-address jabberd/sm[21702]: module 'iq-time' added to chain 'pkt-sm' 
(order 2 index 16 seq 0) Sep  8 06:04:55 censored-address jabberd/sm[21702]: 
module 'iq-version' added to chain 'pkt-sm' (order 3 index 17 seq 0) Sep  8 
06:04:55 censored-address jabberd/sm[21702]: module 'amp' added to chain 
'pkt-sm' (order 4 index 10 seq 1) Sep  8 06:04:55 censored-address 
jabberd/sm[21702]: module 'disco' added to chain 'pkt-sm' (order 5 index 9 seq 
1) Sep  8 06:04:55 censored-address jabberd/sm[21702]: module

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Andrew Bergman]

:04:55 censored-address jabberd/s2s[21718]: process id is 21718, 
written to /var/lib/jabberd/pid/s2s.pid
Sep  8 06:04:55 censored-address jabberd/s2s[21718]: attempting connection to 
router at 127.0.0.1, port=5347
Sep  8 06:04:55 censored-address jabberd/router[21694]: [127.0.0.1, port=33978] 
connect
Sep  8 06:04:55 censored-address jabberd/router[21694]: [127.0.0.1, port=33978] 
authenticated as jabberd@jabberd-router
Sep  8 06:04:55 censored-address jabberd/s2s[21718]: connection to router 
established
Sep  8 06:04:55 censored-address jabberd/router[21694]: [s2s] set as default 
route
Sep  8 06:04:55 censored-address jabberd/router[21694]: [s2s] online (bound to 
127.0.0.1, port 33978)
Sep  8 06:04:55 censored-address jabberd/c2s[21710]: [0.0.0.0, port=5222] 
listening for connections
Sep  8 06:04:55 censored-address jabberd/c2s[21710]: ready for connections
Sep  8 06:04:55 censored-address jabberd/s2s[21718]: [0.0.0.0, port=5269] 
listening for connections
Sep  8 06:04:55 censored-address jabberd/s2s[21718]: ready for connections
Sep  8 06:05:05 censored-address jabberd/c2s[21710]: [7] [134.178.147.224, 
port=46853] connect
Sep  8 06:05:06 censored-address jabberd/c2s[21710]: [7] traditional.digest 
authentication succeeded: rhn-dispatcher-sat@/superclient 134.178.147.224:46853 
TLS
Sep  8 06:05:06 censored-address jabberd/c2s[21710]: [7] requesting session: 
jid=rhn-dispatcher-sat@FQDN-censored-address/superclient
Sep  8 06:05:06 censored-address jabberd/sm[21702]: session started: 
jid=rhn-dispatcher-sat@ FQDN-censored-address /superclient

Jabber looks perfectly healthy.

Regards

Andrew

-Original Message-
From: Robert Paschedag [mailto:robert.pasche...@web.de] 
Sent: Friday, 8 September 2017 4:03 PM
To: spacewalk-list@redhat.com; Andrew Bergman; spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

Am 8. September 2017 07:56:07 MESZ schrieb Andrew Bergman 
<andrew.berg...@bom.gov.au>:
>How can I rebuild the jabber config cleanly?  I tried moving the xml 
>files, restoring them from the .xml.dist files and then re-running
>spacewalk-setup-jabberd but then jabber fails to start.   I ended up
>restoring the original jabber config.
>
>Config snippets with  sections below - note I censored the hostname 
>for security purposes.
>
>c2s.xml
>  c2s
>pemfile="/etc/pki/spacewalk/jabberd/server.pem" realm=""
>register-enable="true">FQDN-censored-hostname
> -->
>
>router.xml
>  router
>
>s2s.xml
>  s2s
>
>sm.xml
>
>  FQDN-censored-hostname
>
>FQDN-censored-hostname
>
>
>vhost1.localdomain (also commented out)
>vhost2.localdomain (also commented out)
>
>Regards
>
>Andrew Bergman
>
>-Original Message-
>From: Robert Paschedag [mailto:robert.pasche...@web.de]
>Sent: Friday, 8 September 2017 2:35 PM
>To: spacewalk-list@redhat.com; Andrew Bergman; 
>spacewalk-list@redhat.com
>Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error 
>[SEC=UNCLASSIFIED]
>
>Am 8. September 2017 03:29:15 MESZ schrieb Andrew Bergman
><andrew.berg...@bom.gov.au>:
>>Hi Spacewalk list,
>>
>>I am seeing an error on the Spacewalk 2.6 server I am responsible for:
>>
>>Jabber is running, port 5222 TCP is running from c2s process and is
>>communicable via telnet.   I see no errors in the logs except from
>>osa-dispatcher.
>>
>># osa-dispatcher -N -
>>
>>The last messages are:
>>--> >type='subscribed' id='presence-fb3eba-37' />
>>
>><-- >'jabber:iq:roster' >>jid='osad-bb7d64e5e1@FQDN-censored-address' subscription='to'
>>/>>subscription='to' />
>>
>><-- >to='rhn-dispatcher-sat@FQDN-censored-address/superclient'
>>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'>=
>>'jabber:iq:roster' >>jid='osad-441293a7e7@FQDN-censored-address' subscription='both'
>>/>
>>
>>--> >'jabber:iq:roster'  />
>>
>><-- >to='rhn-dispatcher-sat@FQDN-censored-address/superclient'
>>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'>=
>>'jabber:iq:roster' >>jid='osad-bb7d64e5e1@FQDN-censored-address' subscription='both'
>>/>
>>
>><-- >/>
>>
>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an error
>stanza:
>>', >/>)
>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an conflict.
>>Restarting with new credentials.',)
>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Error caught:',)
>>
>>ERROR: unhandled exception occurred: (can't write str to text stream).
>>
>>This looks similar to: 
>>http://spacewalk-list.r

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Andrew Bergman]

://localhost/ ldaps://ldap.example.com/

  
  

  
  

  
  uid
  posixAccount
  userPassword
  

  
  

  
  o=Example Corp.

  
  

  
  

  
  60

  




ou=jabbergroups, o=Example Corp.









  

  

  
  


  admin@localhost.localdomain










  

  
  

/usr/lib64/jabberd



  status   




  status   
  iq-last  




  validate 
  status   
  privacy  
  roster   
  vacation 
  
  iq-vcard 
  iq-ping  
  iq-private   
  disco
  amp  
  offline  
  announce 
  presence 
  deliver  




  




  session  
  validate 
  presence 
  privacy  




  privacy  




  iq-last  
  iq-ping  
  iq-time  
  iq-version   
  amp  
  disco
  announce 
  help 
  echo 
  status   
  presence 




  roster   
  presence 
  iq-vcard 
  amp  
  deliver  
  vacation 
  offline  
  iq-last  




  session  
  disco




  active   
  roster   
  roster-publish   
  privacy  
  vacation 




  active   
  template-roster  




  active   
  announce 
  offline  
  privacy  
  roster   
  vacation 
  status   
  iq-last  
  iq-private   
  iq-vcard 




  iq-version   
  help 


  

  
  



  server   
  im   
  Jabber IM server 








  
  

  
  






  

  
  








  
  





60








  

  
  
  

  

  
  








  

  
  











  

  
  


  

  
  


  



-Original Message-
From: Robert Paschedag [mailto:robert.pasche...@web.de] 
Sent: Friday, 8 September 2017 3:37 PM
To: spacewalk-list@redhat.com; Andrew Bergman; spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

Am 8. September 2017 07:16:13 MESZ schrieb Andrew Bergman 
<andrew.berg...@bom.gov.au>:
>Yes, I did an upgrade from 2.2 to 2.6
>
>No ID's that I can see in any of those jabber configs in /etc/jabber
>
>-Original Message-
>From: Robert Paschedag [mailto:robert.pasche...@web.de]
>Sent: Friday, 8 September 2017 3:11 PM
>To: spacewalk-list@redhat.com; Andrew Bergman; 
>spacewalk-list@redhat.com
>Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error 
>[SEC=UNCLASSIFIED]
>
>Am 8. September 2017 06:36:13 MESZ schrieb Andrew Bergman
><andrew.berg...@bom.gov.au>:
>>Where would I find these configured?
>>
>>-Original Message-
>>From: Robert Paschedag [mailto:robert.pasche...@web.de]
>>Sent: Friday, 8 September 2017 2:35 PM
>>To: spacewalk-list@redhat.com; Andrew Bergman; 
>>spacewalk-list@redhat.com
>>Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error 
>>[SEC=UNCLASSIFIED]
>>
>>Am 8. September 2017 03:29:15 MESZ schrieb Andrew Bergman
>><andrew.berg...@bom.gov.au>:
>>>Hi Spacewalk list,
>>>
>>>I am seeing an error on the Spacewalk 2.6 server I am responsible
>for:
>>>
>>>Jabber is running, port 5222 TCP is running from c2s process and is
>>>communicable via telnet.   I see no errors in the logs except from
>>>osa-dispatcher.
>>>
>>># osa-dispatcher -N -
>>>
>>>The last messages are:
>>>--> >>type='subscribed' id='presence-fb3eba-37' />
>>>
>>><-- >>'jabber:iq:roster' >>>jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='to'
>>>/>>>subscription='to' />
>>>
>>><-- >>to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>>

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Andrew Bergman]

I followed the upgrade guide, it said to run spacewalk-setup --upgrade.

As part of that it ran a spacewalk-setup-jabberd

I found id's in the jabber xml files, but they are all correct.  Only in one 
file was the hostname listed twice in sm.xml.  The first was the sm id, the 
second was the  section along with localhost.localdomain.

I have tried removing the latter by commenting but no difference.

Regards

Andrew 

-Original Message-
From: Robert Paschedag [mailto:robert.pasche...@web.de] 
Sent: Friday, 8 September 2017 3:37 PM
To: spacewalk-list@redhat.com; Andrew Bergman; spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

Am 8. September 2017 07:16:13 MESZ schrieb Andrew Bergman 
<andrew.berg...@bom.gov.au>:
>Yes, I did an upgrade from 2.2 to 2.6
>
>No ID's that I can see in any of those jabber configs in /etc/jabber
>
>-Original Message-
>From: Robert Paschedag [mailto:robert.pasche...@web.de]
>Sent: Friday, 8 September 2017 3:11 PM
>To: spacewalk-list@redhat.com; Andrew Bergman; 
>spacewalk-list@redhat.com
>Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error 
>[SEC=UNCLASSIFIED]
>
>Am 8. September 2017 06:36:13 MESZ schrieb Andrew Bergman
><andrew.berg...@bom.gov.au>:
>>Where would I find these configured?
>>
>>-Original Message-
>>From: Robert Paschedag [mailto:robert.pasche...@web.de]
>>Sent: Friday, 8 September 2017 2:35 PM
>>To: spacewalk-list@redhat.com; Andrew Bergman; 
>>spacewalk-list@redhat.com
>>Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error 
>>[SEC=UNCLASSIFIED]
>>
>>Am 8. September 2017 03:29:15 MESZ schrieb Andrew Bergman
>><andrew.berg...@bom.gov.au>:
>>>Hi Spacewalk list,
>>>
>>>I am seeing an error on the Spacewalk 2.6 server I am responsible
>for:
>>>
>>>Jabber is running, port 5222 TCP is running from c2s process and is
>>>communicable via telnet.   I see no errors in the logs except from
>>>osa-dispatcher.
>>>
>>># osa-dispatcher -N -
>>>
>>>The last messages are:
>>>--> >>type='subscribed' id='presence-fb3eba-37' />
>>>
>>><-- >>'jabber:iq:roster' >>>jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='to'
>>>/>>>subscription='to' />
>>>
>>><-- >>to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>>>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'>>=
>>>'jabber:iq:roster' >>>jid='osad-441293a...@sdcvp-spacewalk01.bom.gov.au'
>subscription='both'
>>>/>
>>>
>>>--> >>'jabber:iq:roster'  />
>>>
>>><-- >>to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>>>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'>>=
>>>'jabber:iq:roster' >>>jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au'
>subscription='both'
>>>/>
>>>
>>><-- >>/>
>>>
>>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an error
>>stanza:
>>>', >>/>)
>>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an conflict.
>>>Restarting with new credentials.',)
>>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Error caught:',)
>>>
>>>ERROR: unhandled exception occurred: (can't write str to text
>stream).
>>>
>>>This looks similar to: 
>>>http://spacewalk-list.redhat.narkive.com/aH2kex2k/osa-dispatcher-prob
>>>l
>>>e
>>>ms-no-system-ever-reports
>>>
>>>However, I see no SSL errors, my hosts file is fine, with ipv6 ::1 
>>>entry for localhost, fully qualified hostname and the system hostname
>
>>>set to FQDN correctly.
>>>
>>>Does anyone have any suggestions?
>>>
>>>Thanks
>>>
>>>Andrew Bergman
>>
>>Do you use 2 IDs within your jabber configuration? The different "id"s
>
>>add the "switch" to other credentials looks strange to me.
>>
>>Robert
>>
>>___
>>Spacewalk-list mailing list
>>Spacewalk-list@redhat.com
>>https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>In the c2c or s2.xml I think. Within /etc/jabberd.
>
>Did you update your system some time ago?
>
>Robert
>
>___
>Spacewalk-list mailing list
>Spacewalk-list@redhat.com
>https://www.redhat.com/mailman/listinfo/spacewalk-list

Did you run the "rhnconf" tool after the upgrade? I think it's stated in the 
upgrade guide.

It "diffs" the configuration files from rpm packages.

And there MUST be an  tag within the config. I'm pretty pretty sure.

Robert


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

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Andrew Bergman]

How can I rebuild the jabber config cleanly?  I tried moving the xml files, 
restoring them from the .xml.dist files and then re-running 
spacewalk-setup-jabberd but then jabber fails to start.   I ended up restoring 
the original jabber config.

Config snippets with  sections below - note I censored the hostname for 
security purposes.

c2s.xml
  c2s
FQDN-censored-hostname
 -->

router.xml
  router

s2s.xml
  s2s

sm.xml

  FQDN-censored-hostname

FQDN-censored-hostname


vhost1.localdomain (also commented out)
vhost2.localdomain (also commented out)

Regards

Andrew Bergman

-Original Message-
From: Robert Paschedag [mailto:robert.pasche...@web.de] 
Sent: Friday, 8 September 2017 2:35 PM
To: spacewalk-list@redhat.com; Andrew Bergman; spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

Am 8. September 2017 03:29:15 MESZ schrieb Andrew Bergman 
<andrew.berg...@bom.gov.au>:
>Hi Spacewalk list,
>
>I am seeing an error on the Spacewalk 2.6 server I am responsible for:
>
>Jabber is running, port 5222 TCP is running from c2s process and is
>communicable via telnet.   I see no errors in the logs except from
>osa-dispatcher.
>
># osa-dispatcher -N -
>
>The last messages are:
>--> type='subscribed' id='presence-fb3eba-37' />
>
><-- 'jabber:iq:roster' >jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='to'
>/>subscription='to' />
>
><-- to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'>'jabber:iq:roster' >jid='osad-441293a...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/>
>
>--> 'jabber:iq:roster'  />
>
><-- to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'>'jabber:iq:roster' >jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/>
>
><-- />
>
>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an error stanza:
>', />)
>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an conflict.
>Restarting with new credentials.',)
>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Error caught:',)
>
>ERROR: unhandled exception occurred: (can't write str to text stream).
>
>This looks similar to: 
>http://spacewalk-list.redhat.narkive.com/aH2kex2k/osa-dispatcher-proble
>ms-no-system-ever-reports
>
>However, I see no SSL errors, my hosts file is fine, with ipv6 ::1 
>entry for localhost, fully qualified hostname and the system hostname 
>set to FQDN correctly.
>
>Does anyone have any suggestions?
>
>Thanks
>
>Andrew Bergman

Do you use 2 IDs within your jabber configuration? The different "id"s add the 
"switch" to other credentials looks strange to me.

Robert

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

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Robert Paschedag]

Am 8. September 2017 07:16:13 MESZ schrieb Andrew Bergman 
<andrew.berg...@bom.gov.au>:
>Yes, I did an upgrade from 2.2 to 2.6
>
>No ID's that I can see in any of those jabber configs in /etc/jabber
>
>-Original Message-
>From: Robert Paschedag [mailto:robert.pasche...@web.de] 
>Sent: Friday, 8 September 2017 3:11 PM
>To: spacewalk-list@redhat.com; Andrew Bergman;
>spacewalk-list@redhat.com
>Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error
>[SEC=UNCLASSIFIED]
>
>Am 8. September 2017 06:36:13 MESZ schrieb Andrew Bergman
><andrew.berg...@bom.gov.au>:
>>Where would I find these configured?
>>
>>-Original Message-
>>From: Robert Paschedag [mailto:robert.pasche...@web.de]
>>Sent: Friday, 8 September 2017 2:35 PM
>>To: spacewalk-list@redhat.com; Andrew Bergman; 
>>spacewalk-list@redhat.com
>>Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error 
>>[SEC=UNCLASSIFIED]
>>
>>Am 8. September 2017 03:29:15 MESZ schrieb Andrew Bergman
>><andrew.berg...@bom.gov.au>:
>>>Hi Spacewalk list,
>>>
>>>I am seeing an error on the Spacewalk 2.6 server I am responsible
>for:
>>>
>>>Jabber is running, port 5222 TCP is running from c2s process and is
>>>communicable via telnet.   I see no errors in the logs except from
>>>osa-dispatcher.
>>>
>>># osa-dispatcher -N -
>>>
>>>The last messages are:
>>>--> >>type='subscribed' id='presence-fb3eba-37' />
>>>
>>><-- >>'jabber:iq:roster' >>>jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='to'
>>>/>>>subscription='to' />
>>>
>>><-- >>to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>>>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'>>=
>>>'jabber:iq:roster' >>>jid='osad-441293a...@sdcvp-spacewalk01.bom.gov.au'
>subscription='both'
>>>/>
>>>
>>>--> >>'jabber:iq:roster'  />
>>>
>>><-- >>to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>>>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'>>=
>>>'jabber:iq:roster' >>>jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au'
>subscription='both'
>>>/>
>>>
>>><-- >>/>
>>>
>>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an error
>>stanza:
>>>', >>/>)
>>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an conflict.
>>>Restarting with new credentials.',)
>>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Error caught:',)
>>>
>>>ERROR: unhandled exception occurred: (can't write str to text
>stream).
>>>
>>>This looks similar to: 
>>>http://spacewalk-list.redhat.narkive.com/aH2kex2k/osa-dispatcher-probl
>>>e
>>>ms-no-system-ever-reports
>>>
>>>However, I see no SSL errors, my hosts file is fine, with ipv6 ::1 
>>>entry for localhost, fully qualified hostname and the system hostname
>
>>>set to FQDN correctly.
>>>
>>>Does anyone have any suggestions?
>>>
>>>Thanks
>>>
>>>Andrew Bergman
>>
>>Do you use 2 IDs within your jabber configuration? The different "id"s
>
>>add the "switch" to other credentials looks strange to me.
>>
>>Robert
>>
>>___
>>Spacewalk-list mailing list
>>Spacewalk-list@redhat.com
>>https://www.redhat.com/mailman/listinfo/spacewalk-list
>
>In the c2c or s2.xml I think. Within /etc/jabberd.
>
>Did you update your system some time ago?
>
>Robert
>
>___
>Spacewalk-list mailing list
>Spacewalk-list@redhat.com
>https://www.redhat.com/mailman/listinfo/spacewalk-list

Did you run the "rhnconf" tool after the upgrade? I think it's stated in the 
upgrade guide.

It "diffs" the configuration files from rpm packages.

And there MUST be an  tag within the config. I'm pretty pretty sure.

Robert


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

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Andrew Bergman]

Yes, I did an upgrade from 2.2 to 2.6

No ID's that I can see in any of those jabber configs in /etc/jabber

-Original Message-
From: Robert Paschedag [mailto:robert.pasche...@web.de] 
Sent: Friday, 8 September 2017 3:11 PM
To: spacewalk-list@redhat.com; Andrew Bergman; spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

Am 8. September 2017 06:36:13 MESZ schrieb Andrew Bergman 
<andrew.berg...@bom.gov.au>:
>Where would I find these configured?
>
>-Original Message-
>From: Robert Paschedag [mailto:robert.pasche...@web.de]
>Sent: Friday, 8 September 2017 2:35 PM
>To: spacewalk-list@redhat.com; Andrew Bergman; 
>spacewalk-list@redhat.com
>Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error 
>[SEC=UNCLASSIFIED]
>
>Am 8. September 2017 03:29:15 MESZ schrieb Andrew Bergman
><andrew.berg...@bom.gov.au>:
>>Hi Spacewalk list,
>>
>>I am seeing an error on the Spacewalk 2.6 server I am responsible for:
>>
>>Jabber is running, port 5222 TCP is running from c2s process and is
>>communicable via telnet.   I see no errors in the logs except from
>>osa-dispatcher.
>>
>># osa-dispatcher -N -
>>
>>The last messages are:
>>--> >type='subscribed' id='presence-fb3eba-37' />
>>
>><-- >'jabber:iq:roster' >>jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='to'
>>/>>subscription='to' />
>>
>><-- >to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'>=
>>'jabber:iq:roster' >>jid='osad-441293a...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>>/>
>>
>>--> >'jabber:iq:roster'  />
>>
>><-- >to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'>=
>>'jabber:iq:roster' >>jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>>/>
>>
>><-- >/>
>>
>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an error
>stanza:
>>', >/>)
>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an conflict.
>>Restarting with new credentials.',)
>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Error caught:',)
>>
>>ERROR: unhandled exception occurred: (can't write str to text stream).
>>
>>This looks similar to: 
>>http://spacewalk-list.redhat.narkive.com/aH2kex2k/osa-dispatcher-probl
>>e
>>ms-no-system-ever-reports
>>
>>However, I see no SSL errors, my hosts file is fine, with ipv6 ::1 
>>entry for localhost, fully qualified hostname and the system hostname 
>>set to FQDN correctly.
>>
>>Does anyone have any suggestions?
>>
>>Thanks
>>
>>Andrew Bergman
>
>Do you use 2 IDs within your jabber configuration? The different "id"s 
>add the "switch" to other credentials looks strange to me.
>
>Robert
>
>___
>Spacewalk-list mailing list
>Spacewalk-list@redhat.com
>https://www.redhat.com/mailman/listinfo/spacewalk-list

In the c2c or s2.xml I think. Within /etc/jabberd.

Did you update your system some time ago?

Robert

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

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Robert Paschedag]

Am 8. September 2017 06:45:13 MESZ schrieb Andrew Bergman 
:
>Definitely multiple IDs:
>
>[root@sdcvp-spacewalk01 rhn]# cat /tmp/osad_output.txt |grep "id="|sed
>-e "s/.*id='\(.*\)'.*$/\1/g"
>auth-get-d2f7c1-0'>>type='subscribed' id='presence-fb3eba-37' />
>>
>><-- >'jabber:iq:roster' >>jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='to'
>>/>>subscription='to' />
>>
>><-- >to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'>= 
>>'jabber:iq:roster' >>jid='osad-441293a...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>>/>
>>
>>--> >'jabber:iq:roster'  />
>>
>><-- >to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'>= 
>>'jabber:iq:roster' >>jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>>/>
>>
>><-- >/>
>>
>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an error
>stanza:
>>', >/>)
>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an conflict.
>>Restarting with new credentials.',)
>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Error caught:',)
>>
>>ERROR: unhandled exception occurred: (can't write str to text stream).
>>
>>This looks similar to: 
>>http://spacewalk-list.redhat.narkive.com/aH2kex2k/osa-dispatcher-proble
>>ms-no-system-ever-reports
>>
>>However, I see no SSL errors, my hosts file is fine, with ipv6 ::1 
>>entry for localhost, fully qualified hostname and the system hostname 
>>set to FQDN correctly.
>>
>>Does anyone have any suggestions?
>>
>>Thanks
>>
>>Andrew Bergman
>
>Do you use 2 IDs within your jabber configuration? The different "id"s
>add the "switch" to other credentials looks strange to me.
>
>Robert
>
>___
>Spacewalk-list mailing list
>Spacewalk-list@redhat.com
>https://www.redhat.com/mailman/listinfo/spacewalk-list

Look into the XML configuration files in /etc/jabberd. Should be an "" tag.
You'll see it.

Just on my way to work.

Robert

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

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Robert Paschedag]

Am 8. September 2017 06:36:13 MESZ schrieb Andrew Bergman 
<andrew.berg...@bom.gov.au>:
>Where would I find these configured?
>
>-Original Message-
>From: Robert Paschedag [mailto:robert.pasche...@web.de] 
>Sent: Friday, 8 September 2017 2:35 PM
>To: spacewalk-list@redhat.com; Andrew Bergman;
>spacewalk-list@redhat.com
>Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error
>[SEC=UNCLASSIFIED]
>
>Am 8. September 2017 03:29:15 MESZ schrieb Andrew Bergman
><andrew.berg...@bom.gov.au>:
>>Hi Spacewalk list,
>>
>>I am seeing an error on the Spacewalk 2.6 server I am responsible for:
>>
>>Jabber is running, port 5222 TCP is running from c2s process and is
>>communicable via telnet.   I see no errors in the logs except from
>>osa-dispatcher.
>>
>># osa-dispatcher -N -
>>
>>The last messages are:
>>--> >type='subscribed' id='presence-fb3eba-37' />
>>
>><-- >'jabber:iq:roster' >>jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='to'
>>/>>subscription='to' />
>>
>><-- >to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'>= 
>>'jabber:iq:roster' >>jid='osad-441293a...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>>/>
>>
>>--> >'jabber:iq:roster'  />
>>
>><-- >to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'>= 
>>'jabber:iq:roster' >>jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>>/>
>>
>><-- >/>
>>
>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an error
>stanza:
>>', >/>)
>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an conflict.
>>Restarting with new credentials.',)
>>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Error caught:',)
>>
>>ERROR: unhandled exception occurred: (can't write str to text stream).
>>
>>This looks similar to: 
>>http://spacewalk-list.redhat.narkive.com/aH2kex2k/osa-dispatcher-proble
>>ms-no-system-ever-reports
>>
>>However, I see no SSL errors, my hosts file is fine, with ipv6 ::1 
>>entry for localhost, fully qualified hostname and the system hostname 
>>set to FQDN correctly.
>>
>>Does anyone have any suggestions?
>>
>>Thanks
>>
>>Andrew Bergman
>
>Do you use 2 IDs within your jabber configuration? The different "id"s
>add the "switch" to other credentials looks strange to me.
>
>Robert
>
>___
>Spacewalk-list mailing list
>Spacewalk-list@redhat.com
>https://www.redhat.com/mailman/listinfo/spacewalk-list

In the c2c or s2.xml I think. Within /etc/jabberd.

Did you update your system some time ago?

Robert

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

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Andrew Bergman]

Definitely multiple IDs:

[root@sdcvp-spacewalk01 rhn]# cat /tmp/osad_output.txt |grep "id="|sed -e 
"s/.*id='\(.*\)'.*$/\1/g"
auth-get-d2f7c1-0'>type='subscribed' id='presence-fb3eba-37' />
>
><-- 'jabber:iq:roster' >jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='to'
>/>subscription='to' />
>
><-- to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'>'jabber:iq:roster' >jid='osad-441293a...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/>
>
>--> 'jabber:iq:roster'  />
>
><-- to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'>'jabber:iq:roster' >jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/>
>
><-- />
>
>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an error stanza:
>', />)
>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an conflict.
>Restarting with new credentials.',)
>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Error caught:',)
>
>ERROR: unhandled exception occurred: (can't write str to text stream).
>
>This looks similar to: 
>http://spacewalk-list.redhat.narkive.com/aH2kex2k/osa-dispatcher-proble
>ms-no-system-ever-reports
>
>However, I see no SSL errors, my hosts file is fine, with ipv6 ::1 
>entry for localhost, fully qualified hostname and the system hostname 
>set to FQDN correctly.
>
>Does anyone have any suggestions?
>
>Thanks
>
>Andrew Bergman

Do you use 2 IDs within your jabber configuration? The different "id"s add the 
"switch" to other credentials looks strange to me.

Robert

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

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Andrew Bergman]

Where would I find these configured?

-Original Message-
From: Robert Paschedag [mailto:robert.pasche...@web.de] 
Sent: Friday, 8 September 2017 2:35 PM
To: spacewalk-list@redhat.com; Andrew Bergman; spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

Am 8. September 2017 03:29:15 MESZ schrieb Andrew Bergman 
<andrew.berg...@bom.gov.au>:
>Hi Spacewalk list,
>
>I am seeing an error on the Spacewalk 2.6 server I am responsible for:
>
>Jabber is running, port 5222 TCP is running from c2s process and is
>communicable via telnet.   I see no errors in the logs except from
>osa-dispatcher.
>
># osa-dispatcher -N -
>
>The last messages are:
>--> type='subscribed' id='presence-fb3eba-37' />
>
><-- 'jabber:iq:roster' >jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='to'
>/>subscription='to' />
>
><-- to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'>'jabber:iq:roster' >jid='osad-441293a...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/>
>
>--> 'jabber:iq:roster'  />
>
><-- to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'>'jabber:iq:roster' >jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/>
>
><-- />
>
>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an error stanza:
>', />)
>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an conflict.
>Restarting with new credentials.',)
>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Error caught:',)
>
>ERROR: unhandled exception occurred: (can't write str to text stream).
>
>This looks similar to: 
>http://spacewalk-list.redhat.narkive.com/aH2kex2k/osa-dispatcher-proble
>ms-no-system-ever-reports
>
>However, I see no SSL errors, my hosts file is fine, with ipv6 ::1 
>entry for localhost, fully qualified hostname and the system hostname 
>set to FQDN correctly.
>
>Does anyone have any suggestions?
>
>Thanks
>
>Andrew Bergman

Do you use 2 IDs within your jabber configuration? The different "id"s add the 
"switch" to other credentials looks strange to me.

Robert

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

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Robert Paschedag]

Am 8. September 2017 03:29:15 MESZ schrieb Andrew Bergman 
:
>Hi Spacewalk list,
>
>I am seeing an error on the Spacewalk 2.6 server I am responsible for:
>
>Jabber is running, port 5222 TCP is running from c2s process and is
>communicable via telnet.   I see no errors in the logs except from
>osa-dispatcher.
>
># osa-dispatcher -N -
>
>The last messages are:
>--> type='subscribed' id='presence-fb3eba-37' />
>
><-- 'jabber:iq:roster' >jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='to'
>/>subscription='to' />
>
><-- to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'>'jabber:iq:roster' >jid='osad-441293a...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/>
>
>--> 'jabber:iq:roster'  />
>
><-- to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient'
>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'>'jabber:iq:roster' >jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/>
>
><-- />
>
>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an error stanza:
>', />)
>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an conflict.
>Restarting with new credentials.',)
>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Error caught:',)
>
>ERROR: unhandled exception occurred: (can't write str to text stream).
>
>This looks similar to: 
>http://spacewalk-list.redhat.narkive.com/aH2kex2k/osa-dispatcher-problems-no-system-ever-reports
>
>However, I see no SSL errors, my hosts file is fine, with ipv6 ::1
>entry for localhost, fully qualified hostname and the system hostname
>set to FQDN correctly.
>
>Does anyone have any suggestions?
>
>Thanks
>
>Andrew Bergman

Do you use 2 IDs within your jabber configuration? The different "id"s add the 
"switch" to other credentials looks strange to me.

Robert

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

Re: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

[Andrew Bergman]

Additional:

I see the following errors in the logs:

2017/09/08 03:15:11 -00:00 31850 0.0.0.0: 
osad/jabber_lib.register_callback(>, 'error', None, None, None, 
None)
2017/09/08 03:15:11 -00:00 31850 0.0.0.0: 
osad/jabber_lib._expire_callbacks_list([[>, None, None]], 
1504840511.7368159)
2017/09/08 03:15:11 -00:00 31850 0.0.0.0: 
osad/jabber_lib._expire_callbacks_list([[>, None, None]], 
1504840511.7537439)
2017/09/08 03:15:11 -00:00 31850 0.0.0.0: 
osad/jabber_lib._expire_callbacks_list([[>, None, None]], 
1504840511.7620511)
2017/09/08 03:15:11 -00:00 31850 0.0.0.0: 
osad/jabber_lib._expire_callbacks_list([[>, None, None]], 
1504840511.77037)
2017/09/08 03:15:19 -00:00 31850 0.0.0.0: 
osad/jabber_lib._expire_callbacks_list([[>, None, None]], 
1504840519.8019159)
2017/09/08 03:15:19 -00:00 31850 0.0.0.0: 
osad/jabber_lib._expire_callbacks_list([[>, None, None]], 
1504840519.8847489)
2017/09/08 03:15:19 -00:00 31850 0.0.0.0: 
osad/jabber_lib._expire_callbacks_list([[>, None, None]], 
1504840519.8934169)
2017/09/08 03:15:19 -00:00 31850 0.0.0.0: 
osad/jabber_lib._expire_callbacks_list([[>, None, None]], 
1504840519.904799)
2017/09/08 03:15:19 -00:00 31850 0.0.0.0: 
osad/jabber_lib._expire_callbacks_list([[>, None, None]], 
1504840519.9452281)
2017/09/08 03:15:19 -00:00 31850 0.0.0.0: 
osad/jabber_lib._expire_callbacks_list([[>, None, None]], 
1504840519.9523239)
2017/09/08 03:15:19 -00:00 31850 0.0.0.0: 
osad/jabber_lib._expire_callbacks_list([[>, None, None]], 
1504840519.9636769)
2017/09/08 03:15:27 -00:00 31850 0.0.0.0: 
osad/jabber_lib.dispatch(,)
2017/09/08 03:15:27 -00:00 31850 0.0.0.0: 
osad/jabber_lib._expire_callbacks_list([[>, None, None]], 
1504840527.989017)
2017/09/08 03:15:27 -00:00 31850 0.0.0.0: 
osad/jabber_lib._get_callbacks(,)
2017/09/08 03:15:27 -00:00 31850 0.0.0.0: osad/jabber_lib.dispatch('Calling 
callback', >, )
2017/09/08 03:15:27 -00:00 31850 0.0.0.0: 
osad/jabber_lib._error_callback('ERROR', 'Received an error stanza: ', 
)
2017/09/08 03:15:27 -00:00 31850 0.0.0.0: 
osad/jabber_lib._error_callback('ERROR', 'Received an conflict. Restarting with 
new credentials.')

The errors mostly are generic and unlikely to be related but the conflict stuff 
made me look away from OSA-dispatcher and Spacewalk and at the underlying 
protocol XMPP.

When investigating what a "conflict" means in XMPP terms I find the following:  
https://xmpp.org/rfcs/rfc3921.html

If there is already an active resource of the same name, the server MUST either 
(1) terminate the active resource and allow the newly-requested session, or (2) 
disallow the newly-requested session and maintain the active resource. Which of 
these the server does is up to the implementation, although it is RECOMMENDED 
to implement case #1. In case #1, the server SHOULD send a  stream 
error to the active resource, terminate the XML stream and underlying TCP 
connection for the active resource, and return a IQ stanza of type "result" 
(indicating success) to the newly-requested session. In case #2, the server 
SHOULD send a  stanza error to the newly-requested session but 
maintain the XML stream for that connection so that the newly-requested session 
has an opportunity to negotiate a non-conflicting resource identifier before 
sending another request for session establishment.
Step 2 (alt): Server informs existing active resource of resource conflict 
(case #1):

  


Step 2 (alt): Server informs newly-requested session of resource conflict (case 
#2):

  
  

  

After establishing a session, a client SHOULD send initial presence and request 
its roster as described below, although these actions are OPTIONAL.
Note: Before allowing the creation of instant messaging and presence sessions, 
a server MAY require prior account provisioning. Possible methods for account 
provisioning include account creation by a server administrator as well as 
in-band account registration using the 'jabber:iq:register' namespace; the 
latter method is out of scope for this memo, but is documented in 
[JEP‑0077], published by the 
Jabber Software Foundation [JSF].
Have I possibly hit a bug here in osa-dispatcher or jabber?

Regards

Andrew Bergman



From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Andrew Bergman
Sent: Friday, 8 September 2017 11:29 AM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] OSA Dispatcher "conflict" error [SEC=UNCLASSIFIED]

Hi Spacewalk list,

I am seeing an error on the Spacewalk 2.6 server I am responsible for:

Jabber is running, port 5222 TCP is running from c2s process and is 
communicable via telnet.   I see no errors in the logs except from 
osa-dispatcher.

# osa-dispatcher -N –

The last messages are:
--> 

<-- 

<-- 

--> 

<-- 

<-- 

Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an error stanza: ', 
)
Spacewalk 20123 2017/09/07 06:49:21 -00:00: