Re: New error appears on long-working system - Wrote X bytes to Storage daemon, but only Y accepted

Hi Dan,

Am 06.05.2026 um 17:14 schrieb Stieneke, Dan - OCIO-CEC, ID via 
Bacula-users:
> Sorry all if this is a repeat, the original message was kicked back 
> stating it needs moderator approval because I’m a non-member (sending 
> address was new v. address which joined the list).

we'll see if we get another instance :-)

Without really looking through all the details, I wonder about a few 
things in your job report.

In the progress report at the top, it mentions the SD wrote to three 
volumes.
Eventual volume status is only mentioning two volumes, and the SD bytes 
written is also 0.

This seems to indicate a problem that is not just a network issue 
between FD and SD but rather something affecting the SDs capability to 
communicate to the DIR as well.

If you run backups from other hosts, for example the backup server 
itself, do those succeed?

Also, the report states that the FD believes it runs on Windows Server 
2012, and that the FD version is slightly newer than the DIR/SD. None of 
that is necessarily problematic, but I think it would be reasonable to 
try upgrading the Bacula software on both ends first. Have you installed 
DIR/SD from Ubuntu repos or from another source?

Then, the fact that the FD reports a network issue but the SD doesn't 
seem to have anything to mention but the DIR lost the connection to it 
would imply that, if there's a network or Bacula protocol problem, it 
should be something that may be detected on the SD end. Have you ever 
used debug tracing with Bacula?

Cheers,

Arno

-- 
Arno Lehmann

IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück



_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users