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 avoided
15-Jun 22:00 mybacula-dir: Fatal Error because: Bacula interrupted by signal 
11: Segmentation violation

The strange thing is that all the backups are scheduled to run at 23:05, as 
specified in default WeeklyCycle.

Could it be some new bug in bacula-dir?

Silver


_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to