macOS Client fails after Installing the Bareos Client as PKG.

[Jacob Kamminga]

Hi,

I installed the macOS package ( bareos-22.1.1~pre26.eeec2501e.pkg ) on my Intel MacBook Pro running MacOS ( Ventura 13.4.1(c) ) .

- First of all the bareos-fd fails to start. It produces the next message in /var/run/bareos.log:

dyld[63402]: Library not loaded: /usr/local/opt/jansson/lib/libjansson.4.dylib
 Referenced from: <AB046BF2-74E3-3C9D-A8CE-239043797A8A> /usr/local/bareos/sbin/bareos-fd
 Reason: tried: '/usr/local/opt/jansson/lib/libjansson.4.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/opt/jansson/lib/libjansson.4.dylib' (no such file), '/usr/local/opt/jansson/lib/libjansson.4.dylib' (no such file), '/usr/local/lib/libjansson.4.dylib' (no such file), '/usr/lib/libjansson.4.dylib' (no such file, not in dyld cache)

Indicating it cannot find the Jansson dynamic library.

Is the pkg not supposed to install everything?

- Secondly the documentation say to use launch file org.bareos.bareos-fd. 

However the package install com.bareos.bareos-fd

Thanks and regards,

Jacob 

[Jacob Kamminga]

Ok solved it,  documented my solution for other users to find.

I got 3 things to discus:

1)

Downloaded and compiled janson-2.13.

It generates an error when running "make check"  at the "check-TESTS" step. That seems irrelevant, so continued with "sudo make install".

So I have the libjansson.4.dylib library, so bareos-fd should now run.

Not yet another error message in /var/run/bareos-fd.log:

jacbook-fd: ERROR TERMINATION at lib/util.cc:1066
Working Directory: "/usr/local/var/lib/bareos" not found. Cannot continue.

2)

So what is the problem.

The software is installed in /usr/local/bareos. In there are bin, etc, lib, sbin. share and a var subdirectory.

So I found the potential directory in /usr/local/bareos/var/lib/bareos

Created the expected top-level dir and a softlink to the actual dir

% sudo mkdir /usr/local/var/lib

% sudo ln -s ../../bareos/var/lib/bareos ./bareos

3)

I have one last thing, which is documentation.

The documentation states to use:

% sudo launchctl stop com.bareos.bareos-fd

% sudo launchctl start com.bareos.bareos-fd

Which is an obsolete method and doesn't work anymore.

We now need to use this method:

% sudo launchctl kickstart -p system/com.bareos.bareos-fd

 service spawned with pid: 1225

Ok the service is running service and the director can connect to it.

Cheers,

Jacob