 |
Just checked with 15.2 - same issue |
|
|
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. |
|
|
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 |
|
|
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 |
|
|
Seems this is still an issue in 16.2. Btw, this is not a 'minor', since IPv6 should be pretty important by now. |
|
|
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. |
|
|
Closing old issues fixed long time ago (18x more) |
- Anonymous
