subject:"Re\: \[Spacewalk\-list\] problems with osad"

Re: [Spacewalk-list] Problems with OSAD not picking up remote commands

2019-09-30 Thread Robert Paschedag

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  commands

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 20:16:19 UTC; 2 weeks 4
days ago

  Process: 19180 ExecStart=/bin/true (code=exited, status=0/SUCCESS)

Main PID: 19180 (code=exited, status=0/SUCCESS)

   CGroup: /system.slice/jabberd.service



Checking the /var/log/rhn/osa-dispatcher.log I see this:



2019/09/30 20:32:22 -00:00 14849 0.0.0.0: osad/jabber_lib.main('ERROR',
'Error caught:')

2019/09/30 20:32:22 -00:00 14849 0.0.0.0: osad/jabber_lib.main('ERROR',
'Traceback (most recent call last):¥n  File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 126, in
main¥nself.process_forever(c)¥n  File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 187, in
process_forever¥nself.process_once(client)¥n  File
"/usr/lib/python2.7/site-packages/osad/osa_dispatcher.py", line 182, in
process_once¥nclient.retrieve_roster()¥n  File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 757, in
retrieve_roster¥nstanza = self.get_one_stanza()¥n  File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 829, in
get_one_stanza¥nself.process(timeout=tm)¥n  File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 1100, in
process¥nraise_with_tb(SSLError("OpenSSL error; will retry", str(e)),
sys.exc_info()[2])¥n  File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 1095, in
process¥ndata = self._read(self.BLOCK_SIZE)¥nSSLError: (¥'OpenSSL
error; will retry¥', "(-1, ¥'Unexpected EOF¥')")¥n')



*Larry E. Clegg*

Systems Engineer (SaaS Platform Operations) | *Kyriba*

[Cell Phone] +1 858-357-5579

[Address] 9620 Towne Centre Drive | Suite 250 | San Diego, California |
92121

www.kyriba.com | Facebook <https://www.facebook.com/KyribaCorp> | Twitter
<https://twitter.com/kyribacorp> | LinkedIn
<http://www.linkedin.com/company/kyriba-corporation> | Blog
<http://www.kyriba.com/blog>



*From:* Larry Clegg [mailto:lcl...@kyriba.com]
*Sent:* Monday, September 30, 2019 11:42 AM
*To:* 'spacewalk-list@redhat.com' 
*Subject:* Problems with OSAD not picking up remote commands



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 pick up the remote command within seconds.
Now it is not picking it up for many minutes….even after a normal system
check-in the remote command is still not picked up.  I can login to the
client system and issue a rhn_check – and see it pick up the remote
command and return the output.Service osad is running; restarting makes
no difference.



On the SW server:

jabberpy-0.5-0.27.el7.noarch

spacewalk-setup-jabberd-2.9.2-1.el7.noarch

jabberd-2.6.1-1.el7.x86_64

osa-dispatcher-selinux-5.11.107-1.el7.noarch

python2-osa-common-5.11.107-1.el7.noarch

osa-dispatcher-5.11.107-1.el7.noarch

python2-osa-dispatcher-5.11.107-1.el7.noarch



Port 5222 is open with established connections.  I find no errors in any
logs.

I’m at a loss as to where to look now….any guidance would be appreciated.



Regards,



*Larry E. Clegg*

Systems Engineer (SaaS Platform Operations) | *Kyriba*

[Cell Phone] +1 858-357-5579

[Address] 9620 Towne Centre Drive | Suite 250 | San Diego, California |
92121

www.kyriba.com | Facebook <https://www.facebook.com/KyribaCorp> | Twitter
<https://twitter.com/kyribacorp> | LinkedIn
<http://www.linkedin.com/company/kyriba-corporation> | Blog
<http://www.kyriba.com/blog>




___
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

Re: [Spacewalk-list] Problems with OSAD not picking up remote commands

2019-09-30 Thread Larry Clegg

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 20:16:19 UTC; 2 weeks 4
days ago

  Process: 19180 ExecStart=/bin/true (code=exited, status=0/SUCCESS)

Main PID: 19180 (code=exited, status=0/SUCCESS)

   CGroup: /system.slice/jabberd.service



Checking the /var/log/rhn/osa-dispatcher.log I see this:



2019/09/30 20:32:22 -00:00 14849 0.0.0.0: osad/jabber_lib.main('ERROR',
'Error caught:')

2019/09/30 20:32:22 -00:00 14849 0.0.0.0: osad/jabber_lib.main('ERROR',
'Traceback (most recent call last):¥n  File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 126, in
main¥nself.process_forever(c)¥n  File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 187, in
process_forever¥nself.process_once(client)¥n  File
"/usr/lib/python2.7/site-packages/osad/osa_dispatcher.py", line 182, in
process_once¥nclient.retrieve_roster()¥n  File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 757, in
retrieve_roster¥nstanza = self.get_one_stanza()¥n  File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 829, in
get_one_stanza¥nself.process(timeout=tm)¥n  File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 1100, in
process¥nraise_with_tb(SSLError("OpenSSL error; will retry", str(e)),
sys.exc_info()[2])¥n  File
"/usr/lib/python2.7/site-packages/osad/jabber_lib.py", line 1095, in
process¥ndata = self._read(self.BLOCK_SIZE)¥nSSLError: (¥'OpenSSL
error; will retry¥', "(-1, ¥'Unexpected EOF¥')")¥n')



*Larry E. Clegg*

Systems Engineer (SaaS Platform Operations) | *Kyriba*

[Cell Phone] +1 858-357-5579

[Address] 9620 Towne Centre Drive | Suite 250 | San Diego, California |
92121

www.kyriba.com | Facebook  | Twitter
 | LinkedIn
 | Blog




*From:* Larry Clegg [mailto:lcl...@kyriba.com]
*Sent:* Monday, September 30, 2019 11:42 AM
*To:* 'spacewalk-list@redhat.com' 
*Subject:* Problems with OSAD not picking up remote commands



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 pick up the remote command within seconds.
Now it is not picking it up for many minutes….even after a normal system
check-in the remote command is still not picked up.  I can login to the
client system and issue a rhn_check – and see it pick up the remote
command and return the output.Service osad is running; restarting makes
no difference.



On the SW server:

jabberpy-0.5-0.27.el7.noarch

spacewalk-setup-jabberd-2.9.2-1.el7.noarch

jabberd-2.6.1-1.el7.x86_64

osa-dispatcher-selinux-5.11.107-1.el7.noarch

python2-osa-common-5.11.107-1.el7.noarch

osa-dispatcher-5.11.107-1.el7.noarch

python2-osa-dispatcher-5.11.107-1.el7.noarch



Port 5222 is open with established connections.  I find no errors in any
logs.

I’m at a loss as to where to look now….any guidance would be appreciated.



Regards,



*Larry E. Clegg*

Systems Engineer (SaaS Platform Operations) | *Kyriba*

[Cell Phone] +1 858-357-5579

[Address] 9620 Towne Centre Drive | Suite 250 | San Diego, California |
92121

www.kyriba.com | Facebook  | Twitter
 | LinkedIn
 | Blog

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] problems with osad

2015-08-19 Thread Daryl Rose

I decided to revert my two clients back to initial install (I love VM :) )  I 
recreated the certificate on the spacewalk server and re-registered both 
clients.  All is now good.  I am now scheduling updates, and osad is picking 
them up and patching my systems.

