Building 19.2 for arm

[Karl Cunningham]

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

[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

[Andreas Rogge]

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...@googlegroups.com
> <mailto:bareos-users...@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 andrea...@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

[Karl Cunningham]

Hi Andreas,

Thanks for the comments. I would like to work on packaging for ARM, but I've never done that before. I welcome the challenge and (with some help, I'm sure) may be able to get somewhere. I'll let you know when I need help.

Karl

[W. L.]

Hi Karl,

is it possible for you to send me the packages

 - bareos-filedaemon

 - bareos-common

so I can use them on my raspberry?

I tried to compile bareos on raspberry but unfortunately it failed.
Otherwise I would be happy if you'd send me a description of how to build bareos 19.2 on arm.

Regards
W.L.

[Karl Cunningham]

Hello Will,

Sorry it took so long to get back to you.

I've attached the bareos executables as a tarball. They should go in
/usr/local/sbin/
I've also attached the bareos libraries as a tarball This contains a lot
of stuff I haven't looked into. This should be extracted into
/usr/local/lib/. When you're done there should be a directory:
/usr/local/lib/bareos.
But there is also the matter of creating the bareos user and group, the
systemd unit files, and creating the bareos config files. I think there
are scripts under /usr/local/lib/bareos to do all this but I haven't
tried to figure out how it all works.

If you try compiling yourself, here are my notes from compiling bareos
on a Raspberry Pi. I think this may work for you as well. Start out in a
suitable directory where you want to build the file daemon.

Run the following commands...
sudo apt install build-essential cmake libreadline-dev libssl-dev
liblzo2-dev libacl1-dev
git clone https://github.com/bareos/bareos.git
cd bareos
mkdir build
cd build
cmake -Dclient-only=yes -Dconfdir=/etc/bareos ../bareos
      The cmake option -Dconfdir=/etc/bareos makes the bareos client
look in /etc/bareos for its config files
make
sudo make install

I've also attached a shell script to do a number of things to configure
the client. The script must be run as root, so please look this over to
make sure it's doing what you want. I think script probably does
approximately what installing a repo package would do, but here the
execuable ends up in /usr/local/sbin rather than /usr/sbin, where the
debian/ubuntu package puts it. There are passwords in this script that
will need to be changed for the particular installation and client. This
stuff could easily be done by something like ansible instead.

If you have any questions or problems, please don't hesitate to ask.

Karl

>>> Bareos GmbH & Co. KG Phone: +49 221-630693-86 <+49%20221%2063069386>

[W. L.]

Hi Karl,
thanks a lot.

I will try in the next days.

best regards
Willi