Rob, Arno, Thank you for taking an interest in my problem.
Answers to questions, as best as I can provide: > from Rob: > You mentioned that the last two admin jobs failed. Was that a typo? If not, > what errors did the last job (unmount, eject) give? The errors for jobid 27943 look very much like the errors for 27941. 08-Dec 14:21 linux2-dir JobId 27943: Fatal error: bdb.h:140 Update failed: affected_rows=0 for UPDATE Job SET JobStatus='R',Level=' ',StartTime='2025-12-08 14:21:57',ClientId=1,JobTDate=1765225317,PoolId=0,FileSetId=0 WHERE JobId=27943 08-Dec 14:21 linux2-dir JobId 27943: Fatal error: bdb.h:140 Update failed: affected_rows=0 for UPDATE Job SET JobStatus='f',Level=' ',StartTime='2025-12-08 14:21:57',ClientId=1,JobTDate=1765225317,PoolId=0,FileSetId=0 WHERE JobId=27943 08-Dec 14:21 linux2-dir JobId 27943: Warning: Error updating job record. bdb.h:140 Update failed: affected_rows=0 for UPDATE Job SET JobStatus='f',EndTime='2025-12-08 14:21:57',ClientId=1,JobBytes=0,ReadBytes=0,JobFiles=0,JobErrors=1,VolSessionId=0,VolSessionTime=0,PoolId=0,FileSetId=0,JobTDate=1765225317,RealEndTime='2025-12-08 14:21:57',PriorJobId=0,HasBase=0,PurgedFiles=0 WHERE JobId=27943 08-Dec 14:21 linux2-dir JobId 27943: Warning: Error getting Job record for Job report: ERR=sql_get.c:303 No Job found for JobId 27943 08-Dec 14:21 linux2-dir JobId 27943: Error: Bacula 9.6.7 (10Dec20): 08-Dec-2025 14:21:57 > I presume that the errors you provided from jid 27941 were from the bacula > database backup job. Please let us know if this is not the case. 27941 is the job that runs the Postgresql dump of the bacula database. Since it failed, no new dump was made that night. > Have you been able to run the bacula catalog dump successfully since the > errors? Yes, twice. The unmount/eject job has also run successfully twice. > Has this issue occurred previously? Yes, for one unmount/eject job in June of this year. However, the previous tape drive hardware (LTO-6) was failing at that time, so those errors were ignored. At this point, most relevant logs for that timeframe have been rotated (bacula an exception). > From Arno: > Even just checking via Bacula (through bconsole's sqlquery, a status dir or a > list command) or using the psql tool might reveal database problems. I was hoping that the bacula dbcheck tool might turn up something. However, today I tried llist command on jobs, media, pools, clients, volume -- no reported errors. > It is possible the connection of the DIR to the database engine was lost for > some reason, in that case, a restart of the DIR will be needed. I do not think that happened, since the 2nd Backup job (which followed the 2nd Admin job) ran to completion (though without an updated version of the bacula database dump). For context: Mount Tape (Admin) Extract databases (Admin) Full backup (Backup) Extract bacula database (Admin) [failed, bdb.h error] Backup bacula database (Backup) Unmount and eject tape (Admin) [failed, bdb.h error] Thanks again, Ken _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