Thank you to everyone who replied and gave me assistance.

Daryl

From: spacewalk-list-boun...@redhat.com  on 
behalf of Daryl Rose 
Sent: Tuesday, August 18, 2015 2:04 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] problems with osad

Firewall is not running on any of my demo/test servers.  One of the first 
things that I do when building a new server is shutdown, and disable iptables.  
I verified just to make sure before I posted this reply.

>From the documentation that I read, the osad is supposed to use the same cert 
>that is defied in the up2date file, unless I need a different one, then I 
>would configure osad.conf to point to that cert.

As I was typing this reply, I decided to test using rhn_check again.  This 
time, I received an error telling me there were SSL errors.  Certificate verify 
failed.  So, perhaps I am still having certificate errors and perhaps when I 
ran the rhn_check previously it was just a fluke.

I'll do some more digging and post back.

Thank you.

Daryl

From: spacewalk-list-boun...@redhat.com  on 
behalf of Sebastian Meyer 
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 is for instant
communication between server and clients.

So you schedule an action, the clients get notified via
osa-dispatcher/osad that there are new events.

You renewed your certificate, did you also replace the one
osa-dispatcher is using? If you have build an rpm for the certificate
that should have taken care of that, otherwise you might need to switch
the osa-dispatcher certificate for the new one..

On your spacewalk server, are the jabber services and osa-dispatcher
running? -> check with 'spacewalk-service status'

On the firewall, are the necessary ports open? See
https://fedorahosted.org/spacewalk/wiki/HowToInstall for the
ports/directions they have to be open

Regards
Sebastian

On 18.08.2015 20:10, Daryl Rose wrote:
> Larry,
>
> I hope that you don't mind me piggybacking on to your posting, but I'm 
> dealing with osad issue myself and instead of starting a new thread, I 
> thought that I would hijack yours. :)
>
> Anyway, I've been working on a Proof-of-Concept  Spacewalk environment.  I've 
> finally worked through all of my previous issues and the last hurdle to jump 
> over is OSAD.
>
> The original issue that I had was the osa-dispatcher not starting.  I finally 
> found a posting online that stopped the jabber and osa-dispatcher, remove the 
> jabber db files and restart jabber, followed by osa-dispatcher.  Dispatcher 
> finally started, and stayed running.
>
> Next I adjusted the interval for osad to check in.  The default was 240, but 
> I changed it to 60 minutes, so the updates will get picked up quicker.  I 
> don't want to wait for four hours to see if things work or not.
>
> After two hours, the updates had not been picked up. I read this posting and 
> tried running the osad command manually:
> osad -N -v -v -v -v as.  I get "Unable to connect to jabber servers, sleeping 
> 114 seconds".
>
> I tried what you used to resolve your issue Larry:
> 1) service osad stop
> 2) /bin/rm /etc/sysconfig/rhn/osad-auth.conf
> 3) service osad start
>
> But that did not resolve my issue.
>
> Just to let everyone know, I did recently change the certificate on the 
> server and re-registered my clients.  The original certificate did not 
> contain the FQDN of the server and the SLES 11 client would not work unless I 
> recreated the certificate.  I unregistered both of my test clients, RHEL 6.x 
> and SLES 11, and re-registered both of them using the latest certificate.  I 
> can update both environments using the rhn_check -vv, so I'm assuming that 
> the certificate is working just fine.  And yes, the FQDN in the certificate 
> matched the FQDN in the up2date config file.
>
> What else should I check, or tweak in order to get osad working?
>
> Thanks
>
> Daryl
> ________________
> From: spacewalk-list-boun...@redhat.com  
> on behalf of Clegg, Larry E [HDS] 
> 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 clo

Re: [Spacewalk-list] problems with osad

2015-08-19 Thread Silvio Moioli


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 
the next Spacewalk version as well:

https://github.com/spacewalkproject/spacewalk/pull/272

So starting from Spacewalk 2.4 (or Nightly, or SUSE Manager :-) this will be 
detected and fixed automatically.

Have a great day,
--
Silvio Moioli
SUSE Manager Development Team

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] problems with osad

2015-08-19 Thread Silvio Moioli


On 18/08/2015 20:10, Daryl Rose wrote:

  I finally found a posting online that stopped the jabber and osa-dispatcher, 
remove the jabber db files and restart jabber, followed by osa-dispatcher.  
Dispatcher finally started, and stayed running.


[...]


After two hours, the updates had not been picked up.


Make sure all jabberd processes are up and running, and they can be contacted 
on the appropriate port (you could use nmap to check that). It could be an 
issue that I fixed in Jabberd some time ago:

