View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001256bareos-corefile daemonpublic2020-06-25 13:092023-08-29 09:58
Reporteradmibaun Assigned Tobruno-at-bareos  
PriorityhighSeveritymajorReproducibilityalways
Status closedResolutionunable to reproduce 
Platformx86OSWindowsOS Version10
Product Version19.2.7 
Summary0001256: FileDemon Crashes while get status from client
DescriptionHey,

I found a bug.

I have a Bareos-Server installed on a Debian 10 Maschine (updated) with Version 19.2.7.

My Client is a Windows Pro 1909 64-Bit Client.

I enabled Transport Encryption (TLS) and Data Encryption (PKI).
Steps To ReproduceI made a Full Backup with the Windows 10 Client (run -> select Windows File Demon -> yes ... and go).

While the backup is running (FileDemon sends data to director (or Storage (I don't know the exact mechanism at the moment)) and I type "status -> client -> select Windows Client" it hangs up with "Connecting to Client xxxx at xxxx" -> After some seconds I get "Failed to connect to Client xxxx" (xxx Stands for anonymos replaced).

In the log I can see the Backup gets an Error with the following lines (see attached Info).

The confuse thing is - if I don't type the status-command for the client and don't get the client info while it is backuping -> I don't get this error.

The status-command for the client interrupts the backuping process and let him go in a error status.
Additional Information25-Jun 12:46 bareos-sd JobId 48: Labeled new Volume "Full-ptpsrv-fd-0034" on device "FileStorage" (/home/dump/BACKUP-Bareos).
25-Jun 12:46 bareos-sd JobId 48: Wrote label to prelabeled Volume "Full-ptpsrv-fd-0034" on device "FileStorage" (/home/dump/BACKUP-Bareos)
25-Jun 12:46 bareos-dir JobId 48: Volume used once. Marking Volume "Full-ptpsrv-fd-0034" as Used.
25-Jun 12:46 ptpsrv-fd JobId 48: Generate VSS snapshots. Driver="Win64 VSS", Drive(s)="C"
25-Jun 12:46 ptpsrv-fd JobId 48: VolumeMountpoints are not processed as onefs = yes.
25-Jun 12:52 ptpsrv-fd JobId 48: Fatal error: TLS read/write failure.: ERR=error:0906D06C:PEM routines:PEM_read_bio:no start line
25-Jun 12:52 ptpsrv-fd JobId 48: Error: lib/bsock_tcp.cc:435 Wrote 65536 bytes to Storage daemon:10.1.1.51:9103, but only 16384 accepted.
25-Jun 12:52 ptpsrv-fd JobId 48: Fatal error: filed/backup.cc:1020 Network send error to SD. ERR=Input/output error
25-Jun 12:52 ptpsrv-fd JobId 48: VSS Writer (BackupComplete): "Task Scheduler Writer", State: 0x1 (VSS_WS_STABLE)
25-Jun 12:52 ptpsrv-fd JobId 48: VSS Writer (BackupComplete): "VSS Metadata Store Writer", State: 0x1 (VSS_WS_STABLE)
25-Jun 12:52 ptpsrv-fd JobId 48: VSS Writer (BackupComplete): "Performance Counters Writer", State: 0x1 (VSS_WS_STABLE)
25-Jun 12:52 ptpsrv-fd JobId 48: VSS Writer (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE)
25-Jun 12:52 ptpsrv-fd JobId 48: VSS Writer (BackupComplete): "MSSearch Service Writer", State: 0x1 (VSS_WS_STABLE)
25-Jun 12:52 ptpsrv-fd JobId 48: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE)
25-Jun 12:52 ptpsrv-fd JobId 48: VSS Writer (BackupComplete): "BITS Writer", State: 0x1 (VSS_WS_STABLE)
25-Jun 12:52 ptpsrv-fd JobId 48: VSS Writer (BackupComplete): "ASR Writer", State: 0x1 (VSS_WS_STABLE)
25-Jun 12:52 ptpsrv-fd JobId 48: VSS Writer (BackupComplete): "Shadow Copy Optimization Writer", State: 0x1 (VSS_WS_STABLE)
25-Jun 12:52 ptpsrv-fd JobId 48: VSS Writer (BackupComplete): "SqlServerWriter", State: 0x1 (VSS_WS_STABLE)
25-Jun 12:52 ptpsrv-fd JobId 48: VSS Writer (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE)
25-Jun 12:52 ptpsrv-fd JobId 48: VSS Writer (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE)
25-Jun 12:52 bareos-dir JobId 0: Fatal error: Authorization key rejected bareos-dir.
25-Jun 12:52 bareos-dir JobId 0: Fatal error: Unable to authenticate with File daemon at "10.1.1.50:9102". Possible causes:
Passwords or names not the same or
TLS negotiation failed or
Maximum Concurrent Jobs exceeded on the FD or
FD networking messed up (restart daemon).
25-Jun 12:52 bareos-sd JobId 48: Error: lib/bsock_tcp.cc:651 Read expected 65536 got 16380 from client:10.1.1.50:9103
25-Jun 12:52 bareos-sd JobId 48: Fatal error: stored/append.cc:251 Network error reading from FD. ERR=Eingabe-/Ausgabefehler
25-Jun 12:52 bareos-sd JobId 48: Releasing device "FileStorage" (/home/dump/BACKUP-Bareos).
25-Jun 12:52 bareos-sd JobId 48: Elapsed time=00:06:06, Transfer rate=10.82 M Bytes/second
25-Jun 12:52 bareos-dir JobId 48: Error: Bareos bareos-dir 19.2.7 (16Apr20):
  Build OS: Linux-3.10.0-1062.18.1.el7.x86_64 debian Debian GNU/Linux 10 (buster)
  JobId: 48
  Job: backup-ptpsrv-fd.2020-06-25_12.31.04_04
  Backup Level: Full (upgraded from Incremental)
  Client: "ptpsrv-fd" 19.2.7 (16Apr20) Microsoft Windows 8 Professional (build 9200), 64-bit,Cross-compile,Win64
  FileSet: "FileSet-ptpsrv-fd" 2020-06-25 12:21:48
  Pool: "Full-ptpsrv-fd" (From Job FullPool override)
  Catalog: "MyCatalog" (From Client resource)
  Storage: "File" (From Job resource)
  Scheduled time: 25-Jun-2020 12:31:02
  Start time: 25-Jun-2020 12:46:30
  End time: 25-Jun-2020 12:52:37
  Elapsed time: 6 mins 7 secs
  Priority: 10
  FD Files Written: 1,129
  SD Files Written: 1,129
  FD Bytes Written: 3,961,375,852 (3.961 GB)
  SD Bytes Written: 3,961,860,442 (3.961 GB)
  Rate: 10793.9 KB/s
  Software Compression: None
  VSS: yes
  Encryption: yes
  Accurate: no
  Volume name(s): Full-ptpsrv-fd-0034
  Volume Session Id: 15
  Volume Session Time: 1593069247
  Last Volume Bytes: 3,964,843,189 (3.964 GB)
  Non-fatal FD errors: 2
  SD Errors: 1
  FD termination status: Fatal Error
  SD termination status: Fatal Error
  Bareos binary info: bareos.org build: Get official binaries and vendor support on bareos.com
  Termination: *** Backup Error ***

Tagsdebian 10, fd, filedemon, Windows

Activities

mathias

mathias

2020-11-24 17:20

reporter   ~0004058

Similar situation and issue here on our setup.

Windows 7 (x64) Client bareos 19.2.7 connected to bareos director & storage (19.2.7) running on Debian 9.x

24-Nov 14:47 $server$-dir JobId $jobid$: Start Backup JobId $jobid$, Job=$JOBNAME$.2020-11-24_14.47.07_15
24-Nov 14:47 $server$-dir JobId $jobid$: Connected Storage daemon at $server$:9103, encryption: TLS_AES_256_GCM_SHA384
24-Nov 14:47 $server$-dir JobId $jobid$: Using Device "LTO5-Drive0" to write.
24-Nov 14:47 $server$-dir JobId $jobid$: Connected Client: $client$-fd at $client$:9102, encryption: AES256-GCM-SHA384
24-Nov 14:47 $server$-dir JobId $jobid$: Handshake: Immediate TLS
24-Nov 14:47 $server$-sd JobId $jobid$: Spooling data ...
24-Nov 14:47 $client$-fd JobId $jobid$: Created 28 wildcard excludes from FilesNotToBackup Registry key
24-Nov 14:47 $client$-fd JobId $jobid$: Connected Storage daemon at $server$:9103, encryption: ECDHE-RSA-AES256-GCM-SHA384
24-Nov 14:47 $client$-fd JobId $jobid$: Generate VSS snapshots. Driver="Win64 VSS", Drive(s)="C"
24-Nov 14:47 $client$-fd JobId $jobid$: VolumeMountpoints are not processed as onefs = yes.
24-Nov 14:47 $client$-fd JobId $jobid$: Fatal error: TLS read/write failure.: ERR=error:0906D06C:PEM routines:PEM_read_bio:no start line
24-Nov 14:47 $client$-fd JobId $jobid$: Error: lib/bsock_tcp.cc:435 Wrote 65536 bytes to Storage daemon:$server$:9103, but only 32768 accepted.
24-Nov 14:47 $client$-fd JobId $jobid$: Fatal error: filed/backup.cc:1020 Network send error to SD. ERR=Input/output error
24-Nov 14:47 $client$-fd JobId $jobid$: VSS Writer (BackupComplete): "Task Scheduler Writer", State: 0x1 (VSS_WS_STABLE)
24-Nov 14:47 $client$-fd JobId $jobid$: VSS Writer (BackupComplete): "VSS Metadata Store Writer", State: 0x1 (VSS_WS_STABLE)
24-Nov 14:47 $client$-fd JobId $jobid$: VSS Writer (BackupComplete): "Performance Counters Writer", State: 0x1 (VSS_WS_STABLE)
24-Nov 14:47 $client$-fd JobId $jobid$: VSS Writer (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE)
24-Nov 14:47 $client$-fd JobId $jobid$: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE)
24-Nov 14:47 $client$-fd JobId $jobid$: VSS Writer (BackupComplete): "ASR Writer", State: 0x1 (VSS_WS_STABLE)
24-Nov 14:47 $client$-fd JobId $jobid$: VSS Writer (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE)
24-Nov 14:47 $client$-fd JobId $jobid$: VSS Writer (BackupComplete): "Shadow Copy Optimization Writer", State: 0x1 (VSS_WS_STABLE)
24-Nov 14:47 $client$-fd JobId $jobid$: VSS Writer (BackupComplete): "MSSearch Service Writer", State: 0x1 (VSS_WS_STABLE)
24-Nov 14:47 $client$-fd JobId $jobid$: VSS Writer (BackupComplete): "BITS Writer", State: 0x1 (VSS_WS_STABLE)
24-Nov 14:47 $client$-fd JobId $jobid$: VSS Writer (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE)
24-Nov 14:47 $server$-sd JobId $jobid$: Error: lib/bsock_tcp.cc:651 Read expected 65536 got 65532 from client:$client-ip$:9103
24-Nov 14:47 $server$-dir JobId $jobid$: Error: Bareos $server$-dir 19.2.7 (16Apr20):
bruno-at-bareos

bruno-at-bareos

2023-08-22 20:38

manager   ~0005336

Would you mind to test this with the recent >=22.1.0 version?
Also I wonder why you have EL_7 build on a debian host, do you mix packages ?

Build OS: Linux-3.10.0-1062.18.1.el7.x86_64 debian Debian GNU/Linux 10 (buster)
mathias

mathias

2023-08-29 00:55

reporter   ~0005352

Hi Bruno.
Thanks for your reply. My note to this problem is almost 3 years old now, I'm not able to reproduce it since server and client are migrated to the latest version now and everything is working as expected.
And unfortunately I cannot remember what I've changed back then to get the Win 7 client to work again, sorry!
br, mathias
bruno-at-bareos

bruno-at-bareos

2023-08-29 09:58

manager   ~0005353

fixed in recent version.

Issue History

Date Modified Username Field Change
2020-06-25 13:09 admibaun New Issue
2020-06-25 13:09 admibaun Tag Attached: filedemon
2020-06-25 13:09 admibaun Tag Attached: debian 10
2020-06-25 13:09 admibaun Tag Attached: fd
2020-06-25 13:09 admibaun Tag Attached: Windows
2020-11-24 17:20 mathias Note Added: 0004058
2023-08-22 20:38 bruno-at-bareos Assigned To => bruno-at-bareos
2023-08-22 20:38 bruno-at-bareos Status new => feedback
2023-08-22 20:38 bruno-at-bareos Note Added: 0005336
2023-08-29 00:55 mathias Note Added: 0005352
2023-08-29 09:58 bruno-at-bareos Status feedback => closed
2023-08-29 09:58 bruno-at-bareos Resolution open => unable to reproduce
2023-08-29 09:58 bruno-at-bareos Note Added: 0005353