Am Donnerstag, 3. Januar 2008 schrieb Landon Fuller: > On Jan 3, 2008, at 07:49, Sven Carstens wrote: > > 03-Jan 16:12 epistaxis-dir: ERROR in openssl.c:74 Connect failure: > > ERR=error:14094410:SSL routines:SSL3_READ_BYTES:sslv3 alert > > handshake failure > > 03-Jan 16:12 epistaxis-dir: *Console*.2008-01-03_16.12.28 Fatal > > error: TLS negotiation failed with FD on "[Hostname]:9102". > > > > FD and DIR are running 2.0.3. > > A connection with openssl s_client/s_server and the relevant key/ > > dir/CA files as used by the bacula configuration > > is working perfectly. > > Do you have the log from the File Daemon? It will explain why it > dropped the connection. > > -landonf
I configured file logging for the FD and finally get a message: 04-Jan 07:31 [Hostname]-fd: ERROR in openssl.c:74 Connect failure: ERR=error:140890C7:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:peer did not return a certificate If the cert/key was not readable on the DIR side, it would log an error while starting. At least it did while the cert/key was only 600 root.root . Any hints beside the obvious that the cert/key are not readable by the DIR ? CU Sven ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
