|
|
| Reporter | embareossed | Assigned To | bruno-at-bareos | |
|---|
| Priority | normal | Severity | text | Reproducibility | always |
|---|
| Status | closed | Resolution | no change required | |
|---|
| Platform | Linux | OS | Debian | OS Version | 9 |
|---|
| Product Version | 17.2.4 | |
|---|
|
|
| Summary | 0001137: Maximum Network Buffer Size must be set for network operations |
|---|
| Description | In 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 Reproduce | Set 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 Information | The 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. |
|---|
| Tags | No tags attached. |
|---|
|
|
