Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

During long running jobs my File daemon dies with Pipe Error, or some other communications error. Why?

0
Posted

During long running jobs my File daemon dies with Pipe Error, or some other communications error. Why?

0

There are a number of reasons why a connection might break. Most often, it is a router between your two computers that times out inactive lines (not respecting the keepalive feature that Bacula uses). In that case, you can use the Heartbeat Interval directive in both the Storage daemon and the File daemon. In at least one case, the problem has been a bad driver for a Win32 NVidia NForce 3 ethernet card with driver (4.4.2 17/05/2004). In this case, a good driver is (4.8.2.0 06/04/2005). Moral of the story, make sure you have the latest ethernet drivers loaded, or use the following workaround as suggested by Thomas Simmons for Win32 machines: Browse to: Start > Control Panel > Network Connections Right click the connection for the nvidia adapter and select properties. Under the General tab, click “Configure…”. Under the Advanced tab set “Checksum Offload” to disabled and click OK to save the change. Lack of communications, or communications that get interrupted can also be caused by Li

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123