Hello,
For some reason bpipe() detects an error when it closes the pipe. Either
the other end has exited prematurely, or possibly the connection was
dropped due to a timeout. If it is the former, you must fix what is
going on at the other end. If it is the latter make sure that you have
the most recent version of 9.2.1, because I updated the core bpipe code
to set keepalive to try to avoid socket timeouts due to inactivity.
Best regards,
Kern
On 09/21/2018 02:40 PM, Heitor Faria wrote:
Hello MArtin,
It seems unlikely to me, except maybe if it affects system performance and
hides other problems.
What is the final "xxxx" in your error message (it should be an error number)?
Yes. This is just an example I got from Internet, but it is pretty common:
xen7test-fd JobId 117: Error: bpipe-fd: Error closing for file
/var/tmp/Odoo_8.xva: 268435457
Is this a backup or a restore?
It is more frequent during restore.
__Martin
Regards,
On Thu, 20 Sep 2018 11:31:37 -0300 (BRT), Heitor Faria said:
Dear users,
I observed that using the FileSet option noatime=yes might prevent bpipe closing
file errors such as this:
xxxxx-fd JobId 117: Error: bpipe-fd: Error closing for file /var/tmp/xxxxx: xxxx
Is this accurate?
Regards,
--
MSc Heitor Faria
CEO Bacula LATAM
mobile1: + 1 909 655-8971
mobile2: + 55 61 98268-4220
Brasilia - Miami - New York
www.bacula.com.br
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
