v6 ::1 entry for
localhost, fully qualified hostname and the system hostname set to FQDN
correctly.
Does anyone have any suggestions?
Thanks
Andrew Bergman
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list
fcs/rfc3921.html#JEP-0077>, published by the
Jabber Software Foundation<https://xmpp.org/rfcs/rfc3921.html#JSF> [JSF].
Have I possibly hit a bug here in osa-dispatcher or jabber?
Regards
Andrew Bergman
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat
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&q
error stanza:
>', />)
>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 t
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
rds
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=UNCLAS
s the 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 Be
[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
:
>Yes, I did an
rd-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 cens
Ds 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-bou
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)?
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 "con
Dispatcher "conflict" error [SEC=UNCLASSIFIED]
Hmma 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: Mo
t 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
to production, it has been configured with all the addresses
for its spacewalk install as the production hostname. So two osa-dispatchers
have been talking to the production spacewalk jabber!!!
Unbelievable.
Shut down the PoC and all is well again.
Cheers
Andrew Bergman
-Original Message
them to a RHEL6 group. But when I click on the > and >> buttons
nothing happens.
[cid:image001.jpg@01D32CB3.8D9867E0]
Anyone seen this before?
Cheers
Andrew Bergman
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.co
Hi List,
We have a Channel structure whereby we have a Parent channel, say
centos7-x86_64, which contains no packages or errata but within it has child
channels such as centos7-updates-x86_64. We also have cloned frozen channels
of these childs within the parent channels so that we can easily
Run osa-dispatcher from the command line:
osa-dispatcher -N –vvv
What do you get?
Each v represents 1 debug setting. So put maybe 10 in.
Regards
Andrew Bergman
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Jonathan Payne
Sent
Also, what is in the /var/log/messages logs pertaining to jabber?
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Jonathan Payne
Sent: Tuesday, 19 September 2017 6:22 AM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] osa-dispatcher dies sho
19 matches
Mail list logo