Well, the segfault happens in Thread 5: Thread 5 (Thread 0x7fab87fff700 (LWP 12962)): #0 0x00007fab9677db3a in __waitpid (pid=pid@entry=60063, stat_loc=stat_loc@entry=0x7fab87ffd54c, options=options@entry=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29 #1 0x00007fab97f4dab4 in signal_handler (sig=7) at signal.c:240 #2 <signal handler called> #3 0x00007fab97f22f82 in bnet_host2ipaddrs (host=host@entry=0xaaaaaaaaaaaaaaaa <error: Cannot access memory at address 0xaaaaaaaaaaaaaaaa>, family=family@entry=0, errstr=errstr@entry=0x7fab87ffe028) at bnet.c:418 #4 0x00007fab97f2c5ca in BSOCK_TCP::open (this=0x7fab7c00e068, jcr=0x7fab7c001078, name=0x55a0677fd5a1 "Storage daemon", host=0xaaaaaaaaaaaaaaaa <error: Cannot access memory at address 0xaaaaaaaaaaaaaaaa>, service=<optimized out>, port=-1431655766, heart_beat=-6148914691236517206, fatal=0x7fab87ffebdc) at bsock_tcp.c:182 #5 0x00007fab97f2b5cd in BSOCK_TCP::connect (this=this@entry=0x7fab7c00e068, jcr=jcr@entry=0x7fab7c001078, retry_interval=retry_interval@entry=2, max_retry_time=max_retry_time@entry=1, heart_beat=heart_beat@entry=-6148914691236517206, name=0x55a0677fd5a1 "Storage daemon", host=0xaaaaaaaaaaaaaaaa <error: Cannot access memory at address 0xaaaaaaaaaaaaaaaa>, service=0x0, port=-1431655766, verbose=false) at bsock_tcp.c:115 #6 0x000055a0677c34cd in connect_to_storage_daemon (jcr=0x7fab7c001078, retry_interval=<optimized out>, max_retry_time=<optimized out>, verbose=verbose@entry=false) at sd_cmds.c:117 #7 0x000055a0677c35b8 in connect_to_storage_daemon (jcr=jcr@entry=0x7fab7c001078, retry_interval=retry_interval@entry=2, max_retry_time=max_retry_time@entry=1, verbose=verbose@entry=false) at sd_cmds.c:136 #8 0x000055a0677c648c in statistics_thread_runner (arg=arg@entry=0x0) at stats.c:233 #9 0x00007fab97f3dd9f in lmgr_thread_launcher (x=0x55a069847448) at lockmgr.c:928 #10 0x00007fab96774494 in start_thread (arg=0x7fab87fff700) at pthread_create.c:333 #11 0x00007fab95a15aff in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
It tries to connect to connect to a storage daemon, but fails (weirdly) to determine the host. Have you enabled http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveDirStorageCollect%20Statistics for any storage daemon? Have you some none working SDs? -- Jörg Steffens joerg.steff...@bareos.com Bareos GmbH & Co. KG Phone: +49 221 630693-91 http://www.bareos.com Fax: +49 221 630693-10 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 Komplementär: Bareos Verwaltungs-GmbH Geschäftsführer: S. Dühr, M. Außendorf, Jörg Steffens, P. Storz -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