https://github.com/jabberd2/jabberd2/pull/99

but that would be healed by another deletion of the jabberd database as well.

I thus suspect networking problems here, and would go analyzing traffic with 
Wireshark as explained in a previous message.

Hth,
--
Silvio Moioli
SUSE Manager Development Team

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] problems with osad

2015-08-18 Thread Daryl Rose

Firewall is not running on any of my demo/test servers.  One of the first 
things that I do when building a new server is shutdown, and disable iptables.  
I verified just to make sure before I posted this reply.

>From the documentation that I read, the osad is supposed to use the same cert 
>that is defied in the up2date file, unless I need a different one, then I 
>would configure osad.conf to point to that cert.  

As I was typing this reply, I decided to test using rhn_check again.  This 
time, I received an error telling me there were SSL errors.  Certificate verify 
failed.  So, perhaps I am still having certificate errors and perhaps when I 
ran the rhn_check previously it was just a fluke. 

I'll do some more digging and post back.

Thank you.

Daryl


From: spacewalk-list-boun...@redhat.com  on 
behalf of Sebastian Meyer 
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 is for instant
communication between server and clients.

So you schedule an action, the clients get notified via
osa-dispatcher/osad that there are new events.

You renewed your certificate, did you also replace the one
osa-dispatcher is using? If you have build an rpm for the certificate
that should have taken care of that, otherwise you might need to switch
the osa-dispatcher certificate for the new one..

On your spacewalk server, are the jabber services and osa-dispatcher
running? -> check with 'spacewalk-service status'

On the firewall, are the necessary ports open? See
https://fedorahosted.org/spacewalk/wiki/HowToInstall for the
ports/directions they have to be open

Regards
Sebastian

On 18.08.2015 20:10, Daryl Rose wrote:
> Larry,
>
> I hope that you don't mind me piggybacking on to your posting, but I'm 
> dealing with osad issue myself and instead of starting a new thread, I 
> thought that I would hijack yours. :)
>
> Anyway, I've been working on a Proof-of-Concept  Spacewalk environment.  I've 
> finally worked through all of my previous issues and the last hurdle to jump 
> over is OSAD.
>
> The original issue that I had was the osa-dispatcher not starting.  I finally 
> found a posting online that stopped the jabber and osa-dispatcher, remove the 
> jabber db files and restart jabber, followed by osa-dispatcher.  Dispatcher 
> finally started, and stayed running.
>
> Next I adjusted the interval for osad to check in.  The default was 240, but 
> I changed it to 60 minutes, so the updates will get picked up quicker.  I 
> don't want to wait for four hours to see if things work or not.
>
> After two hours, the updates had not been picked up. I read this posting and 
> tried running the osad command manually:
> osad -N -v -v -v -v as.  I get "Unable to connect to jabber servers, sleeping 
> 114 seconds".
>
> I tried what you used to resolve your issue Larry:
> 1) service osad stop
> 2) /bin/rm /etc/sysconfig/rhn/osad-auth.conf
> 3) service osad start
>
> But that did not resolve my issue.
>
> Just to let everyone know, I did recently change the certificate on the 
> server and re-registered my clients.  The original certificate did not 
> contain the FQDN of the server and the SLES 11 client would not work unless I 
> recreated the certificate.  I unregistered both of my test clients, RHEL 6.x 
> and SLES 11, and re-registered both of them using the latest certificate.  I 
> can update both environments using the rhn_check -vv, so I'm assuming that 
> the certificate is working just fine.  And yes, the FQDN in the certificate 
> matched the FQDN in the up2date config file.
>
> What else should I check, or tweak in order to get osad working?
>
> Thanks
>
> Daryl
> ________________
> From: spacewalk-list-boun...@redhat.com  
> on behalf of Clegg, Larry E [HDS] 
> 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 but apparently my clone script is missing the removal of the 
> osad-auth.conf file.
>
> I did these three steps on all the problem systems:
> 1) service osad stop
> 2) /bin/rm /etc/sysconfig/rhn/osad-auth.conf
> 3) service osad start
>
> 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,
>
> Larry
>
> -Original

Re: [Spacewalk-list] problems with osad

2015-08-18 Thread Sebastian Meyer

Hi Daryl,

the check in interval is for rhnsd, not osad. The first is checking in
regularly, minimum interval is 60 minutes. The latter is for instant
communication between server and clients.

So you schedule an action, the clients get notified via
osa-dispatcher/osad that there are new events.

You renewed your certificate, did you also replace the one
osa-dispatcher is using? If you have build an rpm for the certificate
that should have taken care of that, otherwise you might need to switch
the osa-dispatcher certificate for the new one..

On your spacewalk server, are the jabber services and osa-dispatcher
running? -> check with 'spacewalk-service status'

On the firewall, are the necessary ports open? See
https://fedorahosted.org/spacewalk/wiki/HowToInstall for the
ports/directions they have to be open

Regards
Sebastian

