On Monday 2020-08-31 20:02:58 mark.berg...@pennmedicine.upenn.edu wrote: > I've got one client where backups consistently stall and eventually > timeout after backing up 6 files (~760KB). The backup consistently > stalls at the 7th file: > > Processing file: /boot/System.map-3.10.0-693.el7.x86_64 > > That file is valid on the client (there are no I/O errors) and bacula-fd > runs as root, with permission to read the file. > > The client & server are both running 9.6.5 now, but before today > the server was at 9.5.1 and the client at 9.2.x, with the same > behavior. Restarting bacula-fd on the client does not help. > > The server is able to successfully run the "estimate" command, which > returns an expected value of about 90GB to be backed up from that > client. > > The client & server are multi-homed, but are on the same network. The > client configuration on the bacula-dir specifies the client by IP, > to ensure that traffic goes via the faster network common to the two > machines. > > Other clients on the same network backup successfully (many TB per day). > > When the job times out at 15min 4* seconds, the client eventually > reports only: > > Network send error to SD. ERR=Connection timed out > even with "-d 200" set to enable debugging. > > The server reports: > > Error: bsock.c:383 Write error sending 24573 bytes to Storage > daemon:bacula-server:9103: ERR=Connection timed out
Hello! Sound like routing problem. I would start nc in listening mode on the SD server and try to send some big test file (e.g. some tar archive containing random data) using nc to see if the problem would occur even without bacula. Regards! -- Josip Deanovic _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
