On Fri, Nov 12, 2021 at 3:16 PM Heitor Faria wrote:
> Hello They,
>
> Are all the NICs using the same MTU?
>
Yes, all have an MTU of 1500.
> Have you checked for network layer problems?
>
None of the machines involved show any network errors. The network in
between is out of my hands, but it's
David,
Sorry I can't offer a solution, but I can report that am I getting the
same error when trying to run bacula-fd 9.x on Big Sur (hand compiled).
I've tried the other suggestion of Maximum Network Buffer Size to no avail.
Stephen
On 11/12/21 2:14 PM, David Brodbeck wrote:
I'm
Greetings
I am upgrading (reinstalling) a bacula server configured in 2016 which
has been working great all this time, until the machine died...
It appears that the new version of bacula uses a very different paradigm...
Am I correct in interpreting the manual to mean that all tapes with a
Hello They,
Are all the NICs using the same MTU?
Have you checked for network layer problems?
I have no clue regarding your error, but I would try to limit the packet size
with the following FD directive:
Maximum Network Buffer Size =
Rgds.
--
MSc Heitor Faria (Miami/USA)
CEO Bacula LatAm
I'm getting this error trying to back up a macOS client. I recently
re-installed bacula from macports on this client, after an upgrade to macOS
Big Sur.
| russell.math.ucsb.edu-sd JobId 80985: Fatal error: bsock.c:520 Packet
size=1387166 too big from "client:128.111.88.29:62571". Maximum
