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 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. >> >> > > 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 > > This occurred at the time my regular scheduled backup was to begin. I had > upgraded to 1.38.10 from 1.38.9 on 6/19 in the afternoon- several hours > before the next backup was to begin. I restarted all of the Bacula services > like I always do after each upgrade. All of the upgrades up until this one > went smooth. Running FreeBSD 6.0 Stable. > > Will see how tonight's backup goes. > > ~Doug > > > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > > Hello there.
I don't have any logs but dir and sd just going down (1.38.10) (at night), after reset them I see only director is going down at scheduled time. -- Przemysław Staniszewski _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
