Re: [Bacula-users] Backup fails after update to 9.0.0

Hello Uwe,

My best guess is that for some reason, your Director may not have lz4properly built, so it does not support the new Bacula comm linecompression, and on the client that failed, it is doing comm linecompression. That is typically with version 9.0 what leads to thepacket size being too big. One way to test this is to explicitly set:


  CommCompression = no

In your Client resource.

You can also try setting the same directive in the bacula-dir.conf forthe Director resource.

If you still have problems, I would like to see exactly what Baculaversion, hardware (32bit/64bit, CPU architecture, ...), and OS theclient is running.


Best regards,

Kern


On 07/17/2017 11:38 AM, Uwe Schuerkamp wrote:

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 deniolXXXXX-dir JobId 0: Fatal error: bsock.c:569 Packet
size=1073741835 too big from "Client: YYYY-fd:YYYY:9102. Terminating connection.

I've compiled 9.0.0 from source (CentOS 6 running on all servers).

Any idea what could be causing this? Many thanks in advance for your
comments & suggestions,

Uwe



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users