View Issue Details

IDProjectCategoryView StatusLast Update
0000477bareos-core[All Projects] file daemonpublic2019-08-08 14:56
ReporterRoyKAssigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status acknowledgedResolutionopen 
PlatformWindowsOSanyOS Version8
Product Version14.2.2 
Target VersionFixed in Version 
Summary0000477: Bareos-fd fails with IPv6
DescriptionIf bareos-fd is configured with IPv6 on Windows, director just hangs when attempting to contact fd. If removing the ipv6 config, director hangs in 0000004:0000001 minute before attempting ipv4, and things work. If hardcoding ipv4 address and removing ipv6 config on fd, things works as normal. We use IPv6 with all Linux clients and the plan was to use it with all windows clients as well, but this does not seem to be possible at the moment.
Steps To Reproducebareos-fd.conf - tested on win2k8r2 and win2k12r2, both 64bit

Director {
  Name = urd.my.tld-dir
  Password = "supersecret"
}

FileDaemon {
  Name = somewinbox.my.tld-fd
  Maximum Concurrent Jobs = 20
  FDAddresses = {ipv6 = {port = 9102}}
}
TagsNo tags attached.
bareos-master: impactyes
bareos-master: actionwill care
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: impactyes
bareos-15.2: actionwill care
bareos-14.2: impactyes
bareos-14.2: actionnone
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action

Activities

RoyK

RoyK

2015-10-07 19:30

reporter   ~0001871

Just checked with 15.2 - same issue
eye69

eye69

2016-08-20 10:27

reporter   ~0002337

Just checked with freshly downloaded "winbareos-16.3.1.1471620779.cae6abe-postvista-64-bit-r203.1.exe" on Windows 10 Pro, build 10586.545

When trying to contact the file daemon through IPv6, it just goes to 25% CPU usage and doesn't respond.
tigerfoot

tigerfoot

2016-10-12 14:10

developer   ~0002381

eye69 or RoyK any of you would be able to start bareos-fd with debug mode
options that should be added to windows service
-d 200
Lee

Lee

2016-10-24 13:11

reporter   ~0002406

Hi there,

Please find trace for IPv6 listener below:



bareos-fd (100): lib/parse_conf.c:151-0 config file = C:\ProgramData\Bareos\bareos-fd.d/*/*.conf
bareos-fd (100): lib/lex.c:356-0 glob C:\ProgramData\Bareos\bareos-fd.d/*/*.conf: 4 files
bareos-fd (100): lib/lex.c:250-0 open config file: C:\ProgramData\Bareos\bareos-fd.d/client/myself.conf
bareos-fd (100): lib/lex.c:250-0 open config file: C:\ProgramData\Bareos\bareos-fd.d/director/bareos-dir.conf
bareos-fd (100): lib/lex.c:250-0 open config file: C:\ProgramData\Bareos\bareos-fd.d/director/bareos-mon.conf
bareos-fd (100): lib/lex.c:250-0 open config file: C:\ProgramData\Bareos\bareos-fd.d/messages/Standard.conf
bareos-fd (90): filed/filed_conf.c:445-0 Inserting Director res: bareos-dir
bareos-fd (100): lib/lex.c:356-0 glob C:\ProgramData\Bareos\bareos-fd.d/*/*.conf: 4 files
bareos-fd (100): lib/lex.c:250-0 open config file: C:\ProgramData\Bareos\bareos-fd.d/client/myself.conf
bareos-fd (100): lib/lex.c:250-0 open config file: C:\ProgramData\Bareos\bareos-fd.d/director/bareos-dir.conf
bareos-fd (100): lib/lex.c:250-0 open config file: C:\ProgramData\Bareos\bareos-fd.d/director/bareos-mon.conf
bareos-fd (100): lib/lex.c:250-0 open config file: C:\ProgramData\Bareos\bareos-fd.d/messages/Standard.conf
id48269-fd (100): lib/jcr.c:141-0 read_last_jobs seek to 192
id48269-fd (100): lib/jcr.c:148-0 Read num_items=0
id48269-fd (150): filed/fd_plugins.c:1664-0 plugin dir is NULL
id48269-fd (10): filed/socket_server.c:96-0 filed: listening on port 9102
id48269-fd (100): lib/bnet_server_tcp.c:170-0 Addresses host[ipv6;0.0.0.0;9102]




************************

For comparison with IPv4 trace, i've provided that also (With a successful connect from director):



bareos-fd (100): lib/parse_conf.c:151-0 config file = C:\ProgramData\Bareos\bareos-fd.d/*/*.conf
bareos-fd (100): lib/lex.c:356-0 glob C:\ProgramData\Bareos\bareos-fd.d/*/*.conf: 4 files
bareos-fd (100): lib/lex.c:250-0 open config file: C:\ProgramData\Bareos\bareos-fd.d/client/myself.conf
bareos-fd (100): lib/lex.c:250-0 open config file: C:\ProgramData\Bareos\bareos-fd.d/director/bareos-dir.conf
bareos-fd (100): lib/lex.c:250-0 open config file: C:\ProgramData\Bareos\bareos-fd.d/director/bareos-mon.conf
bareos-fd (100): lib/lex.c:250-0 open config file: C:\ProgramData\Bareos\bareos-fd.d/messages/Standard.conf
bareos-fd (90): filed/filed_conf.c:445-0 Inserting Director res: Ziff-dir
bareos-fd (100): lib/lex.c:356-0 glob C:\ProgramData\Bareos\bareos-fd.d/*/*.conf: 4 files
bareos-fd (100): lib/lex.c:250-0 open config file: C:\ProgramData\Bareos\bareos-fd.d/client/myself.conf
bareos-fd (100): lib/lex.c:250-0 open config file: C:\ProgramData\Bareos\bareos-fd.d/director/bareos-dir.conf
bareos-fd (100): lib/lex.c:250-0 open config file: C:\ProgramData\Bareos\bareos-fd.d/director/bareos-mon.conf
bareos-fd (100): lib/lex.c:250-0 open config file: C:\ProgramData\Bareos\bareos-fd.d/messages/Standard.conf
id48269-fd (100): lib/jcr.c:141-0 read_last_jobs seek to 192
id48269-fd (100): lib/jcr.c:148-0 Read num_items=0
id48269-fd (150): filed/fd_plugins.c:1664-0 plugin dir is NULL
id48269-fd (10): filed/socket_server.c:96-0 filed: listening on port 9102
id48269-fd (100): lib/bnet_server_tcp.c:170-0 Addresses host[ipv4;0.0.0.0;9102]
id48269-fd (110): filed/socket_server.c:63-0 Conn: Hello Director Ziff-dir calling

