On 11/30/12 04:40, lst_ho...@kwsoft.de wrote:
>
> Zitat von Phil Stracchino <ala...@metrocast.net>:
>
>> On 11/29/12 16:45, lst_ho...@kwsoft.de wrote:
>>> Try with another NIC. We first had problems with our Bacula Server
>>> failing two clients out of ~20 with connection failures randomly.
>>> After ditching the Onboard GE (Marvell PHY) and using a PCIe NIC on
>>> the Server the problem went away.
>>
>> I had similar problems at one point with an nVidia nForce chipset NIC,
>> until I discovered the magic configuration trick to fix the problem.
>> Once I figured that out, the problem went away for good.
>
> So what was the trick??
I'd have to dig it up again ... all I remember is that it was an
obscure setting I had to tweak somewhere in the nForce4 BIOS, and I
don't remember for sure at this point what the setting was (though my
vague recollection is some kind of BIOS-level firewall rule was involved).
my point was, there are multiple NIC types that may have issues like
this, but it doesn't *necessarily* mean you have to stop using the
affected NIC - you may be able to just tune or patch the problem away.
You need to research the issue for your specific hardware.
--
Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355
ala...@caerllewys.net ala...@metrocast.net p...@co.ordinate.org
Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater
It's not the years, it's the mileage.
------------------------------------------------------------------------------
Keep yourself connected to Go Parallel:
TUNE You got it built. Now make it sing. Tune shows you how.
http://goparallel.sourceforge.net
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
