The short answer is no.
The most common problem that causes this is a severe time and or date offset between the server an the host. The way to fix that is ntp.
The second is a hostname resolution mismatch. The easiest way to work around this is if you don't have full forward and reverse controls of the lookup you can set the host name as the up address and that will fool the openssl libraries into acting the way you want. And there is a series of well documented commands you need to run to rename the host in spacewalk and make new self signed certs to make that work
The third scenario is you didn't answer the questions properly during the install and it defaulted to the hostname but not the FQDN in other words the hostname without the domain. Essentially in that case you need to recreate the self signed certs with the FQDN
-- Sent from my HP Pre3
On Aug 18, 2013 17:58, Diego Fernández Durán <[email protected]> wrote:
Hi,
I've installed and configured Spacewalk on Fedora 19. The WebUI is
running correctly.
When I try to use rhnpush to put a new package I get the following
error:
[root@localhost ~]# rhnpush --verbose --nosig
--channel=debian_amd64_wheezy vim_7.4.000-1_amd64.deb
Connecting to https://localhost/APP
Username: admin
Password:
ERROR: unhandled exception occurred: ([('SSL routines',
'SSL3_GET_SERVER_CERTIFICATE', 'certificate verify failed')]).
This problem seems related to the self signed certificate Apache is
using. Is there any way to tell rhnpush to do not verify the
certificate?
Thanks in advance.
--
Diego F. Durán <[email protected]> | http://www.goedi.net
GPG : 925C 9A21 7A11 3B13 6E43 50DB F579 D119 90D2 66BB
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