On 18.08.2015 20:10, Daryl Rose wrote:
> Larry,
> 
> I hope that you don't mind me piggybacking on to your posting, but I'm 
> dealing with osad issue myself and instead of starting a new thread, I 
> thought that I would hijack yours. :)
> 
> Anyway, I've been working on a Proof-of-Concept  Spacewalk environment.  I've 
> finally worked through all of my previous issues and the last hurdle to jump 
> over is OSAD.   
> 
> The original issue that I had was the osa-dispatcher not starting.  I finally 
> found a posting online that stopped the jabber and osa-dispatcher, remove the 
> jabber db files and restart jabber, followed by osa-dispatcher.  Dispatcher 
> finally started, and stayed running.
> 
> Next I adjusted the interval for osad to check in.  The default was 240, but 
> I changed it to 60 minutes, so the updates will get picked up quicker.  I 
> don't want to wait for four hours to see if things work or not.
> 
> After two hours, the updates had not been picked up. I read this posting and 
> tried running the osad command manually:
> osad -N -v -v -v -v as.  I get "Unable to connect to jabber servers, sleeping 
> 114 seconds".  
> 
> I tried what you used to resolve your issue Larry:
> 1) service osad stop
> 2) /bin/rm /etc/sysconfig/rhn/osad-auth.conf
> 3) service osad start
> 
> But that did not resolve my issue.
> 
> Just to let everyone know, I did recently change the certificate on the 
> server and re-registered my clients.  The original certificate did not 
> contain the FQDN of the server and the SLES 11 client would not work unless I 
> recreated the certificate.  I unregistered both of my test clients, RHEL 6.x 
> and SLES 11, and re-registered both of them using the latest certificate.  I 
> can update both environments using the rhn_check -vv, so I'm assuming that 
> the certificate is working just fine.  And yes, the FQDN in the certificate 
> matched the FQDN in the up2date config file.
> 
> What else should I check, or tweak in order to get osad working?
> 
> Thanks
> 
> Daryl
> ____________
> From: spacewalk-list-boun...@redhat.com  
> on behalf of Clegg, Larry E [HDS] 
> 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 but apparently my clone script is missing the removal of the 
> osad-auth.conf file.
> 
> I did these three steps on all the problem systems:
> 1) service osad stop
> 2) /bin/rm /etc/sysconfig/rhn/osad-auth.conf
> 3) service osad start
> 
> 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,
> 
> Larry
> 
> -Original Message-
> From: spacewalk-list-boun...@redhat.com 
> [mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Silvio Moioli
> Sent: Sunday, August 16, 2015 11:26 PM
> To: spacewalk-list@redhat.com
> Subject: Re: [Spacewalk-list] problems with osad
> 
> 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, like dropped packets, which broke the 
> connection;
>   - server has interrupted the connection because two clients have the same 
> OSAD auth credentials (identical osad-auth.conf files across different 
> hosts). This can happen if some clients are cloned virtual machines, cure is 
> simply to delete those files and they will be automatica

Re: [Spacewalk-list] problems with osad

2015-08-18 Thread Clegg, Larry E [HDS]

OSAD should pick things up fairly immediately.  Without OSAD you do have to 
wait for the RHNSD agent to wake up every 4 hours (default) to ask the 
Spacewalk server if it has any tasks for it.

Is there a firewall in the way?  Or iptables?  OSAD communicates over port 5222 
and if that isn't open then you'll not be successful.


-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Daryl Rose
Sent: Tuesday, August 18, 2015 11:11 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] problems with osad

Larry,

I hope that you don't mind me piggybacking on to your posting, but I'm dealing 
with osad issue myself and instead of starting a new thread, I thought that I 
would hijack yours. :)


Anyway, I've been working on a Proof-of-Concept  Spacewalk environment.  I've 
finally worked through all of my previous issues and the last hurdle to jump 
over is OSAD.   

The original issue that I had was the osa-dispatcher not starting.  I finally 
found a posting online that stopped the jabber and osa-dispatcher, remove the 
jabber db files and restart jabber, followed by osa-dispatcher.  Dispatcher 
finally started, and stayed running.

Next I adjusted the interval for osad to check in.  The default was 240, but I 
changed it to 60 minutes, so the updates will get picked up quicker.  I don't 
want to wait for four hours to see if things work or not.

After two hours, the updates had not been picked up. I read this posting and 
tried running the osad command manually:
osad -N -v -v -v -v as.  I get "Unable to connect to jabber servers, sleeping 
114 seconds".  

I tried what you used to resolve your issue Larry:
1) service osad stop
2) /bin/rm /etc/sysconfig/rhn/osad-auth.conf
3) service osad start

But that did not resolve my issue.

Just to let everyone know, I did recently change the certificate on the server 
and re-registered my clients.  The original certificate did not contain the 
FQDN of the server and the SLES 11 client would not work unless I recreated the 
certificate.  I unregistered both of my test clients, RHEL 6.x and SLES 11, and 
re-registered both of them using the latest certificate.  I can update both 
environments using the rhn_check -vv, so I'm assuming that the certificate is 
working just fine.  And yes, the FQDN in the certificate matched the FQDN in 
the up2date config file.

What else should I check, or tweak in order to get osad working?

Thanks

Daryl

From: spacewalk-list-boun...@redhat.com  on 
behalf of Clegg, Larry E [HDS] 
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 but 
apparently my clone script is missing the removal of the osad-auth.conf file.

I did these three steps on all the problem systems:
1) service osad stop
2) /bin/rm /etc/sysconfig/rhn/osad-auth.conf
3) service osad start

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,

Larry

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Silvio Moioli
Sent: Sunday, August 16, 2015 11:26 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] problems with osad

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, like dropped packets, which broke the 
connection;
  - server has interrupted the connection because two clients have the same 
OSAD auth credentials (identical osad-auth.conf files across different hosts). 
This can happen if some clients are cloned virtual machines, cure is simply to 
delete those files and they will be automatically regenerated;
  - client tools version is badly outdated.

After checking the above I would recommend a Wireshark capture to figure out 
what went wrong. At least you should be able to see if there are networking 
issues or not. Here are instructions and commands for SUSE Manager on SLES:

https://urldefense.proofpoint.com/v2/url?u=http-3A__wiki.novell.com_index.php_SUSE-5FManager_XMPPDumping&d=BQIF-g&c=_8VcuiJ--MukFqz6Sy5gel64o52_IbhiNdatg8Zb5Gs&r=b7IEz3ofaK6POXcDGRHJcwu-GqbKHox-4tfx-bQLxLo&m=GYrj7GE9nD2eN90AdDoTRjarEsgB39EugzpSnrXHIjA&s=JIrQMKoWUoDQ3Fn8jd_0pf4ZJKHZJ2TSrAdc8vLOxtw&e=

In your setup instructions are still valid, while commands need a little 
tweaking.

Hth,
--
Silvio Moioli

Re: [Spacewalk-list] problems with osad

