[Spacewalk-list] osad not working with Spacewalk proxy server

Jeremy Davis jdavis4102 at gmail.com
Thu Feb 16 22:53:03 UTC 2012


If a server is connecting to a Spacewalk Proxy server you will need to use
the SSL Cert that was generated for that proxy server. This Cert will be in
the same location as the app server but on the proxy server.

On Thu, Feb 16, 2012 at 2:43 PM, Sean Carolan <scarolan at gmail.com> wrote:

> Maybe one of you have already solved this in the past.  We have a
> master Spacewalk server which is working just fine.  All clients are
> able to contact the jabber server and receive push updates, etc. Our
> proxy server is registered with the master server and is also working
> ok for the most part.  New clients can register and they are showing
> up in the GUI.  So far so good. The problem we're having is that none
> of the clients who are pointed at the proxy server can use osad.  When
> we try to start osad on these machines we get this error:
>
> Traceback caught:
> Traceback (most recent call last):
>  File "/usr/share/rhn/osad/jabber_lib.py", line 610, in connect
>    ssl.do_handshake()
> Error: [('SSL routines', 'SSL3_GET_SERVER_CERTIFICATE', 'certificate
> verify failed')]
>
>                                                           [FAILED]
>
>
> I've googled, scoured through the documentation, and tried fiddling
> with various settings but nothing seems to work.  The dates on all
> three machines (master, proxy, and client) are all set correctly, and
> all using GMT.  Is the proxy server supposed to have a different ssl
> cert for jabber communication?
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20120216/7d416111/attachment.htm>


More information about the Spacewalk-list mailing list