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...then....what 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] > >Hmm....a 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 -vvvvvvvvvvvvvvv >>--> <?xml version='1.0' encoding='UTF-8'?><stream:stream >>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&data=02%7C01%7CPaschedag.Netlution >>%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc21 >>6b81f62d%7C0%7C0%7C636407058161574802&sdata=bE%2BPcIfY6%2BOZfhh5AYInJpu >>z5vUHs3JSU5rcJdv5OX0%3D&reserved=0' version='1.0'> >> >><-- <features><address xmlns = >'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Faffinix.com%2Fjabber%2Faddress&data=02%7C01%7CPaschedag.Netlution%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636407058161574802&sdata=hgOOLVQoxgPD1o%2BQVX%2Bs2UbkpW6PXKRFGgOxdwq8NeI%3D&reserved=0' >>>134.178.145.92</address><auth xmlns = >>'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb >>er.org%2Ffeatures%2Fiq-auth&data=02%7C01%7CPaschedag.Netlution%40swr.de >>%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d% >>7C0%7C0%7C636407058161574802&sdata=eO6CwoaOmrVZdY2uSR6WgvYPlGtgzDPuoS%2 >>BanJk8stU%3D&reserved=0' /><register xmlns = >>'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb >>er.org%2Ffeatures%2Fiq-register&data=02%7C01%7CPaschedag.Netlution%40sw >>r.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f >>62d%7C0%7C0%7C636407058161574802&sdata=4p%2BrR4rREwE02sakNKJFw2PQmUwQyt >>LD0sdcXlj1Ov0%3D&reserved=0' /><starttls xmlns = >>'urn:ietf:params:xml:ns:xmpp-tls' ><required /></starttls></features> >> >><-- <proceed /> >> >>--> <?xml version='1.0' encoding='UTF-8'?><stream:stream >>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&data=02%7C01%7CPaschedag.Netlution >>%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc21 >>6b81f62d%7C0%7C0%7C636407058161574802&sdata=bE%2BPcIfY6%2BOZfhh5AYInJpu >>z5vUHs3JSU5rcJdv5OX0%3D&reserved=0' version='1.0'> >> >><-- <features><address xmlns = >'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Faffinix.com%2Fjabber%2Faddress&data=02%7C01%7CPaschedag.Netlution%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636407058161574802&sdata=hgOOLVQoxgPD1o%2BQVX%2Bs2UbkpW6PXKRFGgOxdwq8NeI%3D&reserved=0' >>>134.178.145.92</address><mechanisms xmlns = >>'urn:ietf:params:xml:ns:xmpp-sasl' >>><mechanism>EXTERNAL</mechanism><mechanism>PLAIN</mechanism><mechanism> >>>DIGEST-MD5</mechanism></mechanisms><auth >>xmlns = >>'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb >>er.org%2Ffeatures%2Fiq-auth&data=02%7C01%7CPaschedag.Netlution%40swr.de >>%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d% >>7C0%7C0%7C636407058161574802&sdata=eO6CwoaOmrVZdY2uSR6WgvYPlGtgzDPuoS%2 >>BanJk8stU%3D&reserved=0' /><register xmlns = >>'https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fjabb >>er.org%2Ffeatures%2Fiq-register&data=02%7C01%7CPaschedag.Netlution%40sw >>r.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f >>62d%7C0%7C0%7C636407058161574802&sdata=4p%2BrR4rREwE02sakNKJFw2PQmUwQyt >>LD0sdcXlj1Ov0%3D&reserved=0' /></features> >> >>--> <iq type='get' id='auth-get-02c950-0'><query xmlns = >>'jabber:iq:auth' ><username>rhn-dispatcher-sat</username></query></iq> >> >><-- <iq type='result' id='auth-get-02c950-0'><query xmlns = >>'jabber:iq:auth' ><username>rhn-dispatcher-sat</username><resource >>/><password /><digest /></query></iq> >> >>--> <iq type='set' id='auth-set-02c950-1'><query xmlns = >>'jabber:iq:auth' >>><username>rhn-dispatcher-sat</username><resource>superclient</resource >>>><digest>e004d72e248acb5f9ffd8db5be2655993c7ed389</digest></query></iq >>>> >> >><-- <iq type='result' id='auth-set-02c950-1' /> >> >>--> <iq type='get' id='iq-request-02c950-2'><query xmlns = >>'jabber:iq:roster' /></iq> >> >><-- <iq type='result' id='iq-request-02c950-2'><query xmlns = >>'jabber:iq:roster' ><item >>jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both' >>/><item jid='osad-441293a...@sdcvp-spacewalk01.bom.gov.au' >>subscription='both' /></query></iq> >> >>--> <presence /> >> >>--> <iq type='get' id='iq-request-02c950-3'><query xmlns = >>'jabber:iq:roster' /></iq> >> >><-- <presence >>to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient' >>from='osad-441293a...@sdcvp-spacewalk01.bom.gov.au/osad'><delay xmlns >= >>'urn:xmpp:delay' stamp='2017-09-08T06:06:05Z' >>from='osad-441293a...@sdcvp-spacewalk01.bom.gov.au/osad' /></presence> >> >><-- <iq type='result' id='iq-request-02c950-3'><query xmlns = >>'jabber:iq:roster' ><item >>jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both' >>/><item jid='osad-441293a...@sdcvp-spacewalk01.bom.gov.au' >>subscription='both' /></query></iq> >> >><-- <presence >>to='rhn-dispatcher-...@sdcvp-spacewalk01.bom.gov.au/superclient' >>from='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au/osad'><delay xmlns >= >>'urn:xmpp:delay' stamp='2017-09-08T06:06:53Z' >>from='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au/osad' /></presence> >> >>--> <iq type='get' id='iq-request-02c950-4'><query xmlns = >>'jabber:iq:roster' /></iq> >> >><-- <iq type='result' id='iq-request-02c950-4'><query xmlns = >>'jabber:iq:roster' ><item >>jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both' >>/><item jid='osad-441293a...@sdcvp-spacewalk01.bom.gov.au' >>subscription='both' /></query></iq> >> >>--> <iq type='get' id='iq-request-02c950-5'><query xmlns = >>'jabber:iq:roster' /></iq> >> >><-- <iq type='result' id='iq-request-02c950-5'><query xmlns = >>'jabber:iq:roster' ><item >>jid='osad-bb7d64e...@sdcvp-spacewalk01.bom.gov.au' subscription='both' >>/><item jid='osad-441293a...@sdcvp-spacewalk01.bom.gov.au' >>subscription='both' /></query></iq> >> >>--> <iq type='get' id='iq-request-02c950-6'><query xmlns = >>'jabber:iq:roster' /></iq> >> >><-- <error><conflict xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' >>/></error> >> >>Spacewalk 17712 2017/09/11 00:52:44 -00:00: ('Received an error >stanza: >>', <error><conflict xmlns = 'urn:ietf:params:xml:ns:xmpp-streams' >>/></error>) >>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'><query >xmlns >>>= >> >>And later set to another id >> >>>>to='rhn-dispatcher-sat@FQDN-censored-address/superclient' >>>>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'><query >xmlns >>>= >> >>All of "my" spacewalk clients are registered with a name starting with > >>"osad-<10hexdigits>@<my spacewalk-server-id>" >> >>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 'announce' added to chain 'pkt-sm' (order 6 >>index 12 seq 1) Sep 8 06:04:55 censored-address jabberd/sm[21702]: >>module 'help' added to chain 'pkt-sm' (order 7 index 18 seq 0) Sep 8 >>06:04:55 censored-address jabberd/sm[21702]: module 'echo' added to >>chain 'pkt-sm' (order 8 index 19 seq 0) Sep 8 06:04:55 >>censored-address jabberd/sm[21702]: module 'status' added to chain >>'pkt-sm' (order 9 index 0 seq 3) Sep 8 06:04:55 censored-address >>jabberd/sm[21702]: module 'presence' added to chain 'pkt-sm' (order 10 > >>index 13 seq 2) Sep 8 06:04:55 censored-address jabberd/sm[21702]: >>module 'roster' added to chain 'pkt-user' (order 0 index 4 seq 1) Sep >>8 06:04:55 censored-address jabberd/sm[21702]: module 'presence' added > >>to chain 'pkt-user' (order 1 index 13 seq 3) Sep 8 06:04:55 >>censored-address jabberd/sm[21702]: module 'iq-vcard' added to chain >>'pkt-user' (order 2 index 6 seq 1) Sep 8 06:04:55 censored-address >>jabberd/sm[21702]: module 'amp' added to chain 'pkt-user' (order 3 >>index 10 seq 2) Sep 8 06:04:55 censored-address jabberd/sm[21702]: >>module 'deliver' added to chain 'pkt-user' (order 4 index 14 seq 1) >Sep >>8 06:04:55 censored-address jabberd/sm[21702]: module 'vacation' added > >>to chain 'pkt-user' (order 5 index 5 seq 1) Sep 8 06:04:55 >>censored-address jabberd/sm[21702]: module 'offline' added to chain >>'pkt-user' (order 6 index 11 seq 1) Sep 8 06:04:55 censored-address >>jabberd/sm[21702]: module 'iq-last' added to chain 'pkt-user' (order 7 > >>index 1 seq 2) Sep 8 06:04:55 censored-address jabberd/sm[21702]: >>module 'session' added to chain 'pkt-router' (order 0 index 15 seq 1) >>Sep 8 06:04:55 censored-address jabberd/sm[21702]: module 'disco' >>added to chain 'pkt-router' (order 1 index 9 seq 2) Sep 8 06:04:55 >>censored-address jabberd/sm[21702]: module 'active' added to chain >>'user-load' (order 0 index 20 seq 0) Sep 8 06:04:55 censored-address >>jabberd/sm[21702]: module 'roster' added to chain 'user-load' (order 1 > >>index 4 seq 2) Sep 8 06:04:55 censored-address jabberd/sm[21702]: >>module 'roster-publish' added to chain 'user-load' (order 2 index 21 >>seq 0) Sep 8 06:04:55 censored-address jabberd/sm[21702]: module >>'privacy' added to chain 'user-load' (order 3 index 3 seq 3) Sep 8 >>06:04:55 censored-address jabberd/sm[21702]: module 'vacation' added >to >>chain 'user-load' (order 4 index 5 seq 2) Sep 8 06:04:55 >>censored-address jabberd/sm[21702]: module 'active' added to chain >>'user-create' (order 0 index 20 seq 1) Sep 8 06:04:55 >censored-address >>jabberd/sm[21702]: module 'template-roster' added to chain >>'user-create' (order 1 index 22 seq 0) Sep 8 06:04:55 >censored-address >>jabberd/sm[21702]: module 'active' added to chain 'user-delete' (order >>0 index 20 seq 2) Sep 8 06:04:55 censored-address jabberd/sm[21702]: >>module 'announce' added to chain 'user-delete' (order 1 index 12 seq >2) >>Sep 8 06:04:55 censored-address jabberd/sm[21702]: module 'offline' >>added to chain 'user-delete' (order 2 index 11 seq 2) Sep 8 06:04:55 >>censored-address jabberd/sm[21702]: module 'privacy' added to chain >>'user-delete' (order 3 index 3 seq 4) Sep 8 06:04:55 censored-address >>jabberd/sm[21702]: module 'roster' added to chain 'user-delete' (order >>4 index 4 seq 3) Sep 8 06:04:55 censored-address jabberd/sm[21702]: >>module 'vacation' added to chain 'user-delete' (order 5 index 5 seq 3) > >>Sep 8 06:04:55 censored-address jabberd/sm[21702]: module 'status' >>added to chain 'user-delete' (order 6 index 0 seq 4) Sep 8 06:04:55 >>censored-address jabberd/sm[21702]: module 'iq-last' added to chain >>'user-delete' (order 7 index 1 seq 3) Sep 8 06:04:55 censored-address >>jabberd/sm[21702]: module 'iq-private' added to chain 'user-delete' >>(order 8 index 8 seq 1) Sep 8 06:04:55 censored-address >>jabberd/sm[21702]: module 'iq-vcard' added to chain 'user-delete' >>(order 9 index 6 seq 2) Sep 8 06:04:55 censored-address >>jabberd/sm[21702]: module 'iq-version' added to chain 'disco-extend' >>(order 0 index 17 seq 1) Sep 8 06:04:55 censored-address >>jabberd/sm[21702]: module 'help' added to chain 'disco-extend' (order >1 >>index 18 seq 1) Sep 8 06:04:55 censored-address jabberd/sm[21702]: >>version: jabberd sm 2.6.1 Sep 8 06:04:55 censored-address >>jabberd/sm[21702]: [FQDN-censored-address] configured Sep 8 06:04:55 >>censored-address jabberd/sm[21702]: 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=33974] connect Sep 8 06:04:55 > >>censored-address jabberd/router[21694]: [127.0.0.1, port=33974] >>authenticated as jabberd@jabberd-router Sep 8 06:04:55 >>censored-address jabberd/sm[21702]: connection to router established >>Sep 8 06:04:55 censored-address jabberd/router[21694]: >>[FQDN-censored-address] online (bound to 127.0.0.1, port 33974) Sep 8 >>06:04:55 censored-address jabberd/c2s[21710]: modules search path: >>/usr/lib64/jabberd Sep 8 06:04:55 censored-address >jabberd/c2s[21710]: >>loading 'db' authreg module Sep 8 06:04:55 censored-address >>jabberd/c2s[21710]: initialized auth module 'db' >>Sep 8 06:04:55 censored-address jabberd/c2s[21710]: starting up Sep >8 >>06:04:55 censored-address jabberd/c2s[21710]: process id is 21710, >>written to /var/lib/jabberd/pid/c2s.pid Sep 8 06:04:55 >>censored-address jabberd/sm[21702]: FQDN-censored-address ready for >>sessions Sep 8 06:04:55 censored-address jabberd/c2s[21710]: >>[FQDN-censored-address] configured; realm=, authreg=db, registration >>enabled, using PEM:/etc/pki/spacewalk/jabberd/server.pem >>Sep 8 06:04:55 censored-address jabberd/c2s[21710]: 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=33976] >connect >>Sep 8 06:04:55 censored-address jabberd/router[21694]: [127.0.0.1, >>port=33976] authenticated as jabberd@jabberd-router Sep 8 06:04:55 >>censored-address jabberd/c2s[21710]: connection to router established >>Sep 8 06:04:55 censored-address jabberd/router[21694]: [c2s] online >>(bound to 127.0.0.1, port 33976) Sep 8 06:04:55 censored-address >>jabberd/s2s[21718]: starting up (interval=3, queue=60, keepalive=0, >>idle=86400) Sep 8 06: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 <id> sections below - note I censored the >>hostname >>>for security purposes. >>> >>>c2s.xml >>> <id>c2s</id> >>><id require-starttls="false" >>>pemfile="/etc/pki/spacewalk/jabberd/server.pem" realm="" >>>register-enable="true">FQDN-censored-hostname</id> >>> <id realm='company.int' >>> <id password-change='mu' /> --> >>> >>>router.xml >>> <id>router</id> >>> >>>s2s.xml >>> <id>s2s</id> >>> >>>sm.xml >>><sm> >>> <id>FQDN-censored-hostname</id> >>><local> >>> <id>FQDN-censored-hostname</id> >>> <!-- <id>FQDN-censored-hostname</id> --> >>> <!--<id>localhost.localdomain</id> --> >>> <id>vhost1.localdomain</id> (also commented out) >>> <id>vhost2.localdomain</id> (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 -vvvvvvvvvvvv >>>> >>>>The last messages are: >>>>--> <presence to='osad-bb7d64e5e1@FQDN-censored-address' >>>>type='subscribed' id='presence-fb3eba-37' /> >>>> >>>><-- <iq type='result' id='iq-request-c8a784-8'><query xmlns = >>>>'jabber:iq:roster' ><item >jid='osad-bb7d64e5e1@FQDN-censored-address' >>>>subscription='to' >>>>/><item jid='osad-441293a7e7@FQDN-censored-address' >>>>subscription='to' /></query></iq> >>>> >>>><-- <iq >>>>to='rhn-dispatcher-sat@FQDN-censored-address/superclient' >>>>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'><query >xmlns >>>= >>>>'jabber:iq:roster' ><item >>>>jid='osad-441293a7e7@FQDN-censored-address' subscription='both' >>>>/></query></iq> >>>> >>>>--> <iq type='get' id='iq-request-c8a784-9'><query xmlns = >>>>'jabber:iq:roster' /></iq> >>>> >>>><-- <iq >>>>to='rhn-dispatcher-sat@FQDN-censored-address/superclient' >>>>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'><query >xmlns >>>= >>>>'jabber:iq:roster' ><item >>>>jid='osad-bb7d64e5e1@FQDN-censored-address' 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: >>>>https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fspa >>>>c >>>>ewalk-list.redhat.narkive.com%2FaH2kex2k%2Fosa-dispatcher-probl&data= >>>>0 >>>>2%7C01%7CPaschedag.Netlution%40swr.de%7C3d5c9fd1cd104938539a08d4f681c >>>>1 >>>>31%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636404484535256992&sd >>>>a >>>>ta=aM8zI7thgLSKUPLLvdxZbJwHHvzckR8PgrprvHOjkQw%3D&reserved=0 >>>>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://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. >>>redhat.com%2Fmailman%2Flistinfo%2Fspacewalk-list&data=02%7C01%7CPasche >>>d >>>ag.Netlution%40swr.de%7C3d5c9fd1cd104938539a08d4f681c131%7Cbcca095d88d >>>4 >>>42f88260cc216b81f62d%7C0%7C0%7C636404484535256992&sdata=GfER3kuwz5HQDQ >>>D >>>kIaj7KhRfcbTgcQzP520PFxyFEsU%3D&reserved=0 >> >>I'm still on my way to work. >> >>What does /var/log/messages tell? Any error when starting jabberd? >> >>Robert >> >>_______________________________________________ >>Spacewalk-list mailing list >>Spacewalk-list@redhat.com >>https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. >>redhat.com%2Fmailman%2Flistinfo%2Fspacewalk-list&data=02%7C01%7CPasched >>ag.Netlution%40swr.de%7C3d5c9fd1cd104938539a08d4f681c131%7Cbcca095d88d4 >>42f88260cc216b81f62d%7C0%7C0%7C636404484535256992&sdata=GfER3kuwz5HQDQD >>kIaj7KhRfcbTgcQzP520PFxyFEsU%3D&reserved=0 >> >>_______________________________________________ >>Spacewalk-list mailing list >>Spacewalk-list@redhat.com >>https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. >>redhat.com%2Fmailman%2Flistinfo%2Fspacewalk-list&data=02%7C01%7CPasched >>ag.Netlution%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d4 >>42f88260cc216b81f62d%7C0%7C0%7C636407058161574802&sdata=su8t6fTMKDgiVBY >>PQi%2FClb%2F8DG%2F0YCr8CfgqQYtnJZI%3D&reserved=0 >> >>_______________________________________________ >>Spacewalk-list mailing list >>Spacewalk-list@redhat.com >>https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww. >>redhat.com%2Fmailman%2Flistinfo%2Fspacewalk-list&data=02%7C01%7CPasched >>ag.Netlution%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d4 >>42f88260cc216b81f62d%7C0%7C0%7C636407058161574802&sdata=su8t6fTMKDgiVBY >>PQi%2FClb%2F8DG%2F0YCr8CfgqQYtnJZI%3D&reserved=0 > >Hi Andrew, > >Normally, I'm not a friend of just removing something and hoping that a >clean starts helps. > >People often say, stopping jabberd and osa-dispatcher and removing the >jabber database helped them. > >So, as none of your clients to to jabber, only osa-dispatcher seems to >work, I would really try that. > >Stop jabberd and osa-dispatcher >rm /var/lib/jabberd/db/* >Start daemons again. > >All clients *should* re-register to the server if all works again. > >Robert > >_______________________________________________ >Spacewalk-list mailing list >Spacewalk-list@redhat.com >https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.redhat.com%2Fmailman%2Flistinfo%2Fspacewalk-list&data=02%7C01%7CPaschedag.Netlution%40swr.de%7C066e91b3227745d69c5908d4f8d8f846%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636407058161574802&sdata=su8t6fTMKDgiVBYPQi%2FClb%2F8DG%2F0YCr8CfgqQYtnJZI%3D&reserved=0 > >_______________________________________________ >Spacewalk-list mailing list >Spacewalk-list@redhat.com >https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.redhat.com%2Fmailman%2Flistinfo%2Fspacewalk-list&data=02%7C01%7CPaschedag.Netlution%40swr.de%7Cbd28963d73574c9a0b6a08d4f8e3a882%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636407104081258579&sdata=KfIZYUYG6x2MAIZRj33JVwD7H3pXNSrTL9BDrqxj9dA%3D&reserved=0 > >_______________________________________________ >Spacewalk-list mailing list >Spacewalk-list@redhat.com >https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.redhat.com%2Fmailman%2Flistinfo%2Fspacewalk-list&data=02%7C01%7CPaschedag.Netlution%40swr.de%7Cbd28963d73574c9a0b6a08d4f8e3a882%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636407104081258579&sdata=KfIZYUYG6x2MAIZRj33JVwD7H3pXNSrTL9BDrqxj9dA%3D&reserved=0 > >_______________________________________________ >Spacewalk-list mailing list >Spacewalk-list@redhat.com >https://www.redhat.com/mailman/listinfo/spacewalk-list > >_______________________________________________ >Spacewalk-list mailing list >Spacewalk-list@redhat.com >https://www.redhat.com/mailman/listinfo/spacewalk-list
Did I miss something? With what error does osa-dispatcher fail when you setup jabber with the .dist files? Robert _______________________________________________ Spacewalk-list mailing list Spacewalk-list@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-list