Someone an idea? Still having problems here.
Best,
Nextpertise
On 22 Oct 2013, at 19:17, Josh Fisher wrote:
>
> On 10/22/2013 10:53 AM, Teun Ouwehand [Nextpertise] wrote:
>> Hi Josh,
>>
>> Can you tell me how you come to the conclusion that it's timing out after 2
>> minutes?
>
> My bad.
On 10/22/2013 10:53 AM, Teun Ouwehand [Nextpertise] wrote:
> Hi Josh,
>
> Can you tell me how you come to the conclusion that it's timing out after 2
> minutes?
My bad. I missed the hour change. They say that vision deteriorates with
age. :)
>
>>> 20-Oct 03:04 backup1-dir JobId 18582: Volume u
Hi Josh,
Can you tell me how you come to the conclusion that it's timing out after 2
minutes?
>> 20-Oct 03:04 backup1-dir JobId 18582: Volume used once. Marking Volume
>> "Vol2709" as Used.
>> 20-Oct 04:05 host01 JobId 18582: Fatal error: backup.c:892 Network send
>> error to SD. ERR=Broken pi
I see an hour and 2 minutes. And to follow up on the issue, I see this
problem with my server, too, where the DIR, SD, and FD all reside. No
firewall between any of them. It will happen just as frequently there
with a long running backup as with an external client.
Patti Clark
Linux System Admi
On 10/21/2013 7:57 AM, Teun Ouwehand [Nextpertise] wrote:
> Hi Bacula enthusiasts,
>
> Since one year ago we implemented for our hosted servers a bacula backup
> domain. Since the beginning we have sometimes (regularly on sundays with full
> backups) the problem: "Fatal error: backup.c:892 Netwo
Hi Bacula enthusiasts,
Since one year ago we implemented for our hosted servers a bacula backup
domain. Since the beginning we have sometimes (regularly on sundays with full
backups) the problem: "Fatal error: backup.c:892 Network send error to SD.
ERR=Broken pipe"
This is an hot issue on this
