Hello Roberto,
Both FD and DIR have lost the connection with the Storage Daemon.
I would look more closely what happen here. You can monitor the
process, enable traces, or follow it with gdb if it looks like a
segfault. Maybe it's a network issue with something in the middle
that broke your connection.
Hope it helps
Eric
On 2/24/25 17:13, Roberto Greiner wrote:
Hi,
I have a setup with a windows client that is failing since last Friday. When I
run a backup, it fails after about 2 minutes with the message "Error: lib/
bsock.c:397 Wrote 65540 bytes to Storage daemon:bacula2:9103, but only 32768
accepted.". I've tried a reboot on both the windows client and the bacula
server, but that didn't help. The windows server is in a remote cloud provider.
I have two other (linux) VMs in that provider, and the backup of those VMs is
running fine. I have another local Windows box and it's backup is also running
fine. Could somebody help me try to understand what is failing here?
The client version on both sides is 15.0.2. The client is a Windows 2019 Server.
The bacula server is an Ubuntu 22.04 with a 7TB ZFS disk as main storage.
The error log I'm getting is the following:
24-fev 12:50 bacula2-dir JobId 3233: Start Backup JobId 3233,
Job=Sqlserver2019.2025-02-24_12.50.52_03
24-fev 12:50 bacula2-dir JobId 3233: Connected to Storage "FileAligned" at
bacula2:9103 with TLS
24-fev 12:50 bacula2-dir JobId 3233: Using Device "Aligned-Disk" to write.
24-fev 12:50 bacula2-dir JobId 3233: Connected to Client "sqlserver2019-fd" at
200.150.197.147:9102 with TLS
24-fev 12:50 sqlserver2019-fd JobId 3233: Connected to Storage at bacula2:9103
with TLS
24-fev 12:50 bacula2-sd JobId 3233: Volume "Vol-0565" previously written, moving
to end of data.
24-fev 12:50 sqlserver2019-fd JobId 3233: Generate VSS snapshots. Driver="Win64
VSS"
24-fev 12:50 sqlserver2019-fd JobId 3233: Snapshot mount point: C:\
24-fev 12:52 sqlserver2019-fd JobId 3233: Error: lib/bsock.c:397 Wrote 65540
bytes to Storage daemon:bacula2:9103, but only 32768 accepted.
24-fev 12:52 sqlserver2019-fd JobId 3233: Fatal error: filed/backup.c:1057
Network send error to SD. ERR=Input/output error
24-fev 12:52 sqlserver2019-fd JobId 3233: VSS Writer (BackupComplete): "Task
Scheduler Writer", State: 0x1 (VSS_WS_STABLE)
24-fev 12:52 sqlserver2019-fd JobId 3233: VSS Writer (BackupComplete): "VSS
Metadata Store Writer", State: 0x1 (VSS_WS_STABLE)
24-fev 12:52 sqlserver2019-fd JobId 3233: VSS Writer (BackupComplete):
"Performance Counters Writer", State: 0x1 (VSS_WS_STABLE)
24-fev 12:52 sqlserver2019-fd JobId 3233: VSS Writer (BackupComplete): "System
Writer", State: 0x1 (VSS_WS_STABLE)
24-fev 12:52 sqlserver2019-fd JobId 3233: VSS Writer (BackupComplete):
"SqlServerWriter", State: 0x1 (VSS_WS_STABLE)
24-fev 12:52 sqlserver2019-fd JobId 3233: VSS Writer (BackupComplete): "ASR
Writer", State: 0x1 (VSS_WS_STABLE)
24-fev 12:52 sqlserver2019-fd JobId 3233: VSS Writer (BackupComplete): "MSMQ
Writer (MSMQ)", State: 0x1 (VSS_WS_STABLE)
24-fev 12:52 sqlserver2019-fd JobId 3233: VSS Writer (BackupComplete): "Shadow
Copy Optimization Writer", State: 0x1 (VSS_WS_STABLE)
24-fev 12:52 sqlserver2019-fd JobId 3233: VSS Writer (BackupComplete): "IIS
Config Writer", State: 0x1 (VSS_WS_STABLE)
24-fev 12:52 sqlserver2019-fd JobId 3233: VSS Writer (BackupComplete): "IIS
Metabase Writer", State: 0x1 (VSS_WS_STABLE)
24-fev 12:52 sqlserver2019-fd JobId 3233: VSS Writer (BackupComplete): "COM+
REGDB Writer", State: 0x1 (VSS_WS_STABLE)
24-fev 12:52 sqlserver2019-fd JobId 3233: VSS Writer (BackupComplete): "Registry
Writer", State: 0x1 (VSS_WS_STABLE)
24-fev 12:52 sqlserver2019-fd JobId 3233: VSS Writer (BackupComplete): "WMI
Writer", State: 0x1 (VSS_WS_STABLE)
24-fev 12:52 sqlserver2019-fd JobId 3233: Error: lib/bsock.c:276 Socket has
errors=1 on call to Storage daemon:bacula2:9103
24-fev 12:52 bacula2-dir JobId 3233: Error: Director's connection to SD for this
Job was lost.
24-fev 12:52 bacula2-dir JobId 3233: Error: Bacula bacula2-dir 15.0.2 (21Mar24):
Build OS: x86_64-pc-linux-gnu-bacula ubuntu 22.04
JobId: 3233
Job: Sqlserver2019.2025-02-24_12.50.52_03
Backup Level: Incremental, since=2025-02-20 22:16:11
Client: "sqlserver2019-fd" 15.0.2 (21Mar24) Windows Server
2019 Standard ServerStandard (build 17763), 64-bit,Cross-compile,Win64
FileSet: "senior-backup_sql" 2024-03-21 10:04:56
Pool: "File" (From Job resource)
Catalog: "MyCatalog" (From Client resource)
Storage: "FileAligned" (From Job resource)
Scheduled time: 24-fev-2025 12:50:51
Start time: 24-fev-2025 12:50:55
End time: 24-fev-2025 12:52:46
Elapsed time: 1 min 51 secs
Priority: 10
FD Files Written: 241
SD Files Written: 0
FD Bytes Written: 45,983,400 (45.98 MB)
SD Bytes Written: 0 (0 B)
FD Bytes Written: 45,983,400 (45.98 MB)
SD Bytes Written: 0 (0 B)
Rate: 414.3 KB/s
Software Compression: 100.0% 1.0:1
Comm Line Compression: 83.8% 6.2:1
Snapshot/VSS: yes
Encryption: no
Accurate: no
Volume name(s):
Volume Session Id: 1
Volume Session Time: 1740412198
Last Volume Bytes: meta: 63,602,783 (63.60 MB) aligned: 23,255,190,528
(23.25 GB)
Non-fatal FD errors: 3
SD Errors: 0
FD termination status: Error
SD termination status: Error
Termination: *** Backup Error ***
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