id48269-fd (110): filed/socket_server.c:69-0 Got a DIR connection at 24-Oct-2016 12:07:53
id48269-fd (120): filed/dir_cmd.c:630-0 Calling Authenticate
id48269-fd (200): lib/bsys.c:191-0 pthread_cond_timedwait sec=0 usec=100
id48269-fd (50): lib/cram-md5.c:68-0 send: auth cram-md5 <29108.1477307273@id48269-fd> ssl=0
id48269-fd (100): lib/cram-md5.c:123-0 cram-get received: auth cram-md5 <1182722634.1477307273@Ziff-dir> ssl=0
id48269-fd (99): lib/cram-md5.c:143-0 sending resp to challenge: w7k/nCcyQCwlj+R79x/A2D
id48269-fd (200): lib/bsys.c:191-0 pthread_cond_timedwait sec=0 usec=100
id48269-fd (120): filed/dir_cmd.c:632-0 OK Authenticate
id48269-fd (100): filed/dir_cmd.c:495-0 <dird: status
id48269-fd (100): filed/dir_cmd.c:506-0 Executing status command.
id48269-fd (200): lib/runscript.c:149-0 runscript: running all RUNSCRIPT object (ClientAfterJob) JobStatus=C
id48269-fd (150): filed/fd_plugins.c:327-0 No bplugin_list: generate_plugin_event ignored.
id48269-fd (100): filed/dir_cmd.c:568-0 Done with free_jcr
RoyK

RoyK

2017-02-20 23:01

reporter   ~0002577

Seems this is still an issue in 16.2. Btw, this is not a 'minor', since IPv6 should be pretty important by now.
kjetilho

kjetilho

2018-03-15 00:05

reporter   ~0002946

still an issue in 17.2.4-8.1 on Windows 2012R2 (64-bit). same symptoms, last message in trace is

foo.net-fd (100): lib/bnet_server_tcp.c:174-0 Addresses host[ipv6;0.0.0.0;9102]

and when director tries to connect, one CPU core starts spinning. please let me know if I can assist in debugging this.

Issue History

Date Modified Username Field Change
2015-06-08 13:02 RoyK New Issue
2015-10-07 19:30 RoyK Note Added: 0001871
2015-11-06 17:37 maik bareos-master: impact => yes
2015-11-06 17:37 maik bareos-master: action => will care
2015-11-06 17:37 maik bareos-15.2: impact => yes
2015-11-06 17:37 maik bareos-15.2: action => will care
2015-11-06 17:37 maik bareos-14.2: impact => yes
2015-11-06 17:37 maik bareos-14.2: action => none
2015-11-06 17:37 maik Reproducibility always => have not tried
2015-11-06 17:37 maik Status new => acknowledged
2016-08-20 10:27 eye69 Note Added: 0002337
2016-10-12 14:10 tigerfoot Note Added: 0002381
2016-10-24 13:11 Lee Note Added: 0002406
2017-02-20 23:01 RoyK Note Added: 0002577
2018-03-15 00:05 kjetilho Note Added: 0002946