Skip to content

Job won't run, get "No authorization" connecting to client

Summary

Reproducibility Platform OS OS Version Product Version
always Linux RHEL 9 11.0.1

Description

When I try to run a job from the Bacula console (CLI), I get: No authorization. Client "server.example.com-fd". Job not run. (I substituted "example" for our actual server name.)

The "Director" section in the bacula-fd.conf file has the password set correctly, matching the one in bacula-dir.conf for the "Client" section (see below). So I don't get why it won't authorize.

Thanks for any help.

Steps to Reproduce

  1. open bconsole
  2. run

Additional Information

config files:

bacula-fd.conf:

# Cloud Director
Director {
  Name = dir.clouddir
  Password = "<pw>"
}

#
# File daemon configuration specifications
#
FileDaemon {
  Name = server.example.com-fd
  FDport = 9102
  WorkingDirectory = /var/lib/bacula
  Pid Directory = /var/run
  Maximum Concurrent Jobs = 8
  Plugin Directory = /usr/lib/bacula
}

# Send all messages back to Director
Messages {
  Name = Standard
  director = backup-dir = all
}

bacula-dir.conf (Client section):

Client {
  Name = server.example.com-fd  # The file daemon name of the client
  Address = 127.0.0.1
  FDPort = 9102
  Catalog = MyCatalog
  Password = "<pw>"
  File Retention = 1 year
  Job Retention = 1 year
  AutoPrune = yes
}