Bareos emails "*None*" - Director unable to authenticate with Storage daemon

45 views
Skip to first unread message

Joe

unread,
May 15, 2020, 5:49:16 AM5/15/20
to bareos-users
Hi all,

we running Bareos in multiple instances while each is configured the same except for clients, jobs and of course FQDNs / IPs.

We are receiving emails generated by each Bareos instance with the subject *None*: *None* of *None* - *None* (Error).
15-May 04:11 backup01.example.com JobId 0: Fatal error: Director unable to authenticate with Storage daemon at "backup01.example.com:9103". Possible causes:
Passwords or names not the same or
TLS negotiation problem
or
Maximum Concurrent Jobs exceeded on the SD or
SD networking messed up
(restart daemon).

The message is from 04:11 but the email sent was from 08:52. The time I logged into the Bareos WebUI.
These emails are also being sent while jobs are running.

At first I set the connection in bareos-dir->storage to 127.0.0.1 and localhost but that generated way more emails than using an internal FQDN. So that reduced the amount of emails sent.
What is the exact reason for this message, please?

Here is our config (of hopefully all essential parts).

bareos-dir.d/director/backup01.example.com.conf
Director {
   
Name = backup01.example.com
   
Description = The Bareos server
   
Heartbeat Interval = 60
   
Messages = Error
   
Query File = /usr/lib/bareos/scripts/query.sql
   
Maximum Concurrent Jobs = 2
   
Password = <the password>
}

bareos-dir.d/storage/backup01.example.com.conf
Storage {
   
Name = backup01.example.com
   
Address = backup01.example.com
   
Collect Statistics = yes
   
Description = Storage for all backups
   
Device = FileStorage01
   
Device = FileStorage02
   
Device = FileStorage03
   
Device = FileStorage04
   
Device = FileStorage05
   
Device = FileStorage06
   
Device = FileStorage07
   
Device = FileStorage08
   
Device = FileStorage09
   
Device = FileStorage10
   
Media Type = File
    TLS
Allowed CN = backup01.example.com
    TLS CA
Certificate File = /etc/ssl/ca.pem
    TLS
Certificate = /etc/ssl/local/backup01.example.com.crt
    TLS
Enable = yes
    TLS
Key = /etc/ssl/local/backup01.example.com.key
    TLS
Require = yes
    TLS
Verify Peer = no
   
Maximum Concurrent Jobs = 2
   
Password = <the password>
}


bareos-dir.d/messages/Error.conf
Messages {
   
Name = Error
   
Append = "/var/log/bareos/bareos.log" = error, fatal, terminate, notsaved
   
Catalog = info, warning, error, fatal, terminate, notsaved
   
Description = Error messages only
   
Mail Command = "/usr/sbin/bsmtp -h localhost -f \"(Bareos) bar...@example.com\" -s \"\%e: \%t of \%c - \%n (Error)\" \%r"
   
Mail On Error = backup@example.com = error, fatal, terminate, notsaved
}

bareos-sd.d/storage/backup01.example.com.conf
Storage {
   
Name = backup01.example.com
   
Collect Device Statistics = yes
   
Collect Job Statistics = yes
   
Description = Storage for all backups
   
File Device Concurrent Read = yes
   
Messages = Error
    SD
Address = backup01.example.com
    TLS
Allowed CN = backup01.example.com
    TLS CA
Certificate File = /etc/ssl/ca.pem
    TLS
Certificate = /etc/ssl/local/backup01.example.com.crt
    TLS
Enable = yes
    TLS
Key = /etc/ssl/local/backup01.example.com.key
    TLS
Require = yes
    TLS
Verify Peer = no
   
Maximum Concurrent Jobs = 2
}

bareos-sd.d/director/backup01.example.com.conf
Director {
   
Name = backup01.example.com
   
Description = The director which will connect to the storagedaemon
    TLS
Allowed CN = backup01.example.com
    TLS CA
Certificate File = /etc/ssl/ca.pem
    TLS
Certificate = /etc/ssl/local/backup01.example.com.crt
    TLS
Enable = yes
    TLS
Key = /etc/ssl/local/backup01.example.com.key
    TLS
Require = yes
    TLS
Verify Peer = no
   
Password = <the password>
}

Best regards
Joe

Joe

unread,
May 15, 2020, 5:50:48 AM5/15/20
to bareos-users
I forgot to mention that on each Bareos instance we are running more than 100 jobs succeed while only few fails (like 8) each day.

Joe

unread,
May 26, 2020, 12:54:03 AM5/26/20
to bareos-users
Hi all,

What apparently fixed our problem is adding 10 more connections to dir->sd and sd->storage than dir->director has.

Best regards
Joe
Reply all
Reply to author
Forward
0 new messages