> On Jan 18, 2019, at 11:24 AM, Josh Fisher wrote:
>
> 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_
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),
W dniu 2019-01-17 o 18:17, Dan Langille pisze:
> 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 do
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
