>Quite a number of network connection drops have been reported in the past even >with heartbeat enabled, particularly with Windows machines, and with one >exception explained below, they have been related to bad network cards often >needing firmware upgrades and to Windows networking problems involving large >buffers (documented in the manual).
The problem has manifested over several virtual and physical NICS from various vendors. I noticed shortly after the time I had an issue on a Proliant that HP released a firmware update for the Broadcoms on it, so I applied it and it never helped. Apologize about the Buffer issue, I now recall reading about that ages ago when I first setup Bacula. It's been set along with a debug on the affected client and I will see how this helps over the next few days. >The one exception to the above, of which I am aware, is that there seems to be >a bug in OpenSSL in not correctly handling interrupted system calls -- this >only occurs with version 5.0.x of Bacula and when running encryption. It is >possible that it is a Bacula bug, but from everything that I have seen it has >to do with the fact that OpenSSL doesn't seem to know to repeat an socket >read/write when an interrupted system call occurs, instead it continues and >eventually dies in a zlib routine. We don't have a fix for this. No encryption used here. Thanks for taking the time to respond, jlc ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
