Distribution EOLE » Modules » Scribe

Question posée sur la liste Bareos :
https://groups.google.com/g/bareos-users/c/pF_CfvoJF5U

On rencontre les erreurs suivantes (voir fichier de log ci-joint) :
ERR=error:1408F119:SSL
ERR=error:14094438:SSL
ERR=error:1409E10F:SSL

Échange sur la liste Bareos
https://groups.google.com/g/bareos-users/c/pF_CfvoJF5U

Ceci semble résoudre le problème, en attente de confirmation au 22.01.2024.

* modifier /etc/bareos/bareos-dir.conf et commenter "Heartbeat Interval = 10" (environ ligne 12)
* modifier /etc/bareos/bareos-fd.conf et commenter "Heartbeat Interval = 10" (environ ligne 19)
* redémarrer les services :
   ** systemctl restart bareos-dir.service
   ** systemctl restart bareos-fd.service

bruno.friedmann [à] bareos.com :

While in most majority of cases you don't need heartbeat, it may necessary
when some firewall drop idled connection after a certain time. This may occur
when the FD is collecting files and didn't send anything to the SD.

I highly recommend to set client to passive mode (will be our default in next 
24 version).

https://docs.bareos.org/TasksAndConcepts/NetworkSetup.html#passive-clients

The normal way of initializing the data channel (the channel where the backup data itself is transported) is done by the Bareos File Daemon (client) that connects to the Bareos Storage Daemon.

In many setups, this can cause problems, as this means that:

• The client must be able to resolve the name of the Bareos Storage Daemon (often not true, you have to do tricks with the hosts file)
• The client must be allowed to create a new connection.
• The client must be able to connect to the Bareos Storage Daemon over the network (often difficult over NAT or Firewall)

By using Passive Client, the initialization of the data channel is reversed, so that the storage daemon connects to the Bareos File Daemon. This solves almost every problem created by firewalls, NAT-gateways and resolving issues, as

• The Bareos Storage Daemon initiates the connection, and thus can pass through the same or similar firewall rules that the director already has to access the Bareos File Daemon.
• The client never initiates any connection, thus can be completely firewalled.
• The client never needs any name resolution and is totally independent from any resolving issues.

To use this feature, just configure Passive (Dir->Client)=yes in the client definition of the Bareos Director:

Enable passive mode in bareos-dir.d/client/myself.conf :

Client {
   Name = client1-fd
   Password = "secretpassword" 
   Passive = yes
   [...]
}