On Thursday 04 December 2014 10.06:43 Marco van Wieringen wrote: > Bruno Friedmann <friedmann.bruno <at> gmail.com> writes: > > > > > Okay I'm not a big users of verify, but to be sure about one job I've > > run a Verify VolumeToCatalog > > > > A shorter lap time after the job start I got a > > 02-Dec 15:09 orville-dir JobId 384: Fatal error: bsock.c:546 > > Packet size too big from "Client: > > orville-fd:orville.disney.interne:9102. Terminating connection. > > > > Now due to the fatal error, I'm not able to determine who's wrong > The error you see it because the director receives a message where > the binary header has a value which is out of the allowed range. > > Is this by accident a Windows client ? > > Every message send between the daemons starts with a 32 bits value > which says how long the message is. This value is in network order > but it seems it got corrupted along the way. This was something that > used to happen on windows with crappy network drivers.
Interesting, in fact I've used the internal director client on the dir. But this server has a bond network configuration. bareos 13.2.3 under openSUSE 13.1 64bits The bond mode is "mode=802.3ad miimon=100" enslaving two interfaces (but the interface have different chipset) Intel Gigabit Ethernet controller Kernel modules: e1000e Qualcomm Atheros Gigabit Ethernet controller Kernel modules: alx The communication happened on the bond ip. How can I dig a bit deeper what could raise this issue? -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
