View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000953bareos-corefile daemonpublic2018-05-28 16:172019-12-18 15:24
ReporterWebComPas Assigned Toarogge  
PriorityhighSeveritymajorReproducibilityalways
Status closedResolutionwon't fix 
PlatformLinuxOSUbuntuOS Version18.04
Summary0000953: File daemon cannot establish client initiated connection
DescriptionOn Ubuntu 18.04 using Bareos File Daemon 18.2.2-1351.1 the client initiated connection cannot be established. The log contains repeatedly the following message:

lib/crypto_openssl.cc:1561 Connect failure: ERR=error:1408F10B:SSL routines:ssl3_get_record:wrong version number

Using version 17.2.4-9.1 of Ubuntu 16.04 with the same configuration everything is working fine. So I guess this is an error of the new client version.
Steps To Reproduce1. Install Bareos File Daemon 18.2.2-1351.1 on an Ubuntu 18.04 client.
2. Configure it to use client initiated connections and start it.
Additional InformationBareos Director is running version 16.3.1 on Ubuntu 14.04
TagsNo tags attached.

Activities

joergs

joergs

2018-05-29 18:14

developer   ~0003019

What version of the director are you using? If the director is < 18.2 you must set http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveFdDirectorTLS%20Psk%20Enable to no.
arogge

arogge

2019-01-16 17:25

manager   ~0003199

Basically a newer bareos-fd with an older bareos-dir is not a tested setup. With the new TLS-PSK the 18.2 client is not able to talk to pre-18.2 directors in the default configuration.

You can reconfigure the client to not use TLS-PSK, then it might work.

Issue History

Date Modified Username Field Change
2018-05-28 16:17 WebComPas New Issue
2018-05-29 18:14 joergs Note Added: 0003019
2018-05-29 18:15 joergs Status new => feedback
2019-01-16 17:25 arogge Note Added: 0003199
2019-01-16 17:25 arogge Status feedback => resolved
2019-01-16 17:25 arogge Resolution open => won't fix
2019-01-16 17:25 arogge Assigned To => arogge
2019-12-18 15:24 arogge Status resolved => closed