> On Wed, 21 Jun 2006 14:30:10 -0700, Doug Sampson said:
>
> > > This is a FYI.
> > >
> > > Got the following message in bconsole:
> > >
> > > 20-Jun 00:05 aries-dir: ABORTING due to ERROR in bsys.c:375
> > > Mutex lock failure. ERR=Resource deadlock avoided
> > > 20-Jun 00:05 aries-dir: Fatal
> > This is a FYI.
> >
> > Got the following message in bconsole:
> >
> > 20-Jun 00:05 aries-dir: ABORTING due to ERROR in bsys.c:375
> > Mutex lock failure. ERR=Resource deadlock avoided
> > 20-Jun 00:05 aries-dir: Fatal Error because: Bacula
> interrupted by signal
> > 11: Segmentation violation
Doug Sampson wrote:
>> Yesterday I upgraded Bacula on FreeBSD-4.9 from 1.38.9 to
>> 1.38.10. I hadn't
>> seen Bacula crashing or anything before, but today bacula-dir
>> wasn't running
>> and message in console said:
>>
>> 15-Jun 22:00 mybacula-dir: ABORTING due to ERROR in bsys.c:375
>> Mutex
> Yesterday I upgraded Bacula on FreeBSD-4.9 from 1.38.9 to
> 1.38.10. I hadn't
> seen Bacula crashing or anything before, but today bacula-dir
> wasn't running
> and message in console said:
>
> 15-Jun 22:00 mybacula-dir: ABORTING due to ERROR in bsys.c:375
> Mutex lock failure. ERR=Resource
Hi.
Yesterday I upgraded Bacula on FreeBSD-4.9 from 1.38.9 to 1.38.10. I hadn't
seen Bacula crashing or anything before, but today bacula-dir wasn't running
and message in console said:
15-Jun 22:00 mybacula-dir: ABORTING due to ERROR in bsys.c:375
Mutex lock failure. ERR=Resource deadlock avoi
