Hello,
I have a Bacula setup running with 1 SD, 1 DIR and 50 clients (FDs), i have
Bacula version 2.4.0
Since a white ago i started to receive authorization errors, but they appear
from time to time.
I read http://www.bacula.org/rel-manual/faq.html#AuthorizationErrors , i
increased the Maximum Concurrent Jobs to 30 in the DIR and SD but still this
errors appear from time to time, and they appear on different clients .
I have two dns servers which are master and slave for the zone i'm using on the
clients so it shouldn't be a matter in this case.

The error i receive is:

03-Dec 23:12 server1-fd JobId 7319: Fatal error: Authorization key rejected by
Storage daemon.
Please see http://www.bacula.org/rel-manual/faq.html#AuthorizationErrors for 
help.
03-Dec 23:12 server1-fd JobId 7319: Fatal error: Failed to authenticate Storage
daemon.
03-Dec 23:12 backup-dir JobId 7319: Fatal error: Socket error on Storage
command: ERR=No data available
03-Dec 23:12 backup-dir JobId 7319: Error: Bacula backup-dir 2.4.0 (04Jun08):
03-Dec-2008 23:12:24
  Build OS:               x86_64-pc-linux-gnu debian 4.0
  JobId:                  7319
  Job:                    server1-server-custom.2008-12-03_23.00.54
  Backup Level:           Incremental, since=2008-12-01 23:00:13
  Client:                 "server1-fd" 2.4.0 (04Jun08) 
i486-pc-linux-gnu,debian,4.0
  FileSet:                "server1-server-custom" 2008-08-01 09:13:27
  Pool:                   "daily_incr_custom" (From Run pool override)
  Storage:                "File2c" (From run override)
  Scheduled time:         03-Dec-2008 23:00:00
  Start time:             03-Dec-2008 23:00:00
  End time:               03-Dec-2008 23:12:24
  Elapsed time:           12 mins 24 secs
  Priority:               9
  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
  Storage Encryption:     no
  Volume name(s):
  Volume Session Id:      375
  Volume Session Time:    1227866144
  Last Volume Bytes:      28,685,554 (28.68 MB)
  Non-fatal FD errors:    0
  SD Errors:              0
  FD termination status:
  SD termination status:  Waiting on FD
  Termination:            *** Backup Error ***


In the SD log i can see the following:

03-Dec 23:02 backup-sd JobId 0: Fatal error: job.c:225 FD connect failed: Job
name not found: server1-server-custom.2008-12-03_23.00.54

The  config on the DIR in the Director section contains:

Director {
  Name = backup-dir
  Description = "Bacula Director"
  DIRport = 9101
  QueryFile = "/etc/bacula/scripts/query.sql"
  WorkingDirectory = "/var/lib/bacula"
  PidDirectory = "/var/run/bacula"
  Maximum Concurrent Jobs = 30
  Password = "arandompassword"
  Messages = Daemon
  DirAddress = 192.168.0.100
  FD Connect Timeout = 5 minutes
  SD Connect Timeout = 5 minutes
  Heartbeat Interval = 30
  TLS Enable = yes
  TLS Require = yes
  TLS Verify Peer = yes
  TLS CA Certificate File = /etc/bacula/certs/ca.crt
  TLS Certificate = /etc/bacula/certs/backup.crt
  TLS Key = /etc/bacula/certs/backup.key
}

Storage definition in the Director conf

Storage {
  Name = file_something
  Address = backup.foo.bar             # N.B. Use a fully qualified name here
  SDPort = 9103
  Password = "m/k3mhFkxEXzQMbLDWXuGGlJgZX9P3j/kB70CoOQr740"
  Device = file_something
  Media Type = file_something
  Maximum Concurrent Jobs = 1
  Heartbeat Interval = 30
  TLS Require = yes
  TLS CA Certificate File = /etc/bacula/certs/ca.crt
  TLS Certificate = /etc/bacula/certs/backup.crt
  TLS Key = /etc/bacula/certs/backup.key
}


The SD conf contains in the Storage section:

Storage {
  Name = backup-sd
  SDPort = 9103
  WorkingDirectory = "/var/lib/bacula"
  Pid Directory = "/var/run/bacula"
  Maximum Concurrent Jobs = 40
  SDAddress = 192.168.0.100
  Client Connect Wait = 30
  TLS Enable = yes
  TLS Require = yes
  TLS CA Certificate File = /etc/bacula/certs/ca.crt
  TLS Certificate = /etc/bacula/certs/backup.crt
  TLS Key = /etc/bacula/certs/backup.key
}


The problem is that i don't see it possible to have 30 concurrent jobs on the SD
due how the setup is made and how many device definitions i have in the SD.conf 
.
The problem appeared when i had Maximum Concurrent Jobs = 10 and increasing to
30 didn't solve the issue as problems still appear. Of course if i want to run
the job manually it's ok and there aren't any issues.

Does anyone know what i'm doing wrong ?


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users