I have my new bareos system setup and configured.
Single server runs the Director and StorageDaemon.
I can do a backup of the bareos server, files and database.
I can do a status check of another client.
I can initiate a backup of that other client.
But, then nothing happens.
Status on the client shows a job running, but no transfers being made, and
SDSocket is noted as "closed".
Netstat on the Bareos Server (Direrctor and Storage)
tcp 0 0 *1.2.3.4*:9103 0.0.0.0:*
LISTEN 3323827/bareos-sd
tcp 0 0 0.0.0.0:9101 0.0.0.0:* LISTEN
3324579/bareos-dir
tcp 0 0 0.0.0.0:9102 0.0.0.0:* LISTEN
3323813/bareos-fd
tcp 0 0 *1.2.3.4*:9103 *1.2.3.4*:36666
ESTABLISHED 3323827/bareos-sd
tcp 0 0 127.0.0.1:44844 127.0.0.1:5432
ESTABLISHED 3324579/bareos-dir
tcp 0 0 *1.2.3.4*:51426 *1.2.8.9*:9102
ESTABLISHED 3324579/bareos-dir
tcp 0 0 *1.2.3.4*:36666 *1.2.3.4*:9103
ESTABLISHED 3324579/bareos-dir
Netstat on the Client
tcp 0 0 0.0.0.0:9102 0.0.0.0:* LISTEN
2627965/bareos-fd
tcp 0 0 *1.2.8.9*:9102 *1.2.3.4*:51426
ESTABLISHED 2627965/bareos-fd
tcp 0 1 *1.2.8.9*:60846 *1.2.3.4*:9103
*SYN_SENT* 2627965/bareos-fd
Eventually the 9103 (SYN_SENT) connection on the client will drop, and some
time after that the job will die.
>From what I can tell the FileDaemon is trying to connect with the
StorageDaemon, but never actually makes the connection. My first thought
was a TLS error, so I disabled TLS for all communication, just to rule it
out. I had the same problem.
Here's the final message from the job (and yes, I noticed the mis-config on
the Log Timestamp Format):
2025-08-29 11:47:S bareos-dir JobId 23: Connected Storage daemon at
*backupserver.example.com
<http://backupserver.example.com>*:9103, encryption:
TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
2025-08-29 11:47:S bareos-dir JobId 23: Encryption:
TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
2025-08-29 11:47:S bareos-dir JobId 23: Connected Client: *client1* at
*client1.example.com
<http://client1.example.com>*:9102, encryption:
TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
2025-08-29 11:47:S bareos-dir JobId 23: Handshake: Immediate TLS
2025-08-29 11:47:S bareos-dir JobId 23: Encryption:
TLS_CHACHA20_POLY1305_SHA256 TLSv1.3
2025-08-29 11:47:S bareos-sd JobId 23: Using just in time reservation for
job 23
2025-08-29 11:47:S bareos-dir JobId 23: Using Device "JustInTime Device" to
write.
2025-08-29 11:51:S *client1* JobId 23: Warning: lib/bsock_tcp.cc:171 Could
not connect to Storage daemon on *backupserver.example.com
<http://backupserver.example.com>*:9103. ERR=Connection timed out
Retrying ...
2025-08-29 12:17:S *client1* JobId 23: Fatal error: lib/bsock_tcp.cc:179
Unable to connect to Storage daemon on *backupserver.example.com
<http://backupserver.example.com>*:9103. ERR=Interrupted system call
2025-08-29 12:17:S *client1* JobId 23: Fatal error: Failed to connect to
Storage daemon: *backupserver.example.com <http://backupserver.example.com>*
:9103
2025-08-29 12:17:S bareos-dir JobId 23: Fatal error: Bad response to
Storage command: wanted 2000 OK storage, got 2902 Bad storage
2025-08-29 10:50:S *client1* JobId 22: Warning: lib/bsock_tcp.cc:171 Could
not connect to Storage daemon on *backupserver.example.com
<http://backupserver.example.com>*:9103.ERR=Connection timed out
Retrying ...
2025-08-29 11:16:S *client1* JobId 22: Fatal error: lib/bsock_tcp.cc:179
Unable to connect to Storage daemon on *backupserver.example.com
<http://backupserver.example.com>*:9103. ERR=Interrupted system call
2025-08-29 11:16:S *client1* JobId 22: Fatal error: Failed to connect to
Storage daemon: *backupserver.example.com <http://backupserver.example.com>*
:9103
2025-08-29 11:16:S bareos-dir JobId 22: Fatal error: Bad response to
Storage command: wanted 2000 OK storage
Any ideas?
-John
--
- Adaptability -- Analytical --- Ideation ---- Input ----- Belief -
-------------------------------------------------------------------
John M. Lockard | U of Michigan - School of Information
Unix Sys Admin | Suite 205 | 309 Maynard Street
jlock...@umich.edu | Ann Arbor, MI 48104-2211
www.umich.edu/~jlockard <http://www.umich.edu/%7Ejlockard> |
734-615-8776 | 734-763-9677 FAX
-------------------------------------------------------------------
- The University of Michigan will never ask you for your password -
--
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 bareos-users+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/bareos-users/CAHDqrGcqTwfEok%2BdQAKp6xKNZNB1hC%3DDqz9DnrbEtPejORoCEQ%40mail.gmail.com.
