[pkg-bacula-devel] Bug#1009231: Write errors since upgrade to 9.6.7-4

[Sven Hartge]

On 09.04.22 12:12, Klaus Ethgen wrote:

> Since upgrade from 9.6.7-3 to 9.6.7-4 I get many of the following errors
> in the log. However, the backup seems to work.
> 
> JobId 0: Security Alert: bsock.c:380 Write error sending 4 bytes to client:127.0.0.1:57050: ERR=Broken pipe
> JobId 0: Security Alert: bsock.c:380 Write error sending 4 bytes to client:127.0.0.1:57074: ERR=Broken pipe
> ...
> JobId 0: Security Alert: bsock.c:380 Write error sending 4 bytes to client:127.0.0.1:57134: ERR=Connection reset by peer
> JobId 0: Security Alert: bsock.c:380 Write error sending 4 bytes to client:127.0.0.1:57126: ERR=Connection reset by peer
> ...

Hello Klaus,

I have not been able to reproduce this nor am I seeing this on any of my 
systems.

Please check that the version of bacula-sd matches the one from 
bacula-director and that bacula-fd is of no higher version than the 
Director and the SD.

Also seeing "Connection reset by peer" while connecting via localhost is 
very suspicious, IMHO. Is the FD dying during the backup?

What do you system logs and dmesg show during the exact time this happens?

> ii  init-system-helpers      1.62devuan1

This looks like a mixed Debian/Devuan system. Can you make sure to 
reproduce the bug in a clean Debian system, to rule out anything being 
affected by changes made for Devuan.

Grüße,
Sven.