Am 18.09.2017 um 09:03 schrieb Can Şirin:
It is the same again. It is definitely related with enable-bat
option. Did you compiled it properly with bat?
Yes, bat did compile properly without any additional option - only
--with-mysql --enable-conio --enable-bat.
We use bat via ssh and X11 forwar
Thanks for your advice. Actually it really make sense to look at the spec
file of successfully compiled rpm files. I should have thought about that.
Anyway...
Problem is solved. As I can see from spec file, another configure parameter
(with-x) must be defined to successfully compile the Bacule wi
Hi,
On Mon, Sep 18, 2017 at 9:03 AM, Can Şirin wrote:
> It is the same again. It is definitely related with enable-bat option. Did
> you compiled it properly with bat?
>
> Quoting Ralf Brinkmann :
>
> For a new try I'd set the compile options to a minimum, e.g.:
>
> --with-postgresql
> --enable-
A copy job will communicate using TCP between the Bacula daemons. A bsock
error could indicate that bacula-sd closed the connection unexpectedly and I
would expect media errors to be logged.
Your syslog did include some I/O errors. Any they caused by something else?
Do you have the complete job
It is the same again. It is definitely related with enable-bat option. Did
you compiled it properly with bat?
Quoting Ralf Brinkmann :
For a new try I'd set the compile options to a minimum, e.g.:
--with-postgresql
--enable-conio
--enable-bat
--
Ralf Brinkmann
