<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 14 (filtered medium)"> <style></style> </head> <body lang="EN-AU" link="blue" vlink="purple"> <div class="WordSection1"> Additional:<o:p></o:p> <o:p> </o:p> I see the following errors in the logs:<o:p></o:p> <o:p> </o:p> 2017/09/08 03:15:11 -00:00 31850 0.0.0.0: osad/jabber_lib.register_callback(<bound method Runner._error_callback of <osad.osa_dispatcher.Runner instance at 0x1ec8710>>, 'error', None, None, None, None)<o:p></o:p> 2017/09/08 03:15:11 -00:00 31850 0.0.0.0: osad/jabber_lib._expire_callbacks_list([[<bound method Runner._error_callback of <osad.osa_dispatcher.Runner instance at 0x1ec8710>>, None, None]], 1504840511.7368159)<o:p></o:p> 2017/09/08 03:15:11 -00:00 31850 0.0.0.0: osad/jabber_lib._expire_callbacks_list([[<bound method Runner._error_callback of <osad.osa_dispatcher.Runner instance at 0x1ec8710>>, None, None]], 1504840511.7537439)<o:p></o:p> 2017/09/08 03:15:11 -00:00 31850 0.0.0.0: osad/jabber_lib._expire_callbacks_list([[<bound method Runner._error_callback of <osad.osa_dispatcher.Runner instance at 0x1ec8710>>, None, None]], 1504840511.7620511)<o:p></o:p> 2017/09/08 03:15:11 -00:00 31850 0.0.0.0: osad/jabber_lib._expire_callbacks_list([[<bound method Runner._error_callback of <osad.osa_dispatcher.Runner instance at 0x1ec8710>>, None, None]], 1504840511.77037)<o:p></o:p> 2017/09/08 03:15:19 -00:00 31850 0.0.0.0: osad/jabber_lib._expire_callbacks_list([[<bound method Runner._error_callback of <osad.osa_dispatcher.Runner instance at 0x1ec8710>>, None, None]], 1504840519.8019159)<o:p></o:p> 2017/09/08 03:15:19 -00:00 31850 0.0.0.0: osad/jabber_lib._expire_callbacks_list([[<bound method Runner._error_callback of <osad.osa_dispatcher.Runner instance at 0x1ec8710>>, None, None]], 1504840519.8847489)<o:p></o:p> 2017/09/08 03:15:19 -00:00 31850 0.0.0.0: osad/jabber_lib._expire_callbacks_list([[<bound method Runner._error_callback of <osad.osa_dispatcher.Runner instance at 0x1ec8710>>, None, None]], 1504840519.8934169)<o:p></o:p> 2017/09/08 03:15:19 -00:00 31850 0.0.0.0: osad/jabber_lib._expire_callbacks_list([[<bound method Runner._error_callback of <osad.osa_dispatcher.Runner instance at 0x1ec8710>>, None, None]], 1504840519.904799)<o:p></o:p> 2017/09/08 03:15:19 -00:00 31850 0.0.0.0: osad/jabber_lib._expire_callbacks_list([[<bound method Runner._error_callback of <osad.osa_dispatcher.Runner instance at 0x1ec8710>>, None, None]], 1504840519.9452281)<o:p></o:p> 2017/09/08 03:15:19 -00:00 31850 0.0.0.0: osad/jabber_lib._expire_callbacks_list([[<bound method Runner._error_callback of <osad.osa_dispatcher.Runner instance at 0x1ec8710>>, None, None]], 1504840519.9523239)<o:p></o:p> 2017/09/08 03:15:19 -00:00 31850 0.0.0.0: osad/jabber_lib._expire_callbacks_list([[<bound method Runner._error_callback of <osad.osa_dispatcher.Runner instance at 0x1ec8710>>, None, None]], 1504840519.9636769)<o:p></o:p> 2017/09/08 03:15:27 -00:00 31850 0.0.0.0: osad/jabber_lib.dispatch(<error><conflict xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' /></error>,)<o:p></o:p> 2017/09/08 03:15:27 -00:00 31850 0.0.0.0: osad/jabber_lib._expire_callbacks_list([[<bound method Runner._error_callback of <osad.osa_dispatcher.Runner instance at 0x1ec8710>>, None, None]], 1504840527.989017)<o:p></o:p> 2017/09/08 03:15:27 -00:00 31850 0.0.0.0: osad/jabber_lib._get_callbacks(<error><conflict xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' /></error>,)<o:p></o:p> 2017/09/08 03:15:27 -00:00 31850 0.0.0.0: osad/jabber_lib.dispatch('Calling callback', <bound method Runner._error_callback of <osad.osa_dispatcher.Runner instance at 0x1ec8710>>, <error><conflict xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' /></error>)<o:p></o:p> 2017/09/08 03:15:27 -00:00 31850 0.0.0.0: osad/jabber_lib._error_callback('ERROR', 'Received an error stanza: ', <error><conflict xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' /></error>)<o:p></o:p> 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.')<o:p></o:p> <o:p> </o:p> 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.<o:p></o:p> <o:p> </o:p> When investigating what a "conflict" means in XMPP terms I find the following: <a href="https://xmpp.org/rfcs/rfc3921.html">https://xmpp.org/rfcs/rfc3921.html</a><o:p></o:p> <o:p> </o:p> 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 <conflict/> 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 <conflict/> 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.<o:p></o:p> Step 2 (alt): Server informs existing active resource of resource conflict (case #1):<o:p></o:p> <stream:error><o:p></o:p> <conflict xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><o:p></o:p> </stream:error><o:p></o:p> </stream:stream><o:p></o:p> Step 2 (alt): Server informs newly-requested session of resource conflict (case #2):<o:p></o:p> <iq from='example.com' type='error' id='sess_1'><o:p></o:p> <session xmlns='urn:ietf:params:xml:ns:xmpp-session'/><o:p></o:p> <error type='cancel'><o:p></o:p> <conflict xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/><o:p></o:p> </error><o:p></o:p> </iq><o:p></o:p> After establishing a session, a client SHOULD send initial presence and request its roster as described below, although these actions are OPTIONAL.<o:p></o:p> 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 <a href="https://xmpp.org/rfcs/rfc3921.html#JEP-0077">[JEP‑0077]</a>, published by the <a href="https://xmpp.org/rfcs/rfc3921.html#JSF">Jabber Software Foundation</a> [JSF].<o:p></o:p> Have I possibly hit a bug here in osa-dispatcher or jabber?<o:p></o:p> <o:p> </o:p> Regards<o:p></o:p> <o:p> </o:p> Andrew Bergman<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: spacewalk-list-bounces@redhat.com [mailto:spacewalk-list-bounces@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]<o:p></o:p> </div> </div> <o:p> </o:p> Hi Spacewalk list,<o:p></o:p> <o:p> </o:p> I am seeing an error on the Spacewalk 2.6 server I am responsible for:<o:p></o:p> <o:p> </o:p> 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.<o:p></o:p> <o:p> </o:p> # osa-dispatcher -N –vvvvvvvvvvvv<o:p></o:p> <o:p> </o:p> The last messages are:<o:p></o:p> --> <presence to='osad-bb7d64e5e1@sdcvp-spacewalk01.bom.gov.au' type='subscribed' id='presence-fb3eba-37' /><o:p></o:p> <o:p> </o:p> <-- <iq type='result' id='iq-request-c8a784-8'><query xmlns = 'jabber:iq:roster' ><item jid='osad-bb7d64e5e1@sdcvp-spacewalk01.bom.gov.au' subscription='to' /><item jid='osad-441293a7e7@sdcvp-spacewalk01.bom.gov.au' subscription='to' /></query></iq><o:p></o:p> <o:p> </o:p> <-- <iq to='rhn-dispatcher-sat@sdcvp-spacewalk01.bom.gov.au/superclient' type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'><query xmlns = 'jabber:iq:roster' ><item jid='osad-441293a7e7@sdcvp-spacewalk01.bom.gov.au' subscription='both' /></query></iq><o:p></o:p> <o:p> </o:p> --> <iq type='get' id='iq-request-c8a784-9'><query xmlns = 'jabber:iq:roster' /></iq><o:p></o:p> <o:p> </o:p> <-- <iq to='rhn-dispatcher-sat@sdcvp-spacewalk01.bom.gov.au/superclient' type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'><query xmlns = 'jabber:iq:roster' ><item jid='osad-bb7d64e5e1@sdcvp-spacewalk01.bom.gov.au' subscription='both' /></query></iq><o:p></o:p> <o:p> </o:p> <-- <error><conflict xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' /></error><o:p></o:p> <o:p> </o:p> 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>)<o:p></o:p> Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Received an conflict. Restarting with new credentials.',)<o:p></o:p> Spacewalk 20123 2017/09/07 06:49:21 -00:00: ('Error caught:',)<o:p></o:p> <o:p> </o:p> ERROR: unhandled exception occurred: (can't write str to text stream).<o:p></o:p> <o:p> </o:p> This looks similar to: <a href="http://spacewalk-list.redhat.narkive.com/aH2kex2k/osa-dispatcher-problems-no-system-ever-reports"> http://spacewalk-list.redhat.narkive.com/aH2kex2k/osa-dispatcher-problems-no-system-ever-reports</a><o:p></o:p> <o:p> </o:p> 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.<o:p></o:p> <o:p> </o:p> Does anyone have any suggestions?<o:p></o:p> <o:p> </o:p> Thanks<o:p></o:p> <o:p> </o:p> Andrew Bergman<o:p></o:p> <o:p> </o:p> </div> </body> </html>