2015-08-18 Thread Daryl Rose

Larry,

I hope that you don't mind me piggybacking on to your posting, but I'm dealing 
with osad issue myself and instead of starting a new thread, I thought that I 
would hijack yours. :)

Anyway, I've been working on a Proof-of-Concept  Spacewalk environment.  I've 
finally worked through all of my previous issues and the last hurdle to jump 
over is OSAD.   

The original issue that I had was the osa-dispatcher not starting.  I finally 
found a posting online that stopped the jabber and osa-dispatcher, remove the 
jabber db files and restart jabber, followed by osa-dispatcher.  Dispatcher 
finally started, and stayed running.

Next I adjusted the interval for osad to check in.  The default was 240, but I 
changed it to 60 minutes, so the updates will get picked up quicker.  I don't 
want to wait for four hours to see if things work or not.

After two hours, the updates had not been picked up. I read this posting and 
tried running the osad command manually:
osad -N -v -v -v -v as.  I get "Unable to connect to jabber servers, sleeping 
114 seconds".  

I tried what you used to resolve your issue Larry:
1) service osad stop
2) /bin/rm /etc/sysconfig/rhn/osad-auth.conf
3) service osad start

But that did not resolve my issue.

Just to let everyone know, I did recently change the certificate on the server 
and re-registered my clients.  The original certificate did not contain the 
FQDN of the server and the SLES 11 client would not work unless I recreated the 
certificate.  I unregistered both of my test clients, RHEL 6.x and SLES 11, and 
re-registered both of them using the latest certificate.  I can update both 
environments using the rhn_check -vv, so I'm assuming that the certificate is 
working just fine.  And yes, the FQDN in the certificate matched the FQDN in 
the up2date config file.

What else should I check, or tweak in order to get osad working?

Thanks

Daryl

From: spacewalk-list-boun...@redhat.com  on 
behalf of Clegg, Larry E [HDS] 
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 but 
apparently my clone script is missing the removal of the osad-auth.conf file.

I did these three steps on all the problem systems:
1) service osad stop
2) /bin/rm /etc/sysconfig/rhn/osad-auth.conf
3) service osad start

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,

Larry

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Silvio Moioli
Sent: Sunday, August 16, 2015 11:26 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] problems with osad

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, like dropped packets, which broke the 
connection;
  - server has interrupted the connection because two clients have the same 
OSAD auth credentials (identical osad-auth.conf files across different hosts). 
This can happen if some clients are cloned virtual machines, cure is simply to 
delete those files and they will be automatically regenerated;
  - client tools version is badly outdated.

After checking the above I would recommend a Wireshark capture to figure out 
what went wrong. At least you should be able to see if there are networking 
issues or not. Here are instructions and commands for SUSE Manager on SLES:

https://urldefense.proofpoint.com/v2/url?u=http-3A__wiki.novell.com_index.php_SUSE-5FManager_XMPPDumping&d=BQIF-g&c=_8VcuiJ--MukFqz6Sy5gel64o52_IbhiNdatg8Zb5Gs&r=b7IEz3ofaK6POXcDGRHJcwu-GqbKHox-4tfx-bQLxLo&m=GYrj7GE9nD2eN90AdDoTRjarEsgB39EugzpSnrXHIjA&s=JIrQMKoWUoDQ3Fn8jd_0pf4ZJKHZJ2TSrAdc8vLOxtw&e=

In your setup instructions are still valid, while commands need a little 
tweaking.

Hth,
--
Silvio Moioli
SUSE LLC
Maxfeldstraße 5, 90409 Nürnberg Germany

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com_mailman_listinfo_spacewalk-2Dlist&d=BQIF-g&c=_8VcuiJ--MukFqz6Sy5gel64o52_IbhiNdatg8Zb5Gs&r=b7IEz3ofaK6POXcDGRHJcwu-GqbKHox-4tfx-bQLxLo&m=GYrj7GE9nD2eN90AdDoTRjarEsgB39EugzpSnrXHIjA&s=i4ObyA0JwB0e4M4t4fv1f6qA5LegFDsSUGU5ql2LN38&e=

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.c

Re: [Spacewalk-list] problems with osad

2015-08-18 Thread Clegg, Larry E [HDS]

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 the removal of the osad-auth.conf file. 

I did these three steps on all the problem systems:
1) service osad stop
2) /bin/rm /etc/sysconfig/rhn/osad-auth.conf
3) service osad start

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,

Larry

-Original Message-
From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Silvio Moioli
Sent: Sunday, August 16, 2015 11:26 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] problems with osad

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, like dropped packets, which broke the 
connection;
  - server has interrupted the connection because two clients have the same 
OSAD auth credentials (identical osad-auth.conf files across different hosts). 
This can happen if some clients are cloned virtual machines, cure is simply to 
delete those files and they will be automatically regenerated;
  - client tools version is badly outdated.

After checking the above I would recommend a Wireshark capture to figure out 
what went wrong. At least you should be able to see if there are networking 
issues or not. Here are instructions and commands for SUSE Manager on SLES:

https://urldefense.proofpoint.com/v2/url?u=http-3A__wiki.novell.com_index.php_SUSE-5FManager_XMPPDumping&d=BQIF-g&c=_8VcuiJ--MukFqz6Sy5gel64o52_IbhiNdatg8Zb5Gs&r=b7IEz3ofaK6POXcDGRHJcwu-GqbKHox-4tfx-bQLxLo&m=GYrj7GE9nD2eN90AdDoTRjarEsgB39EugzpSnrXHIjA&s=JIrQMKoWUoDQ3Fn8jd_0pf4ZJKHZJ2TSrAdc8vLOxtw&e=
 

In your setup instructions are still valid, while commands need a little 
tweaking.

