Re: [Spacewalk-list] osa-dispatcher fails to start

2018-03-15 Thread Daryl Rose 
Alex,


The wildcard cert is all I have to work with as we have multiple products that 
use it.  I don't remember my original reason for using it, but it seemed like 
the thing to do at the time.  Now I'm wishing that I just left it alone.


Thanks


Daryl



From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Alexandru Raceanu <a...@capeno.com>
Sent: Thursday, March 15, 2018 2:46 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start

As far as I know, the python ssl implementation is quite poor when it comes to 
wildcard ssl certificates. Had similar issues.
I would strongly recommend to update the certificate as it's already expired 
and try to avoid wildcards for now.

/Alex


From: "Daryl Rose" <darylr...@outlook.com>
To: spacewalk-list@redhat.com
Sent: Wednesday, March 14, 2018 2:39:41 PM
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start


Yes.


From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Alexandru Raceanu <a...@capeno.com>
Sent: Tuesday, March 13, 2018 3:33 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start

Is the certificate a wildcard ?

/Alex



___
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] osa-dispatcher fails to start

2018-03-15 Thread Alexandru Raceanu 
As far as I know, the python ssl implementation is quite poor when it comes to 
wildcard ssl certificates. Had similar issues. 
I would strongly recommend to update the certificate as it's already expired 
and try to avoid wildcards for now. 

/Alex 


From: "Daryl Rose" <darylr...@outlook.com> 
To: spacewalk-list@redhat.com 
Sent: Wednesday, March 14, 2018 2:39:41 PM 
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start 



Yes. 

From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Alexandru Raceanu <a...@capeno.com> 
Sent: Tuesday, March 13, 2018 3:33 PM 
To: spacewalk-list@redhat.com 
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start 
Is the certificate a wildcard ? 

/Alex 



___ 
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] osa-dispatcher fails to start

2018-03-15 Thread Daryl Rose 
Yes.


From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Alexandru Raceanu <a...@capeno.com>
Sent: Tuesday, March 13, 2018 3:33 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start

Is the certificate a wildcard ?

/Alex


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

Re: [Spacewalk-list] osa-dispatcher fails to start

2018-03-13 Thread Alexandru Raceanu 
Is the certificate a wildcard ? 

/Alex 


From: "Daryl Rose" <darylr...@outlook.com> 
To: spacewalk-list@redhat.com 
Sent: Tuesday, March 13, 2018 8:30:26 PM 
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start 



Alex, 




I just realized that I had more errors to look at. I didn't check the error log 
prior to my last update. 





