Re: Hung jobs: continued diagnosis

On 2020-07-15 01:50, Sven Hartge wrote:

> Looking at my logs, I have seen the same in my 9.6.5 installation on 
> Debian 10:
> 
> Excerpts from Error/Canceled-Mails:
> 
> -----
> 
> 24-Jun 00:02 back-dir JobId 585301: Error: bdb.h:140 bdb.h:140 update 
> UPDATE Job SET JobStatus='R',Level='I',StartTime='2020-06-24 
> 00:02:58',ClientId=73,JobTDate=1592949778,PoolId=7,FileSetId=427 WHERE 
> JobId=585301 failed:
> Deadlock found when trying to get lock; try restarting transaction
> 
> 24-Jun 00:02 back-dir JobId 585301: Fatal error: bdb.h:140 update UPDATE 
> Job SET JobStatus='R',Level='I',StartTime='2020-06-24 
> 00:02:58',ClientId=73,JobTDate=1592949778,PoolId=7,FileSetId=427 WHERE 
> JobId=585301 failed:
> Deadlock found when trying to get lock; try restarting transaction
> 
> -----
> 
> 28-Jun 00:02 back-dir JobId 586375: Error: bdb.h:140 bdb.h:140 update 
> UPDATE Job SET JobStatus='R',Level='I',StartTime='2020-06-28 
> 00:02:24',ClientId=149,JobTDate=1593295344,PoolId=7,FileSetId=153 WHERE 
> JobId=586375 failed:
> Deadlock found when trying to get lock; try restarting transaction
> 
> 28-Jun 00:02 back-dir JobId 586375: Fatal error: bdb.h:140 update UPDATE 
> Job SET JobStatus='R',Level='I',StartTime='2020-06-28 
> 00:02:24',ClientId=149,JobTDate=1593295344,PoolId=7,FileSetId=153 WHERE 
> JobId=586375 failed:
> Deadlock found when trying to get lock; try restarting transaction
> 
> -----
> 
> 09-Jul 00:04 back-dir JobId 589511: Error: bdb.h:140 bdb.h:140 update 
> UPDATE Job SET JobStatus='R',Level='I',StartTime='2020-07-09 
> 00:04:16',ClientId=255,JobTDate=1594245856,PoolId=7,FileSetId=408 WHERE 
> JobId=589511 failed:
> Deadlock found when trying to get lock; try restarting transaction
> 
> 09-Jul 00:04 back-dir JobId 589511: Fatal error: bdb.h:140 update UPDATE 
> Job SET JobStatus='R',Level='I',StartTime='2020-07-09 
> 00:04:16',ClientId=255,JobTDate=1594245856,PoolId=7,FileSetId=408 WHERE 
> JobId=589511 failed:
> Deadlock found when trying to get lock; try restarting transaction
> 
> -----
> 
> This is with a remote MariaDB 10.3 server, i.e. the database is not on 
> the same server but exclusive for Bacula.


Thanks for confirming, Sven.  A deadlock should not be a fatal error, it
should be retried.


-- 
  Phil Stracchino
  Babylon Communications
  [email protected]
  [email protected]
  Landline: +1.603.293.8485
  Mobile:   +1.603.998.6958