Hth,
-- 
Silvio Moioli
SUSE LLC
Maxfeldstraße 5, 90409 Nürnberg Germany

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://urldefense.proofpoint.com/v2/url?u=https-3A__www.redhat.com_mailman_listinfo_spacewalk-2Dlist&d=BQIF-g&c=_8VcuiJ--MukFqz6Sy5gel64o52_IbhiNdatg8Zb5Gs&r=b7IEz3ofaK6POXcDGRHJcwu-GqbKHox-4tfx-bQLxLo&m=GYrj7GE9nD2eN90AdDoTRjarEsgB39EugzpSnrXHIjA&s=i4ObyA0JwB0e4M4t4fv1f6qA5LegFDsSUGU5ql2LN38&e=
 

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] problems with osad

2015-08-16 Thread Silvio Moioli


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, like dropped packets, which broke the 
connection;
 - server has interrupted the connection because two clients have the same OSAD 
auth credentials (identical osad-auth.conf files across different hosts). This 
can happen if some clients are cloned virtual machines, cure is simply to 
delete those files and they will be automatically regenerated;
 - client tools version is badly outdated.

After checking the above I would recommend a Wireshark capture to figure out 
what went wrong. At least you should be able to see if there are networking 
issues or not. Here are instructions and commands for SUSE Manager on SLES:

http://wiki.novell.com/index.php/SUSE_Manager/XMPPDumping

In your setup instructions are still valid, while commands need a little 
tweaking.

Hth,
--
Silvio Moioli
SUSE LLC
Maxfeldstraße 5, 90409 Nürnberg Germany

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] problems with osad

2015-08-14 Thread Paul Robert Marino

you may need to clean out the database for jabber anb restart it and osad


On Fri, Aug 14, 2015 at 2:05 PM, Dimitri Yioulos
 wrote:
> I’ve experienced the same issue on some of my clients.  I had to re-register
> those clients, then thing were all good.  I’m not necessarily saying that
> the same will work for you, but you might want to try re-registering one
> client to see what happens.
>
>
>
> 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 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.  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
> kernel varies within the release range.
>
>
>
> I’ve tested using /usr/sbin/osad -N -v -v -v –von several of the other
> clients.  The results are the same with them all ending up at this point:
>
>
>
> Error caught:
>
> Traceback (most recent call last):
>
>   File "/usr/share/rhn/osad/jabber_lib.py", line 121, in main
>
> self.process_forever(c)
>
>   File "/usr/share/rhn/osad/jabber_lib.py", line 179, in process_forever
>
> self.process_once(client)
>
>   File "/usr/share/rhn/osad/osad.py", line 250, in process_once
>
> client.process(timeout=180)
>
>   File "/usr/share/rhn/osad/jabber_lib.py", line 1055, in process
>
> data = self._read(self.BLOCK_SIZE)
>
> SSLError: ('OpenSSL error; will retry', "(-1, '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. upgrade) or to the Spacewalk
> host?  Made a change to the Spacewalk SSL cert?  Does “serverURL” in
> /etc/sysconfig/rhn/up2date match the Common Name in the certificate you
> created for your Spacewalk environment?  Have you tried re-registering one
> 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' 
> Subject: [Spacewalk-list] problems with osad
>
>
>
> 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 systems are no longer
> responding to OSAD requests.
>
>
>
> I run OSAD in the foreground as a test and I get this…it is communicating
> with the SW node but then reliably errors out.  The pattern repeats
> endlessly….
>
>
>
> /usr/sbin/osad -N -v -v -v –v   as
>
>
>
> ……
>
> 2015-08-14 12:30:41 jabber_lib._presence_callback: Node is available
> rhn-dispatcher-...@gfmswalk1lps.hsi.hughessupply.com/superclient None
>
> 2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed to
> {'rhn-dispatcher-...@gfmswalk1lps.hsi.hughessupply.com': {'jid':
> 'rhn-dispatcher-...@gfmswalk1lps.hsi.hughessupply.com', 'subscription':
> u'to'}}
>
> 2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed both {}
>
> 2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed none {}
>
> 2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed from {}
>
> 2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed to
>
> 2015-08-14 12:30:48 jabber_lib.process: 180
>
> 2015-08-14 12:30:58 jabber_lib.process: 180
>
> Error caught:
>
> Traceback (most recent call last):
>
>   File "/usr/share/rhn/osad/jabber_lib.py", line 121, in main
>
> self.process_forever(c)
>
>   File "/usr/share/rhn/osad/jabber_lib.py", line 179, in process_forever
>
> self.process_once(client)
>
>   File "/usr/share/rhn/osad/osad.py", line 250, in process_once
>
> client.process(timeout=180)
>
>   File "/usr/share/rhn

Re: [Spacewalk-list] problems with osad

2015-08-14 Thread Dimitri Yioulos

I've experienced the same issue on some of my clients.  I had to re-register 
those clients, then thing were all good.  I'm not necessarily saying that the 
same will work for you, but you might want to try re-registering one client to 
see what happens.

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 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.  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 kernel 
varies within the release range.

I've tested using /usr/sbin/osad -N -v -v -v -von several of the other 
clients.  The results are the same with them all ending up at this point:

Error caught:
Traceback (most recent call last):
  File "/usr/share/rhn/osad/jabber_lib.py", line 121, in main
self.process_forever(c)
  File "/usr/share/rhn/osad/jabber_lib.py", line 179, in process_forever
self.process_once(client)
  File "/usr/share/rhn/osad/osad.py", line 250, in process_once
client.process(timeout=180)
  File "/usr/share/rhn/osad/jabber_lib.py", line 1055, in process
data = self._read(self.BLOCK_SIZE)
SSLError: ('OpenSSL error; will retry', "(-1, 'Unexpected EOF')")



From: 
spacewalk-list-boun...@redhat.com<mailto: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<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] problems with osad


Have you made any changes to Spacewalk (e.g. upgrade) or to the Spacewalk host? 
 Made a change to the Spacewalk SSL cert?  Does "serverURL" in 
/etc/sysconfig/rhn/up2date match the Common Name in the certificate you created 
for your Spacewalk environment?  Have you tried re-registering one of the 
systems that's no longer connecting?


