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 <local> 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 -vvvvvvvvvvvv >>> >>>The last messages are: >>>--> <presence to='osad-bb7d64e...@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-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='to' >>>/><item jid='osad-441293a...@sdcvp-spacewalk01.bom.gov.au' >>>subscription='to' /></query></iq> >>> >>><-- <iq >>>to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient' >>>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'><query xmlns >>= >>>'jabber:iq:roster' ><item >>>jid='osad-441293a...@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-...@sdcvp-spacewalk01.bom.gov.au/superclient' >>>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'><query xmlns >>= >>>'jabber:iq:roster' ><item >>>jid='osad-bb7d64e...@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-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 <id> 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
