You're right. I mistakenly reduced this in the storage daemon configuration. Thanks a lot!
> On Monday, May 6, 2019 at 4:07:32 PM UTC+3, Steffen Knauf wrote: > > Hi all, > > > > sometimes we get the following Error Message during a Backup: > > > > ------------------------------------- > > 05-May 13:43 XXX-dir JobId 0: Fatal error: Authorization key > > rejected > > by Storage daemon superloader. > > 05-May 13:43 XXX-dir JobId 0: Fatal error: Director unable to > > authenticate with Storage daemon at "XXX: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). > > ------------------------------------- > > > > All quequed Jobs will be terminated. superloader is a LTO5 Tape > > Library. If i restart the Jobs all running jobs go through > > perfectly. > > DaemonStorage and Director are on the same Host, the Password isn't > > the > > Problem, too. > > We use Bareos 17.2.7. Any suggestions to debug this? Thanks! > > > > greets > > > > Steffen > > I got this message when mistakenly reduced "Maximum Concurrent Jobs" > in storage daemon configuration. The limit, if you want implement, > should be configured on device level. The original limit of 20 > concurrent jobs for storage daemon is good. > -- 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 post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