Dimitri

From: 
spacewalk-list-boun...@redhat.com<mailto: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' 
mailto:spacewalk-list@redhat.com>>
Subject: [Spacewalk-list] problems with osad

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 systems are no longer 
responding to OSAD requests.

I run OSAD in the foreground as a test and I get this...it is communicating 
with the SW node but then reliably errors out.  The pattern repeats 
endlessly

/usr/sbin/osad -N -v -v -v -v   as

..
2015-08-14 12:30:41 jabber_lib._presence_callback: Node is available 
rhn-dispatcher-...@gfmswalk1lps.hsi.hughessupply.com/superclient<mailto:rhn-dispatcher-...@gfmswalk1lps.hsi.hughessupply.com/superclient>
 None
2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed to 
{'rhn-dispatcher-...@gfmswalk1lps.hsi.hughessupply.com': {'jid': 
'rhn-dispatcher-...@gfmswalk1lps.hsi.hughessupply.com', 'subscription': u'to'}}
2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed both {}
2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed none {}
2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed from {}
2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed to
2015-08-14 12:30:48 jabber_lib.process: 180
2015-08-14 12:30:58 jabber_lib.process: 180
Error caught:
Traceback (most recent call last):
  File "/usr/share/rhn/osad/jabber_lib.py", line 121, in main
self.process_forever(c)
  File "/usr/share/rhn/osad/jabber_lib.py", line 179, in process_forever
self.process_once(client)
  File "/usr/share/rhn/osad/osad.py", line 250, in process_once
client.process(timeout=180)
  File "/usr/share/rhn/osad/jabber_lib.py", line 1055, in process
data = self._read(self.BLOCK_SIZE)
SSLError: ('OpenSSL error; will retry', "(-1, 'Unexpected EOF')")

2015-08-14 12:30:58 jabber_lib.main: Sleeping 88 seconds


Larry Clegg
HD Supply San Diego
Lead Systems Engineer - HDS FM IT Linux Engineering
San Diego, CA
Desk: 858.831.2650  (Cisco ext:  12650)
Cell: 858-880-6578
EMail: larry.cl...@hdsupply.com<mailto:larry.cl...@hdsupply.com>

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] problems with osad

2015-08-14 Thread Clegg, Larry E [HDS]

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 kernel 
varies within the release range.

I've tested using /usr/sbin/osad -N -v -v -v -von several of the other 
clients.  The results are the same with them all ending up at this point:

Error caught:
Traceback (most recent call last):
  File "/usr/share/rhn/osad/jabber_lib.py", line 121, in main
self.process_forever(c)
  File "/usr/share/rhn/osad/jabber_lib.py", line 179, in process_forever
self.process_once(client)
  File "/usr/share/rhn/osad/osad.py", line 250, in process_once
client.process(timeout=180)
  File "/usr/share/rhn/osad/jabber_lib.py", line 1055, in process
data = self._read(self.BLOCK_SIZE)
SSLError: ('OpenSSL error; will retry', "(-1, '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. upgrade) or to the Spacewalk host? 
 Made a change to the Spacewalk SSL cert?  Does "serverURL" in 
/etc/sysconfig/rhn/up2date match the Common Name in the certificate you created 
for your Spacewalk environment?  Have you tried re-registering one of the 
systems that's no longer connecting?


Dimitri

From: 
spacewalk-list-boun...@redhat.com<mailto: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' 
mailto:spacewalk-list@redhat.com>>
Subject: [Spacewalk-list] problems with osad

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 systems are no longer 
responding to OSAD requests.

I run OSAD in the foreground as a test and I get this...it is communicating 
with the SW node but then reliably errors out.  The pattern repeats 
endlessly

/usr/sbin/osad -N -v -v -v -v   as

..
2015-08-14 12:30:41 jabber_lib._presence_callback: Node is available 
rhn-dispatcher-...@gfmswalk1lps.hsi.hughessupply.com/superclient<mailto:rhn-dispatcher-...@gfmswalk1lps.hsi.hughessupply.com/superclient>
 None
2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed to 
{'rhn-dispatcher-...@gfmswalk1lps.hsi.hughessupply.com': {'jid': 
'rhn-dispatcher-...@gfmswalk1lps.hsi.hughessupply.com', 'subscription': u'to'}}
2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed both {}
2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed none {}
2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed from {}
2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed to
2015-08-14 12:30:48 jabber_lib.process: 180
2015-08-14 12:30:58 jabber_lib.process: 180
Error caught:
Traceback (most recent call last):
  File "/usr/share/rhn/osad/jabber_lib.py", line 121, in main
self.process_forever(c)
  File "/usr/share/rhn/osad/jabber_lib.py", line 179, in process_forever
self.process_once(client)
  File "/usr/share/rhn/osad/osad.py", line 250, in process_once
client.process(timeout=180)
  File "/usr/share/rhn/osad/jabber_lib.py", line 1055, in process
data = self._read(self.BLOCK_SIZE)
SSLError: ('OpenSSL error; will retry', "(-1, 'Unexpected EOF')")

2015-08-14 12:30:58 jabber_lib.main: Sleeping 88 seconds


Larry Clegg
HD Supply San Diego
Lead Systems Engineer - HDS FM IT Linux Engineering
San Diego, CA
Desk: 858.831.2650  (Cisco ext:  12650)
Cell: 858-880-6578
EMail: larry.cl...@hdsupply.com<mailto:larry.cl...@hdsupply.com>

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] problems with osad

2015-08-14 Thread Dimitri Yioulos

Have you made any changes to Spacewalk (e.g. upgrade) or to the Spacewalk host? 
 Made a change to the Spacewalk SSL cert?  Does "serverURL" in 
/etc/sysconfig/rhn/up2date match the Common Name in the certificate you created 
for your Spacewalk environment?  Have you tried re-registering one 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' 
Subject: [Spacewalk-list] problems with osad

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 systems are no longer 
responding to OSAD requests.

