Have you tried with debug level increased, say using -d7 in the command
line? Maybe that would give a clue as to what it does prior to the segfault.
On 1/17/2019 12:17 PM, Dan Langille wrote:
I was noticing this in my /var/log/messages:
Jan 17 17:04:00 slocum kernel: pid 52623 (check_bacula), uid 181: exited on
signal 11
Jan 17 17:04:21 slocum kernel: pid 53805 (check_bacula), uid 181: exited on
signal 11
I tracked it down to a host which was not up:
$ time ./check_bacula -H tape02 -D fd -M nagios-mon -K '[redacted]'
Segmentation fault
real 1m15.101s
user 0m0.006s
sys 0m0.000s
Could someone else please try to replicate this situation for me please?
This check is being run on FreeBSD 12.0-RELEASE-p2 with check_bacula from
Bacula 9.2.2
Thank you.
--
Dan Langille - BSDCan / PGCon
d...@langille.org
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
