Hello.
Thanks Ana for your Helping.
I solve add:
Autoselect = no
On configuration Devices that is bad.
Regards.
On Sun, Jul 16, 2017 at 8:00 PM, Ana Emília M. Arruda <
emiliaarr...@gmail.com> wrote:
> Hello Jose Alberto,
>
> Could you please send to us the configuration used for both ta
Hello Wanderlei,
Please see below ...
On 07/17/2017 03:07 PM, Wanderlei
Huttel wrote:
Hello Kern
- For messages I was not aware
there is any level. You will need to be more explicit.
In my Message
reso
Hi Ana,
Thanks for your thoughts! I thought I was using a safe approach to device
configuration, but your comments make me rethink this. I will revisit this
today. Much appreciated.
Thanks so much,
---
Luke Salsich
On Sun, Jul 16, 2017 at 8:48 PM, Ana Emília M. Arruda <
emiliaarr..
Hello Kern
- For messages I was not aware there is any level. You will need to be more
explicit.
In my Message resource I have configured what messages I want to receive,
in this case (all and !skipped)
..
MailCommand = "/usr/sbin/bsmtp -h localhost -f \"Bacula \"
-s \"Bacula: %t %e of %c %l\" %r"
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 Wanderlei,
Concerning the other things:
- For messages I was not aware there is any level. You will need
to be more explicit.
- For the ports, please show me an example as there is no need to
print it unless it has changed.
- Concerning listing the text.
Hello Kern
Thanks for your answer
Did you see the entire email?
There are more about Messages resource, about (DIRport, SDPort and
FDPort), and about text format.
Best Regards
*Wanderlei Hüttel*
http://www.huttel.com.br
2017-07-15 12:39 GMT-03:00 Kern Sibbald :
> Hello Wanderlei,
>
> Yes it
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
