Michael , as in the trace you give the coredump is happening when the command bareos-dir -t is run I would say that the associated configuration is not found at all : does /etc/bareos exist (or equivalent configuration place you decided during compilation /etc/bareos17/etc ?)
You should have the defaut structure etc/bareos/bareos-dir.d populated with default values (they are normaly build and installed) after the make make install part. On October 15, 2017 12:27:56 AM GMT+02:00, Michael Masterson <m...@siasl.net> wrote: >Solaris 11.3, x86, 17.2.4 compiles ok, but coredumps when starting the >director: > >[root@woden]# bareos-dir -t -d 900 (it cores with or without any >parameters). >Memory fault(coredump) >(/opt/bareos17) >[root@woden]# gdb bin/bareos-dir core >GNU gdb (GDB) 7.6 >Copyright (C) 2013 Free Software Foundation, Inc. >License GPLv3+: GNU GPL version 3 or later ><http://gnu.org/licenses/gpl.html> >This is free software: you are free to change and redistribute it. >There is NO WARRANTY, to the extent permitted by law. Type "show >copying" >and "show warranty" for details. >This GDB was configured as "i386-pc-solaris2.11". >For bug reporting instructions, please see: ><http://www.gnu.org/software/gdb/bugs/>... >Reading symbols from /opt/bareos17/bin/bareos-dir...done. >[New LWP 1] >[New LWP 1] >[Thread debugging using libthread_db enabled] >[New Thread 1 (LWP 1)] >Core was generated by `bareos-dir -t'. >Program terminated with signal 11, Segmentation fault. >#0 0xffff80ffbe56222a in bthread_mutex_lock_p (m=0xffff80ffbe6861b0 ><_ZL5mutex>, > file=0xffff80ffbe5331fd "mem_pool.c", line=145) at lockmgr.c:767 >767 self->pre_P(m, 0, file, line); >(gdb) bt >#0 0xffff80ffbe56222a in bthread_mutex_lock_p (m=0xffff80ffbe6861b0 ><_ZL5mutex>, > file=0xffff80ffbe5331fd "mem_pool.c", line=145) at lockmgr.c:767 >#1 0xffff80ffbe563b34 in sm_get_pool_memory (fname=0x431488 >"../lib/mem_pool.h", lineno=92, > pool=1) at mem_pool.c:145 >#2 0x000000000045e6ee in POOL_MEM::POOL_MEM (this=0xffff80ffbfffebe0) >at ../lib/mem_pool.h:92 >#3 0x0000000000467572 in get_configure_usage_string () at >dird_conf.c:1033 >#4 0x00000000004b1a6b in __static_initialization_and_destruction_0 >(__initialize_p=1, > __priority=65535) at ua_cmds.c:239 >#5 0x00000000004b1d74 in >_GLOBAL__sub_I__ZN9UAContext7executeEP12ua_cmdstruct () > at ua_cmds.c:2772 >#6 0xffff80ffbf5bb14f in call_array () from /lib/amd64/ld.so.1 >#7 0xffff80ffbf5bb2db in call_init () from /lib/amd64/ld.so.1 >#8 0xffff80ffbf5bb062 in is_dep_init () from /lib/amd64/ld.so.1 >#9 0xffff80ffbf5cb0fa in elf_bndr () from /lib/amd64/ld.so.1 >#10 0xffff80ffbf5ac4d3 in elf_rtbndr () from /lib/amd64/ld.so.1 >#11 0xffff80ffbf6cb720 in ?? () >#12 0x0000000000000000 in ?? () >(gdb) quit > > >Please let me know if there's more info I can provide. > >-- >You received this message because you are subscribed to the Google >Groups "bareos-devel" group. >To unsubscribe from this group and stop receiving emails from it, send >an email to bareos-devel+unsubscr...@googlegroups.com. >To post to this group, send email to bareos-devel@googlegroups.com. >For more options, visit https://groups.google.com/d/optout. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- You received this message because you are subscribed to the Google Groups "bareos-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-devel+unsubscr...@googlegroups.com. To post to this group, send email to bareos-devel@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
