The other two daemons started up fine.
--
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
Sorry, I'm out of ideas, I don't have the knowledge needed under Solaris.
Did the other daemon works like the simpler bareos-fd -d200 -t
On October 15, 2017 7:08:01 PM GMT+02:00, Michael Masterson
wrote:
>Config info:
>
> Host: x86_64-pc-solaris2.11
Config info:
Host: x86_64-pc-solaris2.11 -- solaris 5.11
Bareos version: Bareos 17.2.4 (21 Sep 2017)
Distribution: solaris
Source code location: .
Modify package list:
Install binaries:
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
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