On Mon, Jul 17, 2017 at 12:23:34PM +0200, Kern Sibbald wrote:
> Hello Uwe,
>
> My best guess is that for some reason, your Director may not have lz4
> properly built, so it does not support the new Bacula comm line compression,
> and on the client that failed, it is doing comm line compression. T
Hello Uwe,
My best guess is that for some reason, your Director may not have lz4
properly built, so it does not support the new Bacula comm line
compression, and on the client that failed, it is doing comm line
compression. That is typically with version 9.0 what leads to the
packet size bei
Hi folks,
I recently updated our four bacula servers to 9.0.0. Everything went
rather smoothly except for one job which now fails with the following
error message.
17-Jul 11:35 deniolX-dir JobId 0: Fatal error: bsock.c:569 Packet
size=1073741835 too big from "Client: -fd::9102. Termin
