Hello all again ...

After consider that it could be a spooler problem, i remove spooling option
from job and launched the job again.
Full backup crashes again. this is the log from director:

17-Sep 20:01 bareos-dir JobId 38: Fatal error: Network error with FD during
Backup: ERR=No data available
17-Sep 20:01 bareos-sd JobId 38: Releasing device "Disk"
(/mnt/backup/volumes).
17-Sep 20:01 bareos-sd JobId 38: Elapsed time=58:22:50, Transfer rate=24.08
M Bytes/second
17-Sep 20:01 bareos-sd JobId 38: Sending spooled attrs to the Director.
Despooling 1,847,066,635 bytes ...
17-Sep 20:01 bareos-dir JobId 38: Fatal error: No Job status returned from
FD.
17-Sep 20:01 bareos-dir JobId 38: Error: Bareos bareos-dir 19.2.7 (16Apr20):
  Build OS:               Linux-3.10.0-1062.18.1.el7.x86_64 redhat CentOS
Linux release 7.7.1908 (Core)
  JobId:                  38
  Job:                    SAMBA.2020-09-15_09.38.46_07
  Backup Level:           Full (upgraded from Incremental)
  Client:                 "Samba-fd" 19.2.7 (16Apr20)
Linux-3.10.0-1062.18.1.el7.x86_64,redhat,CentOS release 6.10 (Final)
  FileSet:                "SAMBA-FileSet" 2020-09-03 15:08:01
  Pool:                   "Samba-Disk-Pool" (From Job resource)
  Catalog:                "MyCatalog" (From Client resource)
  Storage:                "Disk" (From Job resource)
  Scheduled time:         15-Sep-2020 09:38:41
  Start time:             15-Sep-2020 09:38:48
  End time:               17-Sep-2020 20:01:39
  Elapsed time:           2 days 10 hours 22 mins 51 secs
  Priority:               10
  FD Files Written:       0
  SD Files Written:       0
  FD Bytes Written:       0 (0 B)
  SD Bytes Written:       0 (0 B)
  Rate:                   0.0 KB/s
  Software Compression:   None
  VSS:                    no
  Encryption:             no
  Accurate:               no
  Volume name(s):         Samba-0013
  Volume Session Id:      20
  Volume Session Time:    1599138197
  Last Volume Bytes:      5,066,014,658,608 (5.066 TB)
  Non-fatal FD errors:    1
  SD Errors:              0
  FD termination status:  Error
  SD termination status:  SD despooling Attributes
  Bareos binary info:     bareos.org build: Get official binaries and
vendor support on bareos.com
  Termination:            *** Backup Error ***

Thank you all in advance.

best regards

El mar., 15 sept. 2020 a las 12:02, Jorge Morales (<
[email protected]>) escribió:

> Hello sire !
>
> Thank you so much for your faster response, but we have worked with other
> biggest volumes with the same bareos version and also others with bacula. .
> . and its working nice. . .
>
> so i think that its not the case this time.. .
>
> Thank you so much, very apreciate your help
>
> Best regards
>
> El mar., 15 sept. 2020 a las 11:05, Jorge Morales (<
> [email protected]>) escribió:
>
>> Hi all,
>>
>> I cannot finish any full backup in a Centos6.10 client.
>>
>> im using bareos  bareos-19.2.7-2 version in all platform (director under
>> CentOs7 and Storage and Client under CentOs6)
>>
>> When full backup its near to ends, i get following bareos-dir error and i
>> found bareos-fd stopped on client:
>>
>> 15-Sep 08:40 bareos-dir JobId 33: Fatal error: Network error with FD
>> during Backup: ERR=No data available
>> 15-Sep 08:40 bareos-sd JobId 33: Releasing device "Disk"
>> (/mnt/backup/volumes).
>> 15-Sep 08:40 bareos-sd JobId 33: Elapsed time=57:28:09, Transfer
>> rate=24.43 M Bytes/second
>> 15-Sep 08:40 bareos-sd JobId 33: Sending spooled attrs to the Director.
>> Despooling 1,846,359,585 bytes ...
>> 15-Sep 08:40 bareos-dir JobId 33: Fatal error: No Job status returned
>> from FD.
>> 15-Sep 08:40 bareos-dir JobId 33: Error: Bareos bareos-dir 19.2.7
>> (16Apr20):
>>   Build OS:               Linux-3.10.0-1062.18.1.el7.x86_64 redhat CentOS
>> Linux release 7.7.1908 Core)
>>   JobId:                  33
>>   Job:                    SAMBA.2020-09-12_23.12.00_10
>>   Backup Level:           Full (upgraded from Incremental)
>>   Client:                 "Samba-fd" 19.2.7 (16Apr20)
>> Linux-3.10.0-062.18.1.el7.x86_64,redhat,CentOS release 6.10 (Final)
>>   FileSet:                "SAMBA-FileSet" 2020-09-03 15:08:01
>>   Pool:                   "Samba-Disk-Pool" (From Job resource)
>>   Catalog:                "MyCatalog" (From Client resource)
>>   Storage:                "Disk" (From Job resource)
>>   Scheduled time:         12-Sep-2020 23:11:58
>>   Start time:             12-Sep-2020 23:12:02
>>   End time:               15-Sep-2020 08:40:12
>>   Elapsed time:           2 days 9 hours 28 mins 10 secs
>>   Priority:               10
>>   FD Files Written:       0
>>   SD Files Written:       0
>>   FD Bytes Written:       0 (0 B)
>>   SD Bytes Written:       0 (0 B)
>>   Rate:                   0.0 KB/s
>>   Software Compression:   None
>>   VSS:                    no
>>   Encryption:             no
>>   Accurate:               no
>>   Volume name(s):         Samba-0004
>>   Volume Session Id:      17
>>   Volume Session Time:    1599138197
>>   Last Volume Bytes:      5,059,988,163,264 (5.059 TB)
>>   Non-fatal FD errors:    1
>>   SD Errors:              0
>>
>>   FD termination status:  Error
>>
>>   SD termination status:  SD despooling Attributes
>>
>>   Bareos binary info:     bareos.org build: Get official binaries and
>> vendor support on bareos.com
>>   Termination:            *** Backup Error ***
>>
>> This is the related error from bareos-sd from the same job:
>>
>> 15-Sep 08:40 bareos-sd JobId 33: Sending spooled attrs to the Director.
>> Despooling 1,846,359,585 bytes ...
>> 15-Sep 08:40 bareos-sd JobId 33: Fatal error: Network error on
>> BlastAttributes.
>>
>>
>>
>> And this is from FD-client:
>>
>> Sep 15 08:42:31  bareos-fd: ABORTING due to ERROR#012lib/bsock_tcp.cc:786
>> fcntl F_GETFL error. ERR=Bad file descriptor
>> Sep 15 08:42:31  bareos-fd: BAREOS forced SEG FAULT to obtain traceback.
>> Sep 15 08:42:31  bareos-fd: BAREOS interrupted by signal 11: Segmentation
>> violation
>>
>> Any clue about it?
>>
>> Thank you in advance.
>>
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "bareos-users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/bareos-users/l7gH4VcrvWY/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/bareos-users/af2853ce-01e1-4bb7-9e01-cdc1378f7f4dn%40googlegroups.com
>> <https://groups.google.com/d/msgid/bareos-users/af2853ce-01e1-4bb7-9e01-cdc1378f7f4dn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bareos-users/CAGhGSXvVQtRHDvxo7nZj2ipJ0OnzuFDKwc92%2B_MSR6hmrNbigw%40mail.gmail.com.

Reply via email to