On Dec 16, 2008, at 7:27 AM, Josh Fisher wrote:
> I, and some others on this list, have had similar issues that turned  
> out to be broken ethernet NICs or drivers. Because Bacula expects a  
> rather long duration TCP connection to be maintained between the FD  
> and the SD, it is unforgiving of broken (or intermittently working)  
> network hardware/drivers. The quick and easy attempt at a fix is to  
> replace the NIC in the failing machine. If the problem goes away  
> then you know it is a bad NIC or buggy driver. Since it went from an  
> intermittent problem to a complete failure, my guess is a broken NIC.


This is non-trivial, as the NIC is a motherboard-based broadcom  
interface.  It would require a system swap.

Furthermore, the system being backed up is our main network monitoring  
host.  It spends every minute of every day doing thousands of network  
queries, none of which are failing locally.   If the NIC was failing,  
I am quite positive we would see this in some other way.

Obviously I would be very non-surprised to find that it's a problem in  
the network stack and only visible here because of this machine's  
workload, but I've been trying and trying to find what part of the  
network stack is failing and I can't find anything at all.

-- 
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source  
and other randomness



------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users