View Issue Details

IDProjectCategoryView StatusLast Update
0001518bareos-corefile daemonpublic2023-03-02 14:09
ReporterUraniumDonut Assigned Tobruno-at-bareos  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
PlatformLinuxOSRHEL (and clones)OS Version8
Product Version22.0.2 
Summary0001518: bareos-fd fails to start socket when ipv6 is disabled in OS
DescriptionIf ipv6 is disabled in the OS (indicated by /sys/module/ipv6/parameters/disable) on the client, bareos-fd appears to start normally, but can't create a socket. The director then cannot connect, even via ipv4.

This happens with the default client configuration, without explicitly defined "Address" variables in the config.

The error is only visible in debug mode (bareos-fd -f -s -d 200) . The filedaemon appears to be running properly (even though it isn't)

On the director debug, connecting results in:

bareos-dir (100): lib/bsock_tcp.cc:218-0 Current host[ipv4;XX.XX.XX.XX;9102] All host[ipv4;XX.XX.XX.XX;9102]
bareos-dir (100): lib/bsock_tcp.cc:115-0 Unable to connect to Client: CLIENTNAME on CLIENTNAME :9102. ERR=Connection refused
bareos-dir (50): lib/bsock.cc:669-0 TLS negotiation failed (while probing client protocol)
bareos-dir (100): dird/authenticate.cc:143-0 Could not DoTlsHandshake() with a file daemon
bareos-dir (100): lib/bsock.cc:136-0 Destruct BareosSocket
bareos-dir (120): dird/job.cc:407-0 Connection from client "CLIENTNAME " to director is not allowed.

In bconsole, connecting results in:

02-Mar 09:25 bareos-dir JobId 0: Fatal error:
Failed to connect to client "CLIENTNAME".


Bareos should
- try to create the sockets independently, so still ipv4 works, if ipv6 fails or
- notify the user, that the filedaemon does not work, because ipv6 initialization failed
Steps To Reproduce- Disable ipv6 in OS
- Install bareos-fd
- Run bareos-fd
- Try to connect via bareos-dir to the client running bareos-fd
Additional InformationSadly I am using a restricted console, from where I cannot copy text. Thus the error is as an image in the attachments.

This seems to be created by Bareos-update 21, from when Bareos listens on ipv4 and ipv6 by default.
Tagscrash, fd, filedemon, network

Activities

UraniumDonut

UraniumDonut

2023-03-02 10:28

reporter  

Bareos-IPV6.png (16,292 bytes)   
Bareos-IPV6.png (16,292 bytes)   
bruno-at-bareos

bruno-at-bareos

2023-03-02 14:09

manager   ~0004887

Not a bug, this is the expected behavior since 21.
Have a look at documentation and release note, if you don't want to use the dual socket you have to set the correct address type in the configuration.
bruno-at-bareos

bruno-at-bareos

2023-03-02 14:09

manager   ~0004888

Expected feature and normal functionnality

Issue History

Date Modified Username Field Change
2023-03-02 10:28 UraniumDonut New Issue
2023-03-02 10:28 UraniumDonut Tag Attached: crash
2023-03-02 10:28 UraniumDonut Tag Attached: fd
2023-03-02 10:28 UraniumDonut Tag Attached: filedemon
2023-03-02 10:28 UraniumDonut Tag Attached: network
2023-03-02 10:28 UraniumDonut File Added: Bareos-IPV6.png
2023-03-02 14:09 bruno-at-bareos Note Added: 0004887
2023-03-02 14:09 bruno-at-bareos Assigned To => bruno-at-bareos
2023-03-02 14:09 bruno-at-bareos Status new => closed
2023-03-02 14:09 bruno-at-bareos Resolution open => no change required
2023-03-02 14:09 bruno-at-bareos Note Added: 0004888