Looks like simply you're jabber certificate is broken.
Robert
sent from my mobile device
Originale Nachricht
Von: Larry Clegg
Gesendet: Mon Sep 30 22:33:08 GMT+02:00 2019
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] Problems with OSAD not picking up remote
More research on this issue….I’m finding that on all of my SW 2.9 nodes
running on Centos7 are failing with Jabberd.
● jabberd.service - Jabber Server
Loaded: loaded (/usr/lib/systemd/system/jabberd.service; enabled; vendor
preset: disabled)
Active: active (exited) since Thu 2019-09-12
Greetings Spacers,
My environment:
SW Server: Centos 7 fully patched and Spacewalk 2.9
SW Client: Centos 6 fully patched and Spacewalk Client 2.9 including OSAD
osad-5.11.107-1.el6.noarch
Issue: From the SW server I select several systems and issue a remote
command. Normally OSAD will
on
behalf of Sebastian Meyer me...@b1-systems.de
Sent: Tuesday, August 18, 2015 1:24 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] problems with osad
Hi Daryl,
the check in interval is for rhnsd, not osad. The first is checking in
regularly, minimum interval is 60 minutes. The latter
On 18/08/2015 18:52, Larry E [HDS] Clegg wrote:
All of the problem systems began responding correctly to OSAD requests.
I also updated my clone script to accommodate for this issue. Thank you Thank
you Thank you,
You are welcome! There's a fix from my colleague Michael on the pipeline for
...@hdsupply.com
Sent: Tuesday, August 18, 2015 11:52 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] problems with osad
Thank you Silvio...you identified the issue.we're a heavy VMware shop
with lots of clones and systems built from templates. The templates work
great
, August 18, 2015 11:52 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] problems with osad
Thank you Silvio...you identified the issue.we're a heavy VMware shop with
lots of clones and systems built from templates. The templates work great but
apparently my clone script is missing
of Sebastian Meyer me...@b1-systems.de
Sent: Tuesday, August 18, 2015 1:24 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] problems with osad
Hi Daryl,
the check in interval is for rhnsd, not osad. The first is checking in
regularly, minimum interval is 60 minutes. The latter
On 14/08/2015 18:36, Larry E [HDS] Clegg wrote:
SSLError: ('OpenSSL error; will retry', (-1, 'Unexpected EOF'))
This means that the XMPP connection between client and server got interrupted
from the server side, which leads me to the following hypotheses:
- you have networking problems,
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] problems with osad
No changes to the SW host at all. Out of 253 registered systems only 29 are
showing this issue. So far I have not identified much commonality between
the broken hosts. Most are OL 6.6; some are OL 6.2. And the specific
of the
systems that's no longer connecting?
Dimitri
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Clegg, Larry E [HDS]
Sent: Friday, August 14, 2015 12:36 PM
To: 'spacewalk-list@redhat.com' spacewalk-list@redhat.com
Subject: [Spacewalk-list] problems
Spacewalkers:
My client system is:
Oracle Linux 6.7
[root@gfmpuppetdlps ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.7 (Santiago)
OSAD Version : 5.11.43
My Spacewalk Server is:
Oracle Linux 6.6
Spacewalk 2.2
I'm encountering this problem with OSAD. Some of my
...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Clegg, Larry E [HDS]
Sent: Friday, August 14, 2015 1:42 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] problems with osad
No changes to the SW host at all. Out of 253 registered systems only 29 are
showing this issue
, 'Unexpected EOF'))
From: spacewalk-list-boun...@redhat.com
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Dimitri Yioulos
Sent: Friday, August 14, 2015 10:16 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] problems with osad
Have you made any changes to Spacewalk (e.g
I have recently upgraded to spacewalk 1.2 from 1.1.
When I try to schedule a remote command, I get an internal server error:
500 Error - Internal Server Error
You may have reached this page in one of the following ways:
1. You've found an error in the site. Please report this error to
your
On Thu, Dec 09, 2010 at 12:14:16PM -0600, Trent Johnson wrote:
I have recently upgraded to spacewalk 1.2 from 1.1.
When I try to schedule a remote command, I get an internal server error:
500 Error - Internal Server Error
If you get Internal Server Error on the WebUI, it's not
osad/jabberd
Hi guys,
I am having some problemas with osad.
osa-dispatcher and jabberd are running fine on my spacewalk server:
# ps -ef | egrep c2s|s2s|sm|router | grep -i jabber
jabber 10812 1 0 12:36 ?00:00:00 /usr/bin/router -c
/etc/jabberd/router.xml
jabber 10842 1 0 12:36 ?
Edit /etc/sysconfig/rhn/osad.conf and change the debug level to 6, maybe
that'll give you some more info about why osad isn't connecting.
Also, is everything on your Spacewalk server configured to use the FQDN,
including the hostname, RHN-ORG-TRUSTED-SSL-CERT, et al.? Jabber is
extremely picky.
18 matches
Mail list logo