26 Úno
2013
26 Úno
'13
14:45
Hello,
I've just installed fred from apt-repository on lucid. Now, when I try
to connect to EPP server using fred-client, I get following error:
ERROR: socket.sslerror: [Errno 1] _ssl.c:480: error:14094418:SSL
routines:SSL3_READ_BYTES:tlsv1 alert unknown ca (10.128.5.195:700)
Certificate not signed by verified certificate authority.
There is (hopefully) no problem with CA trust. Moreover, I can see this
in fred-eppd.log:
CORBA exception: IDL:omg.org/CORBA/COMM_FAILURE:1.0
Could not get greeting data from fred_rifd
Any ideas please?
Regards,
Tomas Mazak
26 Úno
26 Úno
18:34
On Tue, 26 Feb 2013 14:45:16 +0100
Tomas Mazak <tomas.mazak(a)centrumholdings.com> wrote:
Hello,
I've just installed fred from apt-repository on lucid. Now, when I try
to connect to EPP server using fred-client, I get following error:
ERROR: socket.sslerror: [Errno 1] _ssl.c:480: error:14094418:SSL
routines:SSL3_READ_BYTES:tlsv1 alert unknown ca (10.128.5.195:700)
Certificate not signed by verified certificate authority.
There is (hopefully) no problem with CA trust. Moreover, I can see this
in fred-eppd.log:
CORBA exception: IDL:omg.org/CORBA/COMM_FAILURE:1.0
Could not get greeting data from fred_rifd
Any ideas please?
Regards,
Tomas Mazak
Are you using the test certificates included in the fred distribution?. I ask this
because we generated our own CA and certificates. You then, need that both the mod-eppd
module certificates and the fred-client certificates are signed by the same CA, in our
case our own.
Best regards.
--
Mario Guerra <mguerra(a)nic.cr>
27 Úno
27 Úno
11:25
Hello,
thanks for your help Mario. I was able to fix the ssl problem but it
doesn't work anyway. I found out, that probably the problem is that
fred-pyfred is not running. When I try to start the service, it segfaults:
# fred-pyfred
File /etc//fred/pyfred.conf used as config file
Importing modules ['genzone', 'mailer', 'filemanager',
'techcheck']
/usr/lib/pymodules/python2.6/pyfred/utils.py:8: DeprecationWarning: The
popen2 module is deprecated. Use the subprocess module.
import sys, os, fcntl, select, time, popen2, signal
Logging to syslog since now
syslog:
[ 2122.285996] fred-pyfred[1264]: segfault at 0 ip 00007f31fca239c4 sp
00007fff80f5fec0 error 4 in libomniORB4.so.1.4[7f31fc944000+198000]
The same with fred-pifd:
# fred-pifd --daemonize
Segmentation fault
syslog:
[ 2164.335557] fred-pifd[1272]: segfault at 10 ip 00007fdc3904e3c4 sp
00007fff782d7b30 error 4 in libpthread-2.11.1.so[7fdc39045000+18000]
Any ideas please?
Regards,
Tomas Mazak
On 02/26/2013 06:34 PM, Mario Guerra wrote:
On Tue, 26 Feb 2013 14:45:16 +0100
Tomas Mazak <tomas.mazak(a)centrumholdings.com> wrote:
Hello,
I've just installed fred from apt-repository on lucid. Now, when I try
to connect to EPP server using fred-client, I get following error:
ERROR: socket.sslerror: [Errno 1] _ssl.c:480: error:14094418:SSL
routines:SSL3_READ_BYTES:tlsv1 alert unknown ca (10.128.5.195:700)
Certificate not signed by verified certificate authority.
There is (hopefully) no problem with CA trust. Moreover, I can see this
in fred-eppd.log:
CORBA exception: IDL:omg.org/CORBA/COMM_FAILURE:1.0
Could not get greeting data from fred_rifd
Any ideas please?
Regards,
Tomas Mazak
Are you using the test certificates included in the fred
distribution?. I ask this because we generated our own CA and certificates. You then, need
that both the mod-eppd module certificates and the fred-client certificates are signed by
the same CA, in our case our own.
Best regards.
4098
days inactive
4099
days old
2 comments
2 participants
participants (2)
-
Mario Guerra -
Tomas Mazak