View Issue Details

IDProjectCategoryView StatusLast Update
0001137bareos-core[All Projects] Generalpublic2019-11-20 23:49
ReporterembareossedAssigned To 
PrioritynormalSeveritytextReproducibilityalways
Status newResolutionopen 
PlatformLinuxOSDebianOS Version9
Product Version17.2.4 
Fixed in Version 
Summary0001137: Maximum Network Buffer Size must be set for network operations
DescriptionIn attempting to copy a job from the the source bareos system 1 (with its own director, storage, and file daemons) to the target bareos system 2 (also with its own director, storage, and file daemons), the job initially failed with an error which appeared in the syslog as:

bareos-sd: bsock_tcp.c:591 Packet size too big from client:192.168.xx.xx:9103

The documentation at https://docs.bareos.org/Configuration/FileDaemon.html#config-Fd_Client_MaximumNetworkBufferSize says default is 65536. However, running bareos-sd -xc reveals:

MaximumNetworkBufferSize = 0
(repeated for each storage and device resource, of course)

Setting this value to a larger number, such as the supposed default value of 65536, permits the copy job to proceed.

Steps To ReproduceSet MaximumNetworkBufferSize to zero, or omit the setting entirely in the Storage and Device resources of both the source and target systems involved in the network operation (copy, migrate, or maybe a distributed configuration?).

Attempt the network operation. A simple test could be running bconsole and requesting status on the remote storage daemon.
Additional InformationThe source system is running bareos 16.2, whereas the target system is running 17.2.

The documentation needs to be updated to instruct the administrator to set these values appropriately for network operations, or else the defaults in the code itself need to be set to the default values indicated in the current documentation.
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-19.2: impact
bareos-19.2: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action

Activities

embareossed

embareossed

2019-11-12 00:26

reporter   ~0003626

Incidentally, both the Storage Resource and the Device Resource of the storage daemon both support the MaximumNetworkBufferSize option. However, only the Device Resource has detailed information on the option. It might be a good idea to either reference the documentation of the Device Resource for more on this option, or add the same information there.
embareossed

embareossed

2019-11-12 00:31

reporter   ~0003627

The link I included in the description is actually the wrong one; it should be https://docs.bareos.org/Configuration/StorageDaemon.html#config-Sd_Device_MaximumNetworkBufferSize. However, the information there is the same as for Storage and Device resources.

Issue History

Date Modified Username Field Change
2019-11-12 00:22 embareossed New Issue
2019-11-12 00:26 embareossed Note Added: 0003626
2019-11-12 00:31 embareossed Note Added: 0003627