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

Andrew Bergman Andrew.Bergman at bom.gov.au
Mon Sep 11 00:10:55 UTC 2017


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-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Paschedag, Robert
Sent: Friday, 8 September 2017 5:44 PM
To: spacewalk-list at 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 at FQDN-censored-address/superclient'
>>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'><query xmlns
>=

And later set to another id

>>to='rhn-dispatcher-sat at 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-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] Im Auftrag von Andrew Bergman
Gesendet: Freitag, 8. September 2017 08:08
An: spacewalk-list at 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 at 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 at 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 at 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 at 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.paschedag at web.de]
Sent: Friday, 8 September 2017 4:03 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 07:56:07 MESZ schrieb Andrew Bergman <Andrew.Bergman at 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.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 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 at FQDN-censored-address'
>>subscription='to'
>>/><item jid='osad-441293a7e7 at FQDN-censored-address'
>>subscription='to' /></query></iq>
>>
>><-- <iq
>>to='rhn-dispatcher-sat at FQDN-censored-address/superclient'
>>type='set' id='zb6g3gnj6oylakzw0ntgapdin3tlgajgmqwq6j9c'><query xmlns
>=
>>'jabber:iq:roster' ><item
>>jid='osad-441293a7e7 at 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 at FQDN-censored-address/superclient'
>>type='set' id='78xisxfsl88wymemq876irn4hjvn340bcyt5w8xh'><query xmlns
>=
>>'jabber:iq:roster' ><item
>>jid='osad-bb7d64e5e1 at 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%2Fspac
>>ewalk-list.redhat.narkive.com%2FaH2kex2k%2Fosa-dispatcher-probl&data=0
>>2%7C01%7CPaschedag.Netlution%40swr.de%7C3d5c9fd1cd104938539a08d4f681c1
>>31%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636404484535256992&sda
>>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 at 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

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 at 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%7C3d5c9fd1cd104938539a08d4f681c131%7Cbcca095d88d442f88260cc216b81f62d%7C0%7C0%7C636404484535256992&sdata=GfER3kuwz5HQDQDkIaj7KhRfcbTgcQzP520PFxyFEsU%3D&reserved=0

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list




More information about the Spacewalk-list mailing list