Hi Karl, sound like you did a great job here :)
It is possible to build Debian packages from our master branch using our build configuration. While this will need some ARM-specific changes (e.g. there is no VMware VDDK for ARM) the resulting packages would look mostly like the ones we provide for x86_64. If you want to go the extra mile and make that work, we will happily accept a pull-request. I can also offer some guidance if you get stuck. As a benefit to you (and the rest of the community) building packages for Raspian would work out of the box. Maybe then I could even convince the other devs to add some Raspberry Pis to our continuous integration system and provide Raspian packages in the future :) Best Regards, Andreas Am 21.09.20 um 19:34 schrieb Karl Cunningham: > 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 > <http://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 > <http://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 bareos-users+unsubscr...@googlegroups.com > <mailto:bareos-users+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/bareos-users/46506360-b462-4062-8f3c-6639960abfddn%40googlegroups.com > <https://groups.google.com/d/msgid/bareos-users/46506360-b462-4062-8f3c-6639960abfddn%40googlegroups.com?utm_medium=email&utm_source=footer>. -- Andreas Rogge andreas.ro...@bareos.com Bareos GmbH & Co. KG Phone: +49 221-630693-86 http://www.bareos.com Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: S. Dühr, M. Außendorf, J. Steffens, Philipp Storz -- 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 bareos-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/9c7accba-e84c-b2c8-7651-48b38ecd7123%40bareos.com.
signature.asc
Description: OpenPGP digital signature
