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

Andrew Bergman Andrew.Bergman at bom.gov.au
Fri Sep 8 04:45:13 UTC 2017


Definitely multiple IDs:

[root at sdcvp-spacewalk01 rhn]# cat /tmp/osad_output.txt |grep "id="|sed -e "s/.*id='\(.*\)'.*$/\1/g"
auth-get-d2f7c1-0'><query xmlns = 'jabber:iq:auth
auth-get-d2f7c1-0'><query xmlns = 'jabber:iq:auth
auth-set-d2f7c1-1'><query xmlns = 'jabber:iq:auth
auth-set-d2f7c1-1
iq-request-d2f7c1-2'><query xmlns = 'jabber:iq:roster
osad-441293a7e7 at sdcvp-spacewalk01.bom.gov.au' subscription='to
iq-request-d2f7c1-3'><query xmlns = 'jabber:iq:roster
osad-441293a7e7 at sdcvp-spacewalk01.bom.gov.au' subscription='to
iq-request-d2f7c1-4'><query xmlns = 'jabber:iq:roster

I just have no idea where these are set

Regards

Andrew Bergman

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

Am 8. September 2017 03:29:15 MESZ schrieb Andrew Bergman <Andrew.Bergman at 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 -vvvvvvvvvvvv
>
>The last messages are:
>--> <presence to='osad-bb7d64e5e1 at sdcvp-spacewalk01.bom.gov.au'
>type='subscribed' id='presence-fb3eba-37' />
>
><-- <iq type='result' id='iq-request-c8a784-8'><query xmlns = 
>'jabber:iq:roster' ><item 
>jid='osad-bb7d64e5e1 at sdcvp-spacewalk01.bom.gov.au' subscription='to'
>/><item jid='osad-441293a7e7 at sdcvp-spacewalk01.bom.gov.au'
>subscription='to' /></query></iq>
>
><-- <iq
>to='rhn-dispatcher-sat at sdcvp-spacewalk01.bom.gov.au/superclient'
>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'><query xmlns = 
>'jabber:iq:roster' ><item 
>jid='osad-441293a7e7 at sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/></query></iq>
>
>--> <iq type='get' id='iq-request-c8a784-9'><query xmlns =
>'jabber:iq:roster'  /></iq>
>
><-- <iq
>to='rhn-dispatcher-sat at sdcvp-spacewalk01.bom.gov.au/superclient'
>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'><query xmlns = 
>'jabber:iq:roster' ><item 
>jid='osad-bb7d64e5e1 at sdcvp-spacewalk01.bom.gov.au' subscription='both'
>/></query></iq>
>
><-- <error><conflict xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' 
>/></error>
>
>Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an error stanza:
>', <error><conflict xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' 
>/></error>)
>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




More information about the Spacewalk-list mailing list