2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.check_cert('Loading 
cert', ) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
rhnSQL/driver_postgresql.convert_named_query_params('Converting query for 
PostgreSQL: \n select id, password\n from rhnPushDispatcher\n where jabber_id 
like :jabber_id\n ',) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
rhnSQL/driver_postgresql.convert_named_query_params('New query: \n select id, 
password\n from rhnPushDispatcher\n where jabber_id like %(jabber_id)s\n ',) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
rhnSQL/driver_postgresql._execute_wrapper('Executing SQL: "\n select id, 
password\n from rhnPushDispatcher\n where jabber_id like %(jabber_id)s\n " with 
bind params: {jabber_id: rhn-dispatcher-sat%}',) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
osad/jabber_lib.setup_connection('Connecting to', '') 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib._get_jabber_client 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
osad/jabber_lib._get_jabber_client('Connecting to', '') 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.__init__ 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.__init__ 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.check_cert('Loading 
cert', ) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Attempting to 
connect',) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process(300,) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process('before 
select(); timeout', 299.9904632568) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process('select() 
returned',) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
osad/jabber_lib._auth_dispatch(,) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Connected',) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Expecting 
features stanza, got:', :::) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('starttls 
node', ) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process(None,) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process('before 
select(); timeout', None) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process('select() 
returned',) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
osad/jabber_lib._auth_dispatch(,) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Expecting 
proceed stanza, got:', ) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Preparing for 
TLS handshake',) 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('ERROR', 
'Traceback caught:') 
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.main('ERROR', 'Error 
caught:') 

Anything here that might be a clue as to what is going on? 

Thanks 

Daryl 




From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Daryl Rose <darylr...@outlook.com> 
Sent: Tuesday, March 13, 2018 1:51 PM 
To: spacewalk-list@redhat.com 
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start 


Alex, 




Sorry, can't/won't post /etc/hosts and /etc/sysconfig/network. Trust me when I 
say that he server name is fully qualified. Nothing in that regard has changed. 
My suspicion was and still is that it's the cert. 




Looking back on this, I realize that I should have kept the self-signed certs 
in place, but for some reason I had to use a signed cert. I used a doc that I 
found on Oracle explaining how to replace the self-signed certs with a CA 
signed cert. 




The cert expired in January. I posted a question asking if I have to 
re-register all of our clients with a new, updated cert. I was told no, that 
all I had to do was update the certificate for the WUI portion of SW. However, 
I see that the jabber certificate, server.pem, did expire in January. 




I replaced the server.pem cert with the one that was generated when I updated 
the cert earlier this year. I just now verified it against 
/var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT and it came back okay. 





openssl verify -CAfile /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT 
/etc/pki/spacewalk/jabberd/server.pem 
/etc/pki/spacewalk/jabberd/server.pem: OK 





However, I still get the same error when starting the osa-dispatcher. 





- ->  

<-- ::: 

<--  

Spacewalk 6928 2018/03/13 13:41:37 -05:00: ('Traceback caught:',) 
Spacewalk 6928 2018/03/13 13:41:37 -05:00: ('Error caught:',) 

ERROR: unhandled exception occurred: (can't write str to text stream). 





One question that I have, is wh

Re: [Spacewalk-list] osa-dispatcher fails to start

2018-03-13 Thread Robert Paschedag 
On 03/13/18 21:07, Robert Paschedag wrote:
> On 03/13/18 20:30, Daryl Rose wrote:
>> Alex,
>>
>>
>> I just realized that I had more errors to look at.   I didn't check the 
>> error log prior to my last update.
>>
>>
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.check_cert('Loading 
>> cert', > L.L.C./CN=Network Solutions OV Server CA 2'>)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
>> rhnSQL/driver_postgresql.convert_named_query_params('Converting query for 
>> PostgreSQL: \nselect id, password\n  from rhnPushDispatcher\n 
>> where jabber_id like :jabber_id\n',)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
>> rhnSQL/driver_postgresql.convert_named_query_params('New query: \nselect 
>> id, password\n  from rhnPushDispatcher\n where jabber_id like 
>> %(jabber_id)s\n',)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
>> rhnSQL/driver_postgresql._execute_wrapper('Executing SQL: "\nselect id, 
>> password\n  from rhnPushDispatcher\n where jabber_id like 
>> %(jabber_id)s\n" with bind params: {jabber_id: rhn-dispatcher-sat%}',)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
>> osad/jabber_lib.setup_connection('Connecting to', '')
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib._get_jabber_client
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
>> osad/jabber_lib._get_jabber_client('Connecting to', '')
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.__init__
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.__init__
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.check_cert('Loading 
>> cert', > L.L.C./CN=Network Solutions OV Server CA 2'>)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Attempting 
>> to connect',)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process(300,)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process('before 
>> select(); timeout', 299.9904632568)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process('select() 
>> returned',)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
>> osad/jabber_lib._auth_dispatch(> 0x24bf950>,)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
>> osad/jabber_lib.connect('Connected',)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Expecting 
>> features stanza, got:', > 'http://affinix.com/jabber/address' >:::> 'http://jabber.org/features/iq-auth'  />> 'http://jabber.org/features/iq-register'  />> 'urn:ietf:params:xml:ns:xmpp-tls' >)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('starttls 
>> node', )
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process(None,)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process('before 
>> select(); timeout', None)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process('select() 
>> returned',)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
>> osad/jabber_lib._auth_dispatch(> 0x2538b90>,)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Expecting 
>> proceed stanza, got:', )
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Preparing 
>> for TLS handshake',)
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('ERROR', 
>> 'Traceback caught:')
>> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.main('ERROR', 
>> 'Error caught:')
>>
>> Anything here that might be a clue as to what is going on?
>>
>> Thanks
>>
>> Daryl
>>
> 
> So your jabber cert seems to be /etc/pki/spacewalk/jabberd/server.pem
> 
> What does
> 
> openssl x509 -in /etc/pki/spacewalk/jabberd/server.pem -noout -enddate
> -subject
> 
> tell?
> 
> Robert

You also might look into this old messagebut this is a more
"generic" message

https://www.redhat.com/archives/spacewalk-list/2015-September/msg00040.html


>> 
>> From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> 
>> on behalf of Daryl Rose <darylr...@outlook.com>
>> Sent: Tuesday, March 13, 2018 1:51 PM
>> To: spacewalk-list@redhat.com
>> Subject: Re: [Spacewalk-list] osa-dispatcher fails to start
>>
>>
>> Alex,
>>
>>
>> Sorry, can't/won't post /etc/hosts and /etc/sysconfig/network.  Trust me 
>> when I say that he server name is fully qualified.  Nothing in that regard 
>> has

Re: [Spacewalk-list] osa-dispatcher fails to start

2018-03-13 Thread Robert Paschedag 
On 03/13/18 20:30, Daryl Rose wrote:
> Alex,
> 
> 
> I just realized that I had more errors to look at.   I didn't check the error 
> log prior to my last update.
> 
> 
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.check_cert('Loading 
> cert',  L.L.C./CN=Network Solutions OV Server CA 2'>)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
> rhnSQL/driver_postgresql.convert_named_query_params('Converting query for 
> PostgreSQL: \nselect id, password\n  from rhnPushDispatcher\n 
> where jabber_id like :jabber_id\n',)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
> rhnSQL/driver_postgresql.convert_named_query_params('New query: \nselect 
> id, password\n  from rhnPushDispatcher\n where jabber_id like 
> %(jabber_id)s\n',)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
> rhnSQL/driver_postgresql._execute_wrapper('Executing SQL: "\nselect id, 
> password\n  from rhnPushDispatcher\n where jabber_id like 
> %(jabber_id)s\n" with bind params: {jabber_id: rhn-dispatcher-sat%}',)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
> osad/jabber_lib.setup_connection('Connecting to', '')
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib._get_jabber_client
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
> osad/jabber_lib._get_jabber_client('Connecting to', '')
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.__init__
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.__init__
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.check_cert('Loading 
> cert',  L.L.C./CN=Network Solutions OV Server CA 2'>)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Attempting 
> to connect',)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process(300,)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process('before 
> select(); timeout', 299.9904632568)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process('select() 
> returned',)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
> osad/jabber_lib._auth_dispatch(,)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Connected',)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Expecting 
> features stanza, got:',  'http://affinix.com/jabber/address' >::: 'http://jabber.org/features/iq-auth'  /> 'http://jabber.org/features/iq-register'  /> 'urn:ietf:params:xml:ns:xmpp-tls' >)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('starttls 
> node', )
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process(None,)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process('before 
> select(); timeout', None)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process('select() 
> returned',)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
> osad/jabber_lib._auth_dispatch(,)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Expecting 
> proceed stanza, got:', )
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Preparing 
> for TLS handshake',)
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('ERROR', 
> 'Traceback caught:')
> 2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.main('ERROR', 'Error 
> caught:')
> 
> Anything here that might be a clue as to what is going on?
> 
> Thanks
> 
> Daryl
> 

So your jabber cert seems to be /etc/pki/spacewalk/jabberd/server.pem

What does

openssl x509 -in /etc/pki/spacewalk/jabberd/server.pem -noout -enddate
-subject

tell?

Robert
> ________
> From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> 
> on behalf of Daryl Rose <darylr...@outlook.com>
> Sent: Tuesday, March 13, 2018 1:51 PM
> To: spacewalk-list@redhat.com
> Subject: Re: [Spacewalk-list] osa-dispatcher fails to start
> 
> 
> Alex,
> 
> 
> Sorry, can't/won't post /etc/hosts and /etc/sysconfig/network.  Trust me when 
> I say that he server name is fully qualified.  Nothing in that regard has 
> changed.  My suspicion was and still is that it's the cert.
> 
> 
> Looking back on this, I realize that I should have kept the self-signed certs 
> in place, but for some reason I had to use a signed cert.  I used a doc that 
> I found on Oracle explaining how to replace the self-signed certs with a CA 
> signed cert.
> 
> 
> The cert expired in January.  I posted a question asking if I have to 
> re-register all of our clients with a new, updated cert.  I was told no, that 
> all I had to do was update the certificate for the WUI portion of SW.  
> However, I see that the jabber certificate, server.pem, did expi

Re: [Spacewalk-list] osa-dispatcher fails to start

2018-03-13 Thread Robert Paschedag 
Am 13. März 2018 19:51:21 MEZ schrieb Daryl Rose <darylr...@outlook.com>:
>Alex,
>
>
>Sorry, can't/won't post /etc/hosts and /etc/sysconfig/network.  Trust
>me when I say that he server name is fully qualified.  Nothing in that
>regard has changed.  My suspicion was and still is that it's the cert.
>
>
>Looking back on this, I realize that I should have kept the self-signed
>certs in place, but for some reason I had to use a signed cert.  I used
>a doc that I found on Oracle explaining how to replace the self-signed
>certs with a CA signed cert.
>
>
>The cert expired in January.  I posted a question asking if I have to
>re-register all of our clients with a new, updated cert.  I was told
>no, that all I had to do was update the certificate for the WUI portion
>of SW.  However, I see that the jabber certificate, server.pem, did
>expire in January.
>
>
>I replaced the server.pem cert with the one that was generated when I
>updated the cert earlier this year.   I just now verified it against
>/var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT and it came back okay.
>
>
>openssl verify -CAfile /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT
>/etc/pki/spacewalk/jabberd/server.pem
>/etc/pki/spacewalk/jabberd/server.pem: OK
>
>
>However, I still get the same error when starting the osa-dispatcher.
>
>
>--> xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
>
><-- >:::'http://jabber.org/features/iq-auth'  />'http://jabber.org/features/iq-register'  />'urn:ietf:params:xml:ns:xmpp-tls' >
>
><-- 
>
>Spacewalk 6928 2018/03/13 13:41:37 -05:00: ('Traceback caught:',)
>Spacewalk 6928 2018/03/13 13:41:37 -05:00: ('Error caught:',)
>
>ERROR: unhandled exception occurred: (can't write str to text stream).
>
>
>One question that I have, is what are these URL's?
>
>http://affinix.com/jabber/address
>
>http://jabber.org/features/iq-register
>
>
>I'm not knowledgeable in python, but it looks to me as if its
>registering with an external url and is using tls.   First of, why is
>jabber registering with an external url?  And, if it is, is it possible
>that the ca-certificates are out of date and need to be updated?
>
>
>Thanks
>
>
>Daryl
>
>
>
>____________
>From: spacewalk-list-boun...@redhat.com
><spacewalk-list-boun...@redhat.com> on behalf of Alexandru Raceanu
><a...@capeno.com>
>Sent: Tuesday, March 13, 2018 12:18 PM
>To: spacewalk-list@redhat.com
>Subject: Re: [Spacewalk-list] osa-dispatcher fails to start
>
>Can you post the /etc/hosts and /etc/sysconfig/network ?
>if not... check this one: https://access.redhat.com/solutions/327903
>
>/Alex
>
>
>From: "Daryl Rose" <darylr...@outlook.com>
>To: spacewalk-list@redhat.com
>Sent: Tuesday, March 13, 2018 4:22:41 PM
>Subject: Re: [Spacewalk-list] osa-dispatcher fails to start
>
>
>Yes, really, that was all.
>
>
>Here is the output from the very verbose osa-dispatcher start:
>
>
>/usr/sbin/osa-dispatcher -N -v -v -v -v -v -v -v
>--> xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
>
><-- >:::10.255.0.6'http://jabber.org/features/iq-auth'  />'http://jabber.org/features/iq-register'  />'urn:ietf:params:xml:ns:xmpp-tls' >
>
><-- 
>
>Spacewalk 653 2018/03/13 10:18:35 -05:00: ('Traceback caught:',)
>Spacewalk 653 2018/03/13 10:18:35 -05:00: ('Error caught:',)
>
>ERROR: unhandled exception occurred: (can't write str to text stream).
>
>Thank you
>
>
>Daryl
>
>
>From: spacewalk-list-boun...@redhat.com
><spacewalk-list-boun...@redhat.com> on behalf of Paschedag, Robert
><paschedag.netlut...@swr.de>
>Sent: Tuesday, March 13, 2018 8:47 AM
>To: spacewalk-list@redhat.com
>Subject: Re: [Spacewalk-list] osa-dispatcher fails to start
>
>
>Is that really all??
>
>
>
>With this information only, it is impossible to help.
>
>
>
>You can try to run osa-dispatcher manually
>
>
>
>Stop it
>
>
>
>/etc/init.d/osa-dispatcher stop
>
>
>
>Run it manually
>
>
>
>/usr/sbin/osa-dispatcher -N -v -v -v -v -v -v -v
>
>
>
>and post errors you get.
>
>
>
>Robert
>
>
>
>
>
>Von: spacewalk-list-boun...@redhat.com
><spacewalk-list-boun...@redhat.com> Im Auftrag von Daryl Rose
>Gesendet: Dienstag, 13. März 2018 14:14
>An: spacewalk-list@redhat.com
>Betreff: Re: [Spacewalk-list] osa-dispatcher fails to start
>
>
>
>Here are the requested entries.
>
>
>
>2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib._

Re: [Spacewalk-list] osa-dispatcher fails to start

2018-03-13 Thread Daryl Rose 
Alex,


I just realized that I had more errors to look at.   I didn't check the error 
log prior to my last update.


2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.check_cert('Loading 
cert', )
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
rhnSQL/driver_postgresql.convert_named_query_params('Converting query for 
PostgreSQL: \nselect id, password\n  from rhnPushDispatcher\n where 
jabber_id like :jabber_id\n',)
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
rhnSQL/driver_postgresql.convert_named_query_params('New query: \nselect 
id, password\n  from rhnPushDispatcher\n where jabber_id like 
%(jabber_id)s\n',)
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
rhnSQL/driver_postgresql._execute_wrapper('Executing SQL: "\nselect id, 
password\n  from rhnPushDispatcher\n where jabber_id like 
%(jabber_id)s\n" with bind params: {jabber_id: rhn-dispatcher-sat%}',)
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
osad/jabber_lib.setup_connection('Connecting to', '')
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib._get_jabber_client
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
osad/jabber_lib._get_jabber_client('Connecting to', '')
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.__init__
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.__init__
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.check_cert('Loading 
cert', )
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Attempting to 
connect',)
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process(300,)
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process('before 
select(); timeout', 299.9904632568)
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process('select() 
returned',)
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
osad/jabber_lib._auth_dispatch(,)
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Connected',)
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Expecting 
features stanza, got:', :::)
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('starttls 
node', )
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process(None,)
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process('before 
select(); timeout', None)
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.process('select() 
returned',)
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: 
osad/jabber_lib._auth_dispatch(,)
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Expecting 
proceed stanza, got:', )
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('Preparing for 
TLS handshake',)
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.connect('ERROR', 
'Traceback caught:')
2018/03/13 14:24:59 -05:00 8164 0.0.0.0: osad/jabber_lib.main('ERROR', 'Error 
caught:')

Anything here that might be a clue as to what is going on?

Thanks

Daryl


From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Daryl Rose <darylr...@outlook.com>
Sent: Tuesday, March 13, 2018 1:51 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start


Alex,


Sorry, can't/won't post /etc/hosts and /etc/sysconfig/network.  Trust me when I 
say that he server name is fully qualified.  Nothing in that regard has 
changed.  My suspicion was and still is that it's the cert.


Looking back on this, I realize that I should have kept the self-signed certs 
in place, but for some reason I had to use a signed cert.  I used a doc that I 
found on Oracle explaining how to replace the self-signed certs with a CA 
signed cert.


The cert expired in January.  I posted a question asking if I have to 
re-register all of our clients with a new, updated cert.  I was told no, that 
all I had to do was update the certificate for the WUI portion of SW.  However, 
I see that the jabber certificate, server.pem, did expire in January.


I replaced the server.pem cert with the one that was generated when I updated 
the cert earlier this year.   I just now verified it against 
/var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT and it came back okay.


openssl verify -CAfile /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT 
/etc/pki/spacewalk/jabberd/server.pem
/etc/pki/spacewalk/jabberd/server.pem: OK


However, I still get the same error when starting the osa-dispatcher.


--> 

<-- :::

<-- 

Spacewalk 6928 2018/03/13 13:41:37 -05:00: ('Traceback caught:',)
Spacewalk 6928 2018/03/13 13:41:37 -05:00: ('Error caught:',)

ERROR: unhandled exception occurred: (can't write str to text stream).


One question that I have, is what are these URL's?

http://affinix.com/jabber/address

http://jabber.org/features/iq-register


I'm not knowledgeable in python, but it looks to me as if its registering with 
an external url and is using tls.   First of, why is jabbe

Re: [Spacewalk-list] osa-dispatcher fails to start

2018-03-13 Thread Daryl Rose 
Alex,


Sorry, can't/won't post /etc/hosts and /etc/sysconfig/network.  Trust me when I 
say that he server name is fully qualified.  Nothing in that regard has 
changed.  My suspicion was and still is that it's the cert.


Looking back on this, I realize that I should have kept the self-signed certs 
in place, but for some reason I had to use a signed cert.  I used a doc that I 
found on Oracle explaining how to replace the self-signed certs with a CA 
signed cert.


The cert expired in January.  I posted a question asking if I have to 
re-register all of our clients with a new, updated cert.  I was told no, that 
all I had to do was update the certificate for the WUI portion of SW.  However, 
I see that the jabber certificate, server.pem, did expire in January.


I replaced the server.pem cert with the one that was generated when I updated 
the cert earlier this year.   I just now verified it against 
/var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT and it came back okay.


openssl verify -CAfile /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT 
/etc/pki/spacewalk/jabberd/server.pem
/etc/pki/spacewalk/jabberd/server.pem: OK


However, I still get the same error when starting the osa-dispatcher.


--> 

<-- :::

<-- 

Spacewalk 6928 2018/03/13 13:41:37 -05:00: ('Traceback caught:',)
Spacewalk 6928 2018/03/13 13:41:37 -05:00: ('Error caught:',)

ERROR: unhandled exception occurred: (can't write str to text stream).


One question that I have, is what are these URL's?

http://affinix.com/jabber/address

http://jabber.org/features/iq-register


I'm not knowledgeable in python, but it looks to me as if its registering with 
an external url and is using tls.   First of, why is jabber registering with an 
external url?  And, if it is, is it possible that the ca-certificates are out 
of date and need to be updated?


Thanks


Daryl




From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Alexandru Raceanu <a...@capeno.com>
Sent: Tuesday, March 13, 2018 12:18 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start

Can you post the /etc/hosts and /etc/sysconfig/network ?
if not... check this one: https://access.redhat.com/solutions/327903

/Alex


From: "Daryl Rose" <darylr...@outlook.com>
To: spacewalk-list@redhat.com
Sent: Tuesday, March 13, 2018 4:22:41 PM
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start


Yes, really, that was all.


Here is the output from the very verbose osa-dispatcher start:


/usr/sbin/osa-dispatcher -N -v -v -v -v -v -v -v
--> 

<-- :::10.255.0.6

<-- 

Spacewalk 653 2018/03/13 10:18:35 -05:00: ('Traceback caught:',)
Spacewalk 653 2018/03/13 10:18:35 -05:00: ('Error caught:',)

ERROR: unhandled exception occurred: (can't write str to text stream).

Thank you


Daryl


From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Paschedag, Robert <paschedag.netlut...@swr.de>
Sent: Tuesday, March 13, 2018 8:47 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start


Is that really all??



With this information only, it is impossible to help.



You can try to run osa-dispatcher manually



Stop it



/etc/init.d/osa-dispatcher stop



Run it manually



/usr/sbin/osa-dispatcher -N -v -v -v -v -v -v -v



and post errors you get.



Robert





Von: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> Im 
Auftrag von Daryl Rose
Gesendet: Dienstag, 13. März 2018 14:14
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] osa-dispatcher fails to start



Here are the requested entries.



2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.__init__

2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.connect('ERROR', 
'Traceback caught:')

2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.main('ERROR', 'Error 
caught:')



Thank you.



Daryl







From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
<spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Alexandru Raceanu <a...@capeno.com<mailto:a...@capeno.com>>
Sent: Monday, March 12, 2018 12:52 PM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start



Can you provide the entries after a "/etc/init.d/osa-dispatcher restart" from 
/var/log/rhn/osa-dispatcher.log ?



/Alex







From: "Daryl Rose" <darylr...@outlook.com<mailto:darylr...@outlook.com>>
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Sent: Monday, March 12, 2018 4:28:18 PM
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start

Re: [Spacewalk-list] osa-dispatcher fails to start

2018-03-13 Thread Alexandru Raceanu 
Can you post the /etc/hosts and /etc/sysconfig/network ? 
if not... check this one: https://access.redhat.com/solutions/327903 

/Alex 


From: "Daryl Rose" <darylr...@outlook.com> 
To: spacewalk-list@redhat.com 
Sent: Tuesday, March 13, 2018 4:22:41 PM 
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start 



Yes, really, that was all. 




Here is the output from the very verbose osa-dispatcher start: 





/usr/sbin/osa-dispatcher -N -v -v -v -v -v -v -v 
-->  

<-- :::10.255.0.6 

<--  

Spacewalk 653 2018/03/13 10:18:35 -05:00: ('Traceback caught:',) 
Spacewalk 653 2018/03/13 10:18:35 -05:00: ('Error caught:',) 

ERROR: unhandled exception occurred: (can't write str to text stream). 

Thank you 






Daryl 

From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Paschedag, Robert <paschedag.netlut...@swr.de> 
Sent: Tuesday, March 13, 2018 8:47 AM 
To: spacewalk-list@redhat.com 
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start 


Is that really all?? 



With this information only, it is impossible to help. 



You can try to run osa-dispatcher manually 



Stop it 



/etc/init.d/osa-dispatcher stop 



Run it manually 



/usr/sbin/osa-dispatcher -N -v -v -v -v -v -v -v 



and post errors you get. 



Robert 






Von: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> Im 
Auftrag von Daryl Rose 
Gesendet: Dienstag, 13. März 2018 14:14 
An: spacewalk-list@redhat.com 
Betreff: Re: [Spacewalk-list] osa-dispatcher fails to start 





Here are the requested entries. 




2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.__init__ 


2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.connect('ERROR', 
'Traceback caught:') 


2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.main('ERROR', 'Error 
caught:') 




Thank you. 



Daryl 







From: spacewalk-list-boun...@redhat.com < spacewalk-list-boun...@redhat.com > 
on behalf of Alexandru Raceanu < a...@capeno.com > 
Sent: Monday, March 12, 2018 12:52 PM 
To: spacewalk-list@redhat.com 
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start 





Can you provide the entries after a "/etc/init.d/osa-dispatcher restart" from 
/var/log/rhn/osa-dispatcher.log ? 





/Alex 









From: "Daryl Rose" < darylr...@outlook.com > 
To: spacewalk-list@redhat.com 
Sent: Monday, March 12, 2018 4:28:18 PM 
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start 





I'm sorry, I just realized that I should have provided more information. 



1. This is a RHEL 6.8 server 
2. SW v2.6. 




Also, we use a signed cert and the certificate expired January. I inquired on 
this list and I was told that I only needed to update the cert for the website 
portion of the cert that they cert used to communicate between the systems did 
not need to be changed. 



I'm guessing its a cert issue from some of the research that I did, but I'm not 
sure what I should update, or if I really need to. 



Thanks 



Daryl 





From: spacewalk-list-boun...@redhat.com < spacewalk-list-boun...@redhat.com > 
on behalf of Daryl Rose < darylr...@outlook.com > 
Sent: Monday, March 12, 2018 10:19 AM 
To: spacewalk-list@redhat.com 
Subject: [Spacewalk-list] osa-dispatcher fails to start 





osa-dispatcher is down and won't start. I get the following error when trying 
to start it: 




Starting osa-dispatcher: Spacewalk 43238 2018/03/12 10:17:13 -05:00: 
('Traceback caught:',) 


Spacewalk 43238 2018/03/12 10:17:13 -05:00: ('Error caught:',) 





ERROR: unhandled exception occurred: (can't write str to text stream). 


[FAILED] 




Any suggestions? 



Thanks 



Daryl 



___ 
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 
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Re: [Spacewalk-list] osa-dispatcher fails to start

2018-03-13 Thread Robert Paschedag 
Am 13. März 2018 16:22:41 MEZ schrieb Daryl Rose <darylr...@outlook.com>:
>Yes, really, that was all.
>
>
>Here is the output from the very verbose osa-dispatcher start:
>
>
>/usr/sbin/osa-dispatcher -N -v -v -v -v -v -v -v
>--> xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
>
><-- >:::10.255.0.6'http://jabber.org/features/iq-auth'  />'http://jabber.org/features/iq-register'  />'urn:ietf:params:xml:ns:xmpp-tls' >
>
><-- 
>
>Spacewalk 653 2018/03/13 10:18:35 -05:00: ('Traceback caught:',)
>Spacewalk 653 2018/03/13 10:18:35 -05:00: ('Error caught:',)
>
>ERROR: unhandled exception occurred: (can't write str to text stream).
>
>Thank you
>
>
>Daryl
>
>
>From: spacewalk-list-boun...@redhat.com
><spacewalk-list-boun...@redhat.com> on behalf of Paschedag, Robert
><paschedag.netlut...@swr.de>
>Sent: Tuesday, March 13, 2018 8:47 AM
>To: spacewalk-list@redhat.com
>Subject: Re: [Spacewalk-list] osa-dispatcher fails to start
>
>
>Is that really all??
>
>
>
>With this information only, it is impossible to help.
>
>
>
>You can try to run osa-dispatcher manually
>
>
>
>Stop it
>
>
>
>/etc/init.d/osa-dispatcher stop
>
>
>
>Run it manually
>
>
>
>/usr/sbin/osa-dispatcher -N -v -v -v -v -v -v -v
>
>
>
>and post errors you get.
>
>
>
>Robert
>
>
>
>
>
>Von: spacewalk-list-boun...@redhat.com
><spacewalk-list-boun...@redhat.com> Im Auftrag von Daryl Rose
>Gesendet: Dienstag, 13. März 2018 14:14
>An: spacewalk-list@redhat.com
>Betreff: Re: [Spacewalk-list] osa-dispatcher fails to start
>
>
>
>Here are the requested entries.
>
>
>
>2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.__init__
>
>2018/03/13 08:11:08 -05:00 45604 0.0.0.0:
>osad/jabber_lib.connect('ERROR', 'Traceback caught:')
>
>2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.main('ERROR',
>'Error caught:')
>
>
>
>Thank you.
>
>
>
>Daryl
>
>
>
>
>
>____
>
>From:
>spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>
><spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>>
>on behalf of Alexandru Raceanu
><a...@capeno.com<mailto:a...@capeno.com>>
>Sent: Monday, March 12, 2018 12:52 PM
>To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
>Subject: Re: [Spacewalk-list] osa-dispatcher fails to start
>
>
>
>Can you provide the entries after a "/etc/init.d/osa-dispatcher
>restart" from /var/log/rhn/osa-dispatcher.log ?
>
>
>
>/Alex
>
>
>
>
>
>
>
>From: "Daryl Rose"
><darylr...@outlook.com<mailto:darylr...@outlook.com>>
>To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
>Sent: Monday, March 12, 2018 4:28:18 PM
>Subject: Re: [Spacewalk-list] osa-dispatcher fails to start
>
>
>
>I'm sorry, I just realized that I should have provided more
>information.
>
>
>
>  1.  This is a RHEL 6.8 server
>  2.  SW v2.6.
>
>
>
>Also, we use a signed cert and the certificate expired January.  I
>inquired on this list and I was told that I only needed to update the
>cert for the website portion of the cert that they cert used to
>communicate between the systems did not need to be changed.
>
>
>
>I'm guessing its a cert issue from some of the research that I did, but
>I'm not sure what I should update, or if I really need to.
>
>
>
>Thanks
>
>
>
>Daryl
>
>
>
>
>
>From:
>spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>
><spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>>
>on behalf of Daryl Rose
><darylr...@outlook.com<mailto:darylr...@outlook.com>>
>Sent: Monday, March 12, 2018 10:19 AM
>To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
>Subject: [Spacewalk-list] osa-dispatcher fails to start
>
>
>
>osa-dispatcher is down and won't start.   I get the following error
>when trying to start it:
>
>
>
>Starting osa-dispatcher: Spacewalk 43238 2018/03/12 10:17:13 -05:00:
>('Traceback caught:',)
>
>Spacewalk 43238 2018/03/12 10:17:13 -05:00: ('Error caught:',)
>
>
>
>ERROR: unhandled exception occurred: (can't write str to text stream).
>
>   [FAILED]
>
>
>
>Any suggestions?
>
>
>
>Thanks
>
>
>
>Daryl
>
>___
>Spacewalk-list mailing list
>Spacewalk-list@redhat.com<mailto:Spacewalk-list@redhat.com>
>https://www.redhat.com/mailman/listinfo/spacewalk-list

Did you update some python modules on the server?


-- 
sent from my mobile device

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

Re: [Spacewalk-list] osa-dispatcher fails to start

2018-03-13 Thread Daryl Rose 
Yes, really, that was all.


Here is the output from the very verbose osa-dispatcher start:


/usr/sbin/osa-dispatcher -N -v -v -v -v -v -v -v
--> 

<-- :::10.255.0.6

<-- 

Spacewalk 653 2018/03/13 10:18:35 -05:00: ('Traceback caught:',)
Spacewalk 653 2018/03/13 10:18:35 -05:00: ('Error caught:',)

ERROR: unhandled exception occurred: (can't write str to text stream).

Thank you


Daryl


From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Paschedag, Robert <paschedag.netlut...@swr.de>
Sent: Tuesday, March 13, 2018 8:47 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start


Is that really all??



With this information only, it is impossible to help.



You can try to run osa-dispatcher manually



Stop it



/etc/init.d/osa-dispatcher stop



Run it manually



/usr/sbin/osa-dispatcher -N -v -v -v -v -v -v -v



and post errors you get.



Robert





Von: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> Im 
Auftrag von Daryl Rose
Gesendet: Dienstag, 13. März 2018 14:14
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] osa-dispatcher fails to start



Here are the requested entries.



2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.__init__

2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.connect('ERROR', 
'Traceback caught:')

2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.main('ERROR', 'Error 
caught:')



Thank you.



Daryl







From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
<spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Alexandru Raceanu <a...@capeno.com<mailto:a...@capeno.com>>
Sent: Monday, March 12, 2018 12:52 PM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start



Can you provide the entries after a "/etc/init.d/osa-dispatcher restart" from 
/var/log/rhn/osa-dispatcher.log ?



/Alex







From: "Daryl Rose" <darylr...@outlook.com<mailto:darylr...@outlook.com>>
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Sent: Monday, March 12, 2018 4:28:18 PM
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start



I'm sorry, I just realized that I should have provided more information.



  1.  This is a RHEL 6.8 server
  2.  SW v2.6.



Also, we use a signed cert and the certificate expired January.  I inquired on 
this list and I was told that I only needed to update the cert for the website 
portion of the cert that they cert used to communicate between the systems did 
not need to be changed.



I'm guessing its a cert issue from some of the research that I did, but I'm not 
sure what I should update, or if I really need to.



Thanks



Daryl





From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
<spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Daryl Rose <darylr...@outlook.com<mailto:darylr...@outlook.com>>
Sent: Monday, March 12, 2018 10:19 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [Spacewalk-list] osa-dispatcher fails to start



osa-dispatcher is down and won't start.   I get the following error when trying 
to start it:



Starting osa-dispatcher: Spacewalk 43238 2018/03/12 10:17:13 -05:00: 
('Traceback caught:',)

Spacewalk 43238 2018/03/12 10:17:13 -05:00: ('Error caught:',)



ERROR: unhandled exception occurred: (can't write str to text stream).

   [FAILED]



Any suggestions?



Thanks



Daryl

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com<mailto: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] osa-dispatcher fails to start

2018-03-13 Thread Paschedag, Robert 
Is that really all??

With this information only, it is impossible to help.

You can try to run osa-dispatcher manually

Stop it

/etc/init.d/osa-dispatcher stop

Run it manually

/usr/sbin/osa-dispatcher -N -v -v -v -v -v -v -v

and post errors you get.

Robert


Von: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> Im 
Auftrag von Daryl Rose
Gesendet: Dienstag, 13. März 2018 14:14
An: spacewalk-list@redhat.com
Betreff: Re: [Spacewalk-list] osa-dispatcher fails to start


Here are the requested entries.


2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.__init__
2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.connect('ERROR', 
'Traceback caught:')
2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.main('ERROR', 'Error 
caught:')


Thank you.



Daryl




From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
<spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Alexandru Raceanu <a...@capeno.com<mailto:a...@capeno.com>>
Sent: Monday, March 12, 2018 12:52 PM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start

Can you provide the entries after a "/etc/init.d/osa-dispatcher restart" from 
/var/log/rhn/osa-dispatcher.log ?

/Alex



From: "Daryl Rose" <darylr...@outlook.com<mailto:darylr...@outlook.com>>
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Sent: Monday, March 12, 2018 4:28:18 PM
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start


I'm sorry, I just realized that I should have provided more information.



  1.  This is a RHEL 6.8 server
  2.  SW v2.6.


Also, we use a signed cert and the certificate expired January.  I inquired on 
this list and I was told that I only needed to update the cert for the website 
portion of the cert that they cert used to communicate between the systems did 
not need to be changed.



I'm guessing its a cert issue from some of the research that I did, but I'm not 
sure what I should update, or if I really need to.



Thanks



Daryl


From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
<spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com>> 
on behalf of Daryl Rose <darylr...@outlook.com<mailto:darylr...@outlook.com>>
Sent: Monday, March 12, 2018 10:19 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: [Spacewalk-list] osa-dispatcher fails to start


osa-dispatcher is down and won't start.   I get the following error when trying 
to start it:


Starting osa-dispatcher: Spacewalk 43238 2018/03/12 10:17:13 -05:00: 
('Traceback caught:',)
Spacewalk 43238 2018/03/12 10:17:13 -05:00: ('Error caught:',)

ERROR: unhandled exception occurred: (can't write str to text stream).
   [FAILED]


Any suggestions?



Thanks



Daryl

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com<mailto: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] osa-dispatcher fails to start

2018-03-13 Thread Daryl Rose 
Here are the requested entries.


2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.__init__
2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.connect('ERROR', 
'Traceback caught:')
2018/03/13 08:11:08 -05:00 45604 0.0.0.0: osad/jabber_lib.main('ERROR', 'Error 
caught:')


Thank you.


Daryl




From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Alexandru Raceanu <a...@capeno.com>
Sent: Monday, March 12, 2018 12:52 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start

Can you provide the entries after a "/etc/init.d/osa-dispatcher restart" from 
/var/log/rhn/osa-dispatcher.log ?

/Alex



From: "Daryl Rose" <darylr...@outlook.com>
To: spacewalk-list@redhat.com
Sent: Monday, March 12, 2018 4:28:18 PM
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start


I'm sorry, I just realized that I should have provided more information.


  1.  This is a RHEL 6.8 server
  2.  SW v2.6.


Also, we use a signed cert and the certificate expired January.  I inquired on 
this list and I was told that I only needed to update the cert for the website 
portion of the cert that they cert used to communicate between the systems did 
not need to be changed.


I'm guessing its a cert issue from some of the research that I did, but I'm not 
sure what I should update, or if I really need to.


Thanks


Daryl



From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Daryl Rose <darylr...@outlook.com>
Sent: Monday, March 12, 2018 10:19 AM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] osa-dispatcher fails to start


osa-dispatcher is down and won't start.   I get the following error when trying 
to start it:


Starting osa-dispatcher: Spacewalk 43238 2018/03/12 10:17:13 -05:00: 
('Traceback caught:',)
Spacewalk 43238 2018/03/12 10:17:13 -05:00: ('Error caught:',)

ERROR: unhandled exception occurred: (can't write str to text stream).
   [FAILED]


Any suggestions?


Thanks


Daryl

___
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] osa-dispatcher fails to start

2018-03-12 Thread Alexandru Raceanu 
Can you provide the entries after a "/etc/init.d/osa-dispatcher restart" from 
/var/log/rhn/osa-dispatcher.log ? 

/Alex 



From: "Daryl Rose" <darylr...@outlook.com> 
To: spacewalk-list@redhat.com 
Sent: Monday, March 12, 2018 4:28:18 PM 
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start 



I'm sorry, I just realized that I should have provided more information. 






1. This is a RHEL 6.8 server 
2. SW v2.6. 





Also, we use a signed cert and the certificate expired January. I inquired on 
this list and I was told that I only needed to update the cert for the website 
portion of the cert that they cert used to communicate between the systems did 
not need to be changed. 




I'm guessing its a cert issue from some of the research that I did, but I'm not 
sure what I should update, or if I really need to. 




Thanks 




Daryl 


From: spacewalk-list-boun...@redhat.com <spacewalk-list-boun...@redhat.com> on 
behalf of Daryl Rose <darylr...@outlook.com> 
Sent: Monday, March 12, 2018 10:19 AM 
To: spacewalk-list@redhat.com 
Subject: [Spacewalk-list] osa-dispatcher fails to start 


osa-dispatcher is down and won't start. I get the following error when trying 
to start it: 






Starting osa-dispatcher: Spacewalk 43238 2018/03/12 10:17:13 -05:00: 
('Traceback caught:',) 
Spacewalk 43238 2018/03/12 10:17:13 -05:00: ('Error caught:',) 

ERROR: unhandled exception occurred: (can't write str to text stream). 
[FAILED] 





Any suggestions? 




Thanks 




Daryl 

___ 
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] osa-dispatcher fails to start

2018-03-12 Thread Daryl Rose 
I'm sorry, I just realized that I should have provided more information.


  1.  This is a RHEL 6.8 server
  2.  SW v2.6.


Also, we use a signed cert and the certificate expired January.  I inquired on 
this list and I was told that I only needed to update the cert for the website 
portion of the cert that they cert used to communicate between the systems did 
not need to be changed.


I'm guessing its a cert issue from some of the research that I did, but I'm not 
sure what I should update, or if I really need to.


Thanks


Daryl



From: spacewalk-list-boun...@redhat.com  on 
behalf of Daryl Rose 
Sent: Monday, March 12, 2018 10:19 AM
To: spacewalk-list@redhat.com
Subject: [Spacewalk-list] osa-dispatcher fails to start


osa-dispatcher is down and won't start.   I get the following error when trying 
to start it:


Starting osa-dispatcher: Spacewalk 43238 2018/03/12 10:17:13 -05:00: 
('Traceback caught:',)
Spacewalk 43238 2018/03/12 10:17:13 -05:00: ('Error caught:',)

ERROR: unhandled exception occurred: (can't write str to text stream).
   [FAILED]


Any suggestions?


Thanks


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

Re: [Spacewalk-list] osa-dispatcher fails to start with null ssl error

2017-12-22 Thread Adams , Nick 
Thank you Bruce, you have just made my holidays complete!

Worked like a charm, service is now starting successfully!

Thank you,


[new_sig]
[stifel-sig]

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Bruce Wainer
Sent: Friday, December 22, 2017 2:41 PM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start with null ssl error

Hostname for spacewalk/satellite servers can be lowercase only, otherwise it 
causes exactly the type of issue with OSA that you are experiencing. This is 
documented in the satellite documentation, and was added just days ago to the 
spacewalk wiki.

On Dec 22, 2017, at 11:29 AM, Adams, Nick 
<ada...@stifel.com<mailto:ada...@stifel.com>> wrote:
Thanks Vipul for the quick reply! I’ve updated the hostname to be an fqdn that 
is resolvable via DNS, though the same error still persists.

Please see the following changes:
[root@SNCFGSPWD01S ~]# cat /etc/hostname
SNCFGSPWD01S.stifelnet.stifel.local

Osa-dispatcher.log:
2017/12/22 10:06:36 -05:00 6374 0.0.0.0: osad/jabber_lib.__init__
2017/12/22 10:06:36 -05:00 6374 0.0.0.0: osad/jabber_lib.connect('Server did 
not return a  stanza, reconnecting',)
2017/12/22 10:06:37 -05:00 6374 0.0.0.0: osad/jabber_lib.connect('Server did 
not return a  stanza, reconnecting',)
2017/12/22 10:06:38 -05:00 6374 0.0.0.0: osad/jabber_lib.connect('Server did 
not return a  stanza, reconnecting',)
2017/12/22 10:06:39 -05:00 6374 0.0.0.0: osad/jabber_lib.connect('ERROR', 'Not 
able to reconnect - See https://access.redhat.com/solutions/45332 for possible 
solutions.\n')
2017/12/22 10:06:39 -05:00 6374 0.0.0.0: 
osad/jabber_lib.print_message('SSLError',)
2017/12/22 10:06:39 -05:00 6374 0.0.0.0: osad/jabber_lib.print_message('Could 
not connect to jabber server', 'SNCFGSPWD01S.stifelnet.stifel.local')
2017/12/22 10:06:39 -05:00 6374 0.0.0.0: osad/jabber_lib.main('ERROR', 'Error 
caught:')

rhn.conf:
# OSA configuration #

server.jabber_server = SNCFGSPWD01S.stifelnet.stifel.local
osa-dispatcher.jabber_server = SNCFGSPWD01S.stifelnet.stifel.local

# set up SSL on the dispatcher
osa-dispatcher.osa_ssl_cert = /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT

# system snapshots enabled
enable_snapshots = 1

#cobbler host name
cobbler.host = SNCFGSPWD01S.stifelnet.stifel.local


SSL subjects:
[root@SNCFGSPWD01S ~]# grep CN= /etc/pki/spacewalk/jabberd/server.pem | grep 
Subject
Subject: C=US, ST=MO, O=Stifel, OU=SNCFGSPWD01S.stifelnet.stifel.local, 
CN=SNCFGSPWD01S.stifelnet.stifel.local/emailAddress=ada...@stifel.com<mailto:CN=SNCFGSPWD01S.stifelnet.stifel.local/emailAddress=ada...@stifel.com>
[root@SNCFGSPWD01S ~]# grep CN= $(grep spacewalk.crt /etc/httpd/conf.d/ssl.conf 
| cut -f 2 -d' ') | grep Subject
Subject: C=US, ST=MO, O=Stifel, OU=SNCFGSPWD01S.stifelnet.stifel.local, 
CN=SNCFGSPWD01S.stifelnet.stifel.local/emailAddress=ada...@stifel.com<mailto:CN=SNCFGSPWD01S.stifelnet.stifel.local/emailAddress=ada...@stifel.com>


Jabber configs:
[root@SNCFGSPWD01S ~]# grep $(hostname) /etc/jabberd/*xml
/etc/jabberd/c2s.xml:SNCFGSPWD01S.stifelnet.stifel.local
/etc/jabberd/sm.xml:  SNCFGSPWD01S.stifelnet.stifel.local
/etc/jabberd/sm.xml:SNCFGSPWD01S.stifelnet.stifel.local
/etc/jabberd/sm.xml:SNCFGSPWD01S.stifelnet.stifel.local
[root@SNCFGSPWD01S ~]# grep require-starttls /etc/jabberd/c2s.xml | grep pemfile
SNCFGSPWD01S.stifelnet.stifel.local


Thanks!



[stifel-sig]

From: 
spacewalk-list-boun...@redhat.com<mailto:spacewalk-list-boun...@redhat.com> 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Vipul Sharma (DevOps)
Sent: Friday, December 22, 2017 9:56 AM
To: spacewalk-list@redhat.com<mailto:spacewalk-list@redhat.com>
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start with null ssl error

Some pointers -

  *   Your hostname should match your FQDN -
  *   Compare your SSL certs between /var/jabberd/server.pem & 
/etc/pki/spacewalk/server.pem - They should be same.
  *   CN & OU should be your FQDN in your .crt & .pem files.

Thanks

Vipul


On Fri, Dec 22, 2017 at 8:29 PM, Adams, Nick 
<ada...@stifel.com<mailto:ada...@stifel.com>> wrote:
All,

I have ran into what I hope is a simple misconfiguration during setup. I am 
unable to start the osa-dispatcher service:

[root@SNCFGSPWD01S ~]# spacewalk-service restart
Shutting down spacewalk services...
Redirecting to /bin/systemctl stop taskomatic.service
Stopping cobblerd (via systemctl): [  OK  ]
Redirecting to /bin/systemctl stop rhn-search.service
Redirecting to /bin/systemctl stop osa-dispatcher.service
Redirecting to /bin/systemctl stop httpd.service
Redirecting to /bin/systemctl stop tomcat.service
Redirecting to /bin/systemctl stop jabberd.service
Done.
Starting spacewalk services...
Redirecting to /bin/systemctl start jabberd.service
Redirecting to /bin/systemctl start tomcat.service
Waiting for tomcat to be

Re: [Spacewalk-list] osa-dispatcher fails to start with null ssl error

2017-12-22 Thread Vipul Sharma (DevOps) 
Hey,

I need some more information --

Please add 'debug = 5' ( Please remove the '' )  in your rhn.conf & tailf
the osa-dispatcher log along with jabber logs.

osa-dispatcher logs --> tailf /var/log/rhn/osa-dispatcher.log

jabberd logs --> tailf /var/log/messages

*Let me know what you get from jabberd logs and osa-dispatcher logs.*

Then follow the given below steps - Let me know, I'm in IST time zone, So
reply can take some time - Till then keep googling -

On the Spacewalk server run:

systemctl stop jabberd
systemctl stop osa-dispatcher
rm -Rf /var/lib/jabberd/db/*
systemctl start jabberd
systemctl start osa-dispatcher

Thanks
Vipul
DevOps Architect

On Fri, Dec 22, 2017 at 9:59 PM, Adams, Nick <ada...@stifel.com> wrote:

> Thanks Vipul for the quick reply! I’ve updated the hostname to be an fqdn
> that is resolvable via DNS, though the same error still persists.
>
>
>
> Please see the following changes:
>
> [root@SNCFGSPWD01S ~]# cat /etc/hostname
>
> SNCFGSPWD01S.stifelnet.stifel.local
>
>
>
> Osa-dispatcher.log:
>
> 2017/12/22 10:06:36 -05:00 6374 0.0.0.0: osad/jabber_lib.__init__
>
> 2017/12/22 10:06:36 -05:00 6374 0.0.0.0: osad/jabber_lib.connect('Server
> did not return a  stanza, reconnecting',)
>
> 2017/12/22 10:06:37 -05:00 6374 0.0.0.0: osad/jabber_lib.connect('Server
> did not return a  stanza, reconnecting',)
>
> 2017/12/22 10:06:38 -05:00 6374 0.0.0.0: osad/jabber_lib.connect('Server
> did not return a  stanza, reconnecting',)
>
> 2017/12/22 10:06:39 -05:00 6374 0.0.0.0: osad/jabber_lib.connect('ERROR',
> 'Not able to reconnect - See https://access.redhat.com/solutions/45332
> for possible solutions.\n')
>
> 2017/12/22 10:06:39 -05:00 6374 0.0.0.0: osad/jabber_lib.print_message(
> 'SSLError',)
>
> 2017/12/22 10:06:39 -05:00 6374 0.0.0.0: osad/jabber_lib.print_message('Could
> not connect to jabber server', 'SNCFGSPWD01S.stifelnet.stifel.local')
>
> 2017/12/22 10:06:39 -05:00 6374 0.0.0.0: osad/jabber_lib.main('ERROR',
> 'Error caught:')
>
>
>
> rhn.conf:
>
> # OSA configuration #
>
>
>
> server.jabber_server = SNCFGSPWD01S.stifelnet.stifel.local
>
> osa-dispatcher.jabber_server = SNCFGSPWD01S.stifelnet.stifel.local
>
>
>
> # set up SSL on the dispatcher
>
> osa-dispatcher.osa_ssl_cert = /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT
>
>
>
> # system snapshots enabled
>
> enable_snapshots = 1
>
>
>
> #cobbler host name
>
> cobbler.host = SNCFGSPWD01S.stifelnet.stifel.local
>
>
>
>
>
> SSL subjects:
>
> [root@SNCFGSPWD01S ~]# grep CN= /etc/pki/spacewalk/jabberd/server.pem |
> grep Subject
>
> Subject: C=US, ST=MO, O=Stifel, 
> OU=SNCFGSPWD01S.stifelnet.stifel.local,
> CN=SNCFGSPWD01S.stifelnet.stifel.local/emailAddress=ada...@stifel.com
>
> [root@SNCFGSPWD01S ~]# grep CN= $(grep spacewalk.crt
> /etc/httpd/conf.d/ssl.conf | cut -f 2 -d' ') | grep Subject
>
> Subject: C=US, ST=MO, O=Stifel, 
> OU=SNCFGSPWD01S.stifelnet.stifel.local,
> CN=SNCFGSPWD01S.stifelnet.stifel.local/emailAddress=ada...@stifel.com
>
>
>
>
>
> Jabber configs:
>
> [root@SNCFGSPWD01S ~]# grep $(hostname) /etc/jabberd/*xml
>
> /etc/jabberd/c2s.xml: pemfile="/etc/pki/spacewalk/jabberd/server.pem" realm=""
> register-enable="true">SNCFGSPWD01S.stifelnet.stifel.local
>
> /etc/jabberd/sm.xml:  SNCFGSPWD01S.stifelnet.stifel.local
>
> /etc/jabberd/sm.xml:SNCFGSPWD01S.stifelnet.stifel.local
>
> /etc/jabberd/sm.xml:SNCFGSPWD01S.stifelnet.stifel.local
>
> [root@SNCFGSPWD01S ~]# grep require-starttls /etc/jabberd/c2s.xml | grep
> pemfile
>
>  pemfile="/etc/pki/spacewalk/jabberd/server.pem"
> realm="" register-enable="true">SNCFGSPWD01S.stifelnet.stifel.local
>
>
>
>
>
> Thanks!
>
>
>
>
>
> [image: new_sig]
>
> [image: stifel-sig]
>
>
>
> *From:* spacewalk-list-boun...@redhat.com [mailto:spacewalk-list-bounces
> @redhat.com] *On Behalf Of *Vipul Sharma (DevOps)
> *Sent:* Friday, December 22, 2017 9:56 AM
> *To:* spacewalk-list@redhat.com
> *Subject:* Re: [Spacewalk-list] osa-dispatcher fails to start with null
> ssl error
>
>
>
> Some pointers -
>
>- Your hostname should match your FQDN -
>- Compare your SSL certs between /var/jabberd/server.pem &
>/etc/pki/spacewalk/server.pem - They should be same.
>- CN & OU should be your FQDN in your .crt & .pem files.
>
> Thanks
>
> Vipul
>
>
>
>
>
> On Fri, Dec 22, 2017 at 8:29 PM, Adams, Nick <ada...@stifel.com> wrote:
>
> All,
>
>
>
> I have ran into what I hope is a simp

Re: [Spacewalk-list] osa-dispatcher fails to start with null ssl error

2017-12-22 Thread Adams , Nick 
Thanks Vipul for the quick reply! I’ve updated the hostname to be an fqdn that 
is resolvable via DNS, though the same error still persists.

Please see the following changes:
[root@SNCFGSPWD01S ~]# cat /etc/hostname
SNCFGSPWD01S.stifelnet.stifel.local

Osa-dispatcher.log:
2017/12/22 10:06:36 -05:00 6374 0.0.0.0: osad/jabber_lib.__init__
2017/12/22 10:06:36 -05:00 6374 0.0.0.0: osad/jabber_lib.connect('Server did 
not return a  stanza, reconnecting',)
2017/12/22 10:06:37 -05:00 6374 0.0.0.0: osad/jabber_lib.connect('Server did 
not return a  stanza, reconnecting',)
2017/12/22 10:06:38 -05:00 6374 0.0.0.0: osad/jabber_lib.connect('Server did 
not return a  stanza, reconnecting',)
2017/12/22 10:06:39 -05:00 6374 0.0.0.0: osad/jabber_lib.connect('ERROR', 'Not 
able to reconnect - See https://access.redhat.com/solutions/45332 for possible 
solutions.\n')
2017/12/22 10:06:39 -05:00 6374 0.0.0.0: 
osad/jabber_lib.print_message('SSLError',)
2017/12/22 10:06:39 -05:00 6374 0.0.0.0: osad/jabber_lib.print_message('Could 
not connect to jabber server', 'SNCFGSPWD01S.stifelnet.stifel.local')
2017/12/22 10:06:39 -05:00 6374 0.0.0.0: osad/jabber_lib.main('ERROR', 'Error 
caught:')

rhn.conf:
# OSA configuration #

server.jabber_server = SNCFGSPWD01S.stifelnet.stifel.local
osa-dispatcher.jabber_server = SNCFGSPWD01S.stifelnet.stifel.local

# set up SSL on the dispatcher
osa-dispatcher.osa_ssl_cert = /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT

# system snapshots enabled
enable_snapshots = 1

#cobbler host name
cobbler.host = SNCFGSPWD01S.stifelnet.stifel.local


SSL subjects:
[root@SNCFGSPWD01S ~]# grep CN= /etc/pki/spacewalk/jabberd/server.pem | grep 
Subject
Subject: C=US, ST=MO, O=Stifel, OU=SNCFGSPWD01S.stifelnet.stifel.local, 
CN=SNCFGSPWD01S.stifelnet.stifel.local/emailAddress=ada...@stifel.com
[root@SNCFGSPWD01S ~]# grep CN= $(grep spacewalk.crt /etc/httpd/conf.d/ssl.conf 
| cut -f 2 -d' ') | grep Subject
Subject: C=US, ST=MO, O=Stifel, OU=SNCFGSPWD01S.stifelnet.stifel.local, 
CN=SNCFGSPWD01S.stifelnet.stifel.local/emailAddress=ada...@stifel.com


Jabber configs:
[root@SNCFGSPWD01S ~]# grep $(hostname) /etc/jabberd/*xml
/etc/jabberd/c2s.xml:SNCFGSPWD01S.stifelnet.stifel.local
/etc/jabberd/sm.xml:  SNCFGSPWD01S.stifelnet.stifel.local
/etc/jabberd/sm.xml:SNCFGSPWD01S.stifelnet.stifel.local
/etc/jabberd/sm.xml:SNCFGSPWD01S.stifelnet.stifel.local
[root@SNCFGSPWD01S ~]# grep require-starttls /etc/jabberd/c2s.xml | grep pemfile
SNCFGSPWD01S.stifelnet.stifel.local


Thanks!


[new_sig]
[stifel-sig]

From: spacewalk-list-boun...@redhat.com 
[mailto:spacewalk-list-boun...@redhat.com] On Behalf Of Vipul Sharma (DevOps)
Sent: Friday, December 22, 2017 9:56 AM
To: spacewalk-list@redhat.com
Subject: Re: [Spacewalk-list] osa-dispatcher fails to start with null ssl error

Some pointers -

  *   Your hostname should match your FQDN -
  *   Compare your SSL certs between /var/jabberd/server.pem & 
/etc/pki/spacewalk/server.pem - They should be same.
  *   CN & OU should be your FQDN in your .crt & .pem files.

Thanks

Vipul


On Fri, Dec 22, 2017 at 8:29 PM, Adams, Nick 
<ada...@stifel.com<mailto:ada...@stifel.com>> wrote:
All,

I have ran into what I hope is a simple misconfiguration during setup. I am 
unable to start the osa-dispatcher service:

[root@SNCFGSPWD01S ~]# spacewalk-service restart
Shutting down spacewalk services...
Redirecting to /bin/systemctl stop taskomatic.service
Stopping cobblerd (via systemctl): [  OK  ]
Redirecting to /bin/systemctl stop rhn-search.service
Redirecting to /bin/systemctl stop osa-dispatcher.service
Redirecting to /bin/systemctl stop httpd.service
Redirecting to /bin/systemctl stop tomcat.service
Redirecting to /bin/systemctl stop jabberd.service
Done.
Starting spacewalk services...
Redirecting to /bin/systemctl start jabberd.service
Redirecting to /bin/systemctl start tomcat.service
Waiting for tomcat to be ready ...
Redirecting to /bin/systemctl start httpd.service
Redirecting to /bin/systemctl start osa-dispatcher.service
Job for osa-dispatcher.service failed because the control process exited with 
error code. See "systemctl status osa-dispatcher.service" and "journalctl -xe" 
for details.
Redirecting to /bin/systemctl start rhn-search.service
Starting cobblerd (via systemctl): [  OK  ]
Redirecting to /bin/systemctl start taskomatic.service
Done.

When reviewing the osa-dispatcher log:
2017/12/21 13:30:36 -05:00 3040 0.0.0.0<http://0.0.0.0>: 
osad/jabber_lib.__init__
2017/12/21 13:30:36 -05:00 3040 0.0.0.0<http://0.0.0.0>: 
osad/jabber_lib.connect('Server did not return a  stanza, 
reconnecting',)
2017/12/21 13:30:37 -05:00 3040 0.0.0.0<http://0.0.0.0>: 
osad/jabber_lib.connect('Server did not return a  stanza, 
reconnecting',)
2017/12/21 13:30:38 -05:00 3040 0.0.0.0<http://0.0.0.0>: 
osad/jabber_lib.connect('Server did not return a  s

Re: [Spacewalk-list] osa-dispatcher fails to start with null ssl error

2017-12-22 Thread Vipul Sharma (DevOps) 
Some pointers -


   - Your hostname should match your FQDN -
   - Compare your SSL certs between /var/jabberd/server.pem &
   /etc/pki/spacewalk/server.pem - They should be same.
   - CN & OU should be your FQDN in your .crt & .pem files.

Thanks

Vipul


On Fri, Dec 22, 2017 at 8:29 PM, Adams, Nick  wrote:

> All,
>
>
>
> I have ran into what I hope is a simple misconfiguration during setup. I
> am unable to start the osa-dispatcher service:
>
>
>
> [root@SNCFGSPWD01S ~]# spacewalk-service restart
>
> Shutting down spacewalk services...
>
> Redirecting to /bin/systemctl stop taskomatic.service
>
> Stopping cobblerd (via systemctl): [  OK  ]
>
> Redirecting to /bin/systemctl stop rhn-search.service
>
> Redirecting to /bin/systemctl stop osa-dispatcher.service
>
> Redirecting to /bin/systemctl stop httpd.service
>
> Redirecting to /bin/systemctl stop tomcat.service
>
> Redirecting to /bin/systemctl stop jabberd.service
>
> Done.
>
> Starting spacewalk services...
>
> Redirecting to /bin/systemctl start jabberd.service
>
> Redirecting to /bin/systemctl start tomcat.service
>
> Waiting for tomcat to be ready ...
>
> Redirecting to /bin/systemctl start httpd.service
>
> Redirecting to /bin/systemctl start osa-dispatcher.service
>
> Job for osa-dispatcher.service failed because the control process exited
> with error code. See "systemctl status osa-dispatcher.service" and
> "journalctl -xe" for details.
>
> Redirecting to /bin/systemctl start rhn-search.service
>
> Starting cobblerd (via systemctl): [  OK  ]
>
> Redirecting to /bin/systemctl start taskomatic.service
>
> Done.
>
>
>
> When reviewing the osa-dispatcher log:
>
> 2017/12/21 13:30:36 -05:00 3040 0.0.0.0: osad/jabber_lib.__init__
>
> 2017/12/21 13:30:36 -05:00 3040 0.0.0.0: osad/jabber_lib.connect('Server
> did not return a  stanza, reconnecting',)
>
> 2017/12/21 13:30:37 -05:00 3040 0.0.0.0: osad/jabber_lib.connect('Server
> did not return a  stanza, reconnecting',)
>
> 2017/12/21 13:30:38 -05:00 3040 0.0.0.0: osad/jabber_lib.connect('Server
> did not return a  stanza, reconnecting',)
>
> 2017/12/21 13:30:39 -05:00 3040 0.0.0.0: osad/jabber_lib.connect('ERROR',
> 'Not able to reconnect - See https://access.redhat.com/solutions/45332
> for possible solutions.\n')
>
> 2017/12/21 13:30:39 -05:00 3040 0.0.0.0: osad/jabber_lib.print_message(
> 'SSLError',)
>
> 2017/12/21 13:30:39 -05:00 3040 0.0.0.0: osad/jabber_lib.print_message('Could
> not connect to jabber server', 'SNCFGSPWD01S')
>
> 2017/12/21 13:30:39 -05:00 3040 0.0.0.0: osad/jabber_lib.main('ERROR',
> 'Error caught:')
>
>
>
> Some Jabber specific configs:
>
> [root@SNCFGSPWD01S ~]# grep $(hostname) /etc/jabberd/*xml
>
> /etc/jabberd/c2s.xml: pemfile="/etc/pki/spacewalk/jabberd/server.pem" realm=""
> register-enable="true">SNCFGSPWD01S
>
> /etc/jabberd/sm.xml:  SNCFGSPWD01S
>
> /etc/jabberd/sm.xml:SNCFGSPWD01S
>
> /etc/jabberd/sm.xml:SNCFGSPWD01S
>
> /etc/jabberd/sm.xml:SNCFGSPWD01S
>
> /etc/jabberd/sm.xml:SNCFGSPWD01S
>
> /etc/jabberd/sm.xml:SNCFGSPWD01S
>
> /etc/jabberd/sm.xml:SNCFGSPWD01S
>
>
>
>
>
> Seeing as this is an SSL error, makes sense to include these:
>
> [root@SNCFGSPWD01S ~]# grep CN= $(grep spacewalk.crt
> /etc/httpd/conf.d/ssl.conf | cut -f 2 -d' ') | grep Subject
>
> Subject: C=US, ST=MO, O=Stifel, OU=SNCFGSPWD01S,
> CN=SNCFGSPWD01S/emailAddress=ada...@stifel.com
>
> [root@SNCFGSPWD01S ~]# grep CN= /etc/pki/spacewalk/jabberd/server.pem |
> grep Subject
>
> Subject: C=US, ST=MO, O=Stifel, OU=SNCFGSPWD01S,
> CN=SNCFGSPWD01S/emailAddress=ada...@stifel.com
>
>
>
>
>
> The OSA configuration portion of rhn.conf:
>
> # OSA configuration #
>
>
>
> server.jabber_server = SNCFGSPWD01S
>
> osa-dispatcher.jabber_server = SNCFGSPWD01S
>
>
>
> # set up SSL on the dispatcher
>
> osa-dispatcher.osa_ssl_cert = /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT
>
>
>
> # system snapshots enabled
>
> enable_snapshots = 1
>
>
>
> #cobbler host name
>
> cobbler.host = SNCFGSPWD01S
>
>
>
>
>
>
>
> And finally the contents of the up2date.conf:
>
> # Red Hat Update Agent config file.
>
> # Format: 1.0
>
>
>
> debug[comment]=Whether or not debugging is enabled
>
> debug=0
>
>
>
> systemIdPath[comment]=Location of system id
>
> systemIdPath=/etc/sysconfig/rhn/systemid
>
>
>
> serverURL[comment]=Remote server URL (use FQDN)
>
> serverURL=https://sncfgspwd01s/XMLRPC
>
>
>
> hostedWhitelist[comment]=RHN Hosted URL's
>
> hostedWhitelist=
>
>
>
> enableProxy[comment]=Use a HTTP Proxy
>
> enableProxy=0
>
>
>
> versionOverride[comment]=Override the automatically determined system
> version
>
> versionOverride=
>
>
>
> httpProxy[comment]=HTTP proxy in host:port format, e.g.
> squid.redhat.com:3128
>
> httpProxy=
>
>
>
> noReboot[comment]=Disable the reboot actions
>
> noReboot=0
>
>
>
> networkRetries[comment]=Number of attempts to make at network connections
> before giving up
>
> networkRetries=1
>
>
>
>