Thanks, Josip! I'll give that a try.
--Shawn
On 3/12/18, 4:29 PM, "Josip Deanovic" wrote:
On Monday 2018-03-12 20:51:40 Shawn Rappaport wrote:
> Thanks! That showed me what the problem was:
> Failed to open Plugin directory /usr/lib64: ERR=No such file or
> directory
>
On Monday 2018-03-12 20:51:40 Shawn Rappaport wrote:
> Thanks! That showed me what the problem was:
> Failed to open Plugin directory /usr/lib64: ERR=No such file or
> directory
>
> To fix it, I simply created a /usr/lib64 directory and copied
> bpipe-fd.so to that directory. Now the client proces
Thanks! That showed me what the problem was:
Failed to open Plugin directory /usr/lib64: ERR=No such file or directory
To fix it, I simply created a /usr/lib64 directory and copied bpipe-fd.so to
that directory. Now the client process starts up and lets me connect via
bconsole.
--Shawn
On 3/1
On Monday 2018-03-12 19:36:58 Shawn Rappaport wrote:
> I installed the 9.0.6 client on an old 32-bit Ubuntu 12.04.4 LTS server.
> The installation went fine and I get no errors if I run
> /sbin/bacula-fd -t -c bacula-fd.conf. However, after starting the
> client, I noticed that the process is not
I installed the 9.0.6 client on an old 32-bit Ubuntu 12.04.4 LTS server. The
installation went fine and I get no errors if I run /sbin/bacula-fd -t -c
bacula-fd.conf. However, after starting the client, I noticed that the process
is not running. Is there some way to debug why the client won’t r
