Hello World,

I have the following situation:
* 1 Linux Server
  - Debian Linux 11.1
  - has Bareos 20.0.1 installed
  - uses postgresql 13 for the catalog
  - has a data directory to back up
* 3 Windows PCs
  - Windows 10
  - have different directories to back up

I have had a working Bareos 16.4 (from the Debian repository), but I upgraded to Bareos 20 (from the Bareos "Community Repository").

I have installed the "Community Edition" of Bareos 20 on the Debian server.

When I try to start the job to back up the data directory on the server in bconsole I get the following error:

07-Nov 20:25 bareos-dir JobId 15: No prior Full backup Job record found.
07-Nov 20:25 bareos-dir JobId 15: No prior or suitable Full backup found in catalog. Doing FULL backup. 07-Nov 20:25 bareos-dir JobId 15: Start Backup JobId 15, Job=BackupServer.2021-11-07_20.25.24_06 07-Nov 20:25 bareos-dir JobId 15: Fatal error: Connect failure: ERR=error:14094417:SSL routines:ssl3_read_bytes:sslv3 alert illegal parameter
07-Nov 20:25 bareos-dir JobId 15: Fatal error: TLS negotiation failed
07-Nov 20:25 bareos-dir JobId 15: Error: Bareos bareos-dir 20.0.1 (02Mar21):
  Build OS:               Debian GNU/Linux 10 (buster)
  JobId:                  15
  Job:                    BackupServer.2021-11-07_20.25.24_06
  Backup Level:           Full (upgraded from Incremental)
  Client:                 "bareos-fd"
  FileSet:                "LocalData" 2021-11-07 17:39:35
  Pool:                   "Full" (From Job FullPool override)
  Catalog:                "TscharnerMechanikCatalog" (From Client resource)
  Storage:                "USBDisk" (From Job resource)
  Scheduled time:         07-Nov-2021 20:25:20
  Start time:             07-Nov-2021 20:25:26
  End time:               07-Nov-2021 20:25:26
  Elapsed time:           0 secs
  Priority:               10
  FD Files Written:       0
  SD Files Written:       0
  FD Bytes Written:       0 (0 B)
  SD Bytes Written:       0 (0 B)
  Rate:                   0.0 KB/s
  Software Compression:   None
  VSS:                    no
  Encryption:             no
  Accurate:               no
  Volume name(s):
  Volume Session Id:      0
  Volume Session Time:    0
  Last Volume Bytes:      0 (0 B)
  Non-fatal FD errors:    1
  SD Errors:              0
  FD termination status:
  SD termination status:
  FD  Secure Erase Cmd:   <NULL>
  SD  Secure Erase Cmd:   <NULL>
Bareos binary info: bareos.org build: Get official binaries and vendor support on bareos.com
  Job triggered by:       User
  Termination:            *** Backup Error ***


journalctl -xe gives me:

Nov 07 20:25:02 server bconsole[35606]: Connected Director daemon at localhost:9101, encryption: None Nov 07 20:25:26 server bareos-sd[35238]: Connect failure: ERR=error:141FA0FD:SSL routines:tls_psk_do_binder:binder does not verify Nov 07 20:25:26 server bareos-sd[35238]: lib/bnet.cc:124 TLS Negotiation failed.


I have tried to add TLS Enable = no (on the director and all clients) and have also added TLS Require = no (also on director and all clients), but nothing worked.

I have no certificates and hoped the mentioned TLS-PKS would work.

Server: Debian GNU/Linux 11.1: Linux server 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30) x86_64 GNU/Linux

What did I miss? What can I do?

TIA and best regards
        Andreas
--
Andreas Tscharner                                 [email protected]
------------------------------------------------------------------------
Der entscheidende Vorteil eines Chats gegenueber einem normalen Telefon-
anruf ist der, dass ersterer langsamer geht und mehr kostet (fuer den
lebenswichtigen Austausch von Informationen wie "hya folks", "C U
l8er" und ":-)") ...                       Aus Murphy's Computergesetzen

--
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/f0f3d548-d98a-5358-db5e-f5ab5bc42fe3%40gmail.com.

Reply via email to