I found the problem. I was putting configs into /etc/bareos but building with the default config directory /usr/local/etc/bareos Sorry for the confusion. Karl
On Friday, September 18, 2020 at 11:41:35 AM UTC-7 Karl Cunningham wrote: > Hello, > > I'm trying to get a 19.2 client to work on a Raspberry Pi running Raspian > buster. I successfully compiled the 19.2 client, but a connection from the > director failed with the usual message: > Connecting to Client sp0-fd at sp0.xxxxxxxx.com:9102 > Probing client protocol... (result will be saved until config reload) > Failed to connect to Client sp0-fd. > ==== > *messages > 18-Sep 09:14 bareos-dir JobId 0: Fatal error: Authorization key rejected > bareos-dir. > 18-Sep 09:14 bareos-dir JobId 0: Fatal error: Unable to authenticate with > File daemon at "sp0.xxxxxxxx.com:9102". Possible causes: > Passwords or names not the same or > TLS negotiation failed or > Maximum Concurrent Jobs exceeded on the FD or > FD networking messed up (restart daemon). > > I disabled TLS on the director and client, but that didn't seem to make a > difference. > Connection from the director to a freshly-compiled amd64 client works fine. > I installed the 16.2 client from the Raspbian repo and the director was > able to connect, but I'd like to use 19.2 since that's what is on other > client machines. > Is there a known issue building the client on arm? > > Thanks for your help. > Karl -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/46506360-b462-4062-8f3c-6639960abfddn%40googlegroups.com.