I run OSAD in the foreground as a test and I get this...it is communicating 
with the SW node but then reliably errors out.  The pattern repeats 
endlessly

/usr/sbin/osad -N -v -v -v -v   as

..
2015-08-14 12:30:41 jabber_lib._presence_callback: Node is available 
rhn-dispatcher-...@gfmswalk1lps.hsi.hughessupply.com/superclient
 None
2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed to 
{'rhn-dispatcher-...@gfmswalk1lps.hsi.hughessupply.com': {'jid': 
'rhn-dispatcher-...@gfmswalk1lps.hsi.hughessupply.com', 'subscription': u'to'}}
2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed both {}
2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed none {}
2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed from {}
2015-08-14 12:30:41 jabber_lib.subscribe_to_presence: Subscribed to
2015-08-14 12:30:48 jabber_lib.process: 180
2015-08-14 12:30:58 jabber_lib.process: 180
Error caught:
Traceback (most recent call last):
  File "/usr/share/rhn/osad/jabber_lib.py", line 121, in main
self.process_forever(c)
  File "/usr/share/rhn/osad/jabber_lib.py", line 179, in process_forever
self.process_once(client)
  File "/usr/share/rhn/osad/osad.py", line 250, in process_once
client.process(timeout=180)
  File "/usr/share/rhn/osad/jabber_lib.py", line 1055, in process
data = self._read(self.BLOCK_SIZE)
SSLError: ('OpenSSL error; will retry', "(-1, 'Unexpected EOF')")

2015-08-14 12:30:58 jabber_lib.main: Sleeping 88 seconds


Larry Clegg
HD Supply San Diego
Lead Systems Engineer - HDS FM IT Linux Engineering
San Diego, CA
Desk: 858.831.2650  (Cisco ext:  12650)
Cell: 858-880-6578
EMail: larry.cl...@hdsupply.com

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Problems with osad/jabberd and scheduler after upgrade

2010-12-09 Thread Trent Johnson

Thanks so much for the quick response.  I have updated today, and the 
server error is gone.

Osad is still not working though.  Not sure how to investigate further. 
 When I ping, nothing comes back.  /var/log/osad on the client has no 
errors.  Scripts scheduled do no process immediately, but do process 
with rhn_check.

Thanks,
Trent

> If you get Internal Server Error on the WebUI, it's not
> osad/jabberd related.
>
> Please upgrade your Spacewalk with packages that I've just today
> pushed to the yum repos.
>
> Yours,
>
> --
> Jan Pazdziora
> Principal Software Engineer, Satellite Engineering, Red Hat
>

On 12/09/2010 12:14 PM, 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

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
local administrator with details of how you received this message.

I think it has to do with jabber, but am not 100% certain. I did follow
the instructions here:
https://www.redhat.com/archives/spacewalk-list/2010-November/msg00181.html

I am not sure what else to look at.

Thanks,
Trent

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Problems with osad/jabberd and scheduler after upgrade

2010-12-09 Thread Jan Pazdziora

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 related.

Please upgrade your Spacewalk with packages that I've just today
pushed to the yum repos.

Yours,

-- 
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] Problems with osad

2010-02-04 Thread Stephen Benjamin

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.


- Steve



On Thu, Feb 4, 2010 at 10:52 AM, Hugo Doria  wrote:

> 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 ?00:00:00 /usr/bin/sm -c
> /etc/jabberd/sm.xml
> jabber   10872 1  0 12:36 ?00:00:00 /usr/bin/c2s -c
> /etc/jabberd/c2s.xml
> jabber   10902 1  0 12:36 ?00:00:00 /usr/bin/s2s -c
> /etc/jabberd/s2s.xml
>
> But when i try to run osad on my spacewalk-client i get:
>
>  /etc/init.d/osad restart
> Shutting down osad:[  OK  ]
> Starting osad: Server did not return a  stanza
> Traceback (most recent call last):
>  File "/usr/share/rhn/osad/jabber_lib.py", line 254, in setup_connection
>c = self._get_jabber_client(js)
>  File "/usr/share/rhn/osad/jabber_lib.py", line 311, in _get_jabber_client
>c.connect()
>  File "/usr/share/rhn/osad/jabber_lib.py", line 593, in connect
>raise SSLDisabledError
> SSLDisabledError
>   [  OK  ]
>
> On /var/log/messages i see several of these messages:
>
> Feb  4 12:48:27 dfsdfgdfg jabberd/c2s[10872]: [9] [10.0.1.6, port=10288]
> connect
> Feb  4 12:48:27 dfsdfgdfg jabberd/c2s[10872]: [9] [10.0.1.6,
> port=10288] disconnect jid=unbound, packets: 0
>
> I am running spacewalk 0.7 on CentOS 5.4 and i followed these instructions:
> https://fedorahosted.org/spacewalk/wiki/OSADSetup
>
> Any tips?
>
> --
> Hugo Doria
>
> ___
> 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

Re: [Spacewalk-list] Problems with OSAD not picking up remote commands

Re: [Spacewalk-list] Problems with OSAD not picking up remote commands

Re: [Spacewalk-list] problems with osad

Re: [Spacewalk-list] problems with osad

Re: [Spacewalk-list] problems with osad

Re: [Spacewalk-list] problems with osad

Re: [Spacewalk-list] problems with osad

Re: [Spacewalk-list] problems with osad

Re: [Spacewalk-list] problems with osad

Re: [Spacewalk-list] problems with osad

Re: [Spacewalk-list] problems with osad

Re: [Spacewalk-list] problems with osad

Re: [Spacewalk-list] problems with osad

Re: [Spacewalk-list] problems with osad

Re: [Spacewalk-list] problems with osad

Re: [Spacewalk-list] Problems with osad/jabberd and scheduler after upgrade

Re: [Spacewalk-list] Problems with osad/jabberd and scheduler after upgrade

Re: [Spacewalk-list] Problems with osad

18 matches

Site Navigation

Mail list logo

Footer information