Incrementals now failing

20 views
Skip to first unread message

Peter Kropf

unread,
Jul 26, 2024, 5:09:19 PM7/26/24
to bareos-users
My backups have been running without issue for a while but I'm starting to see this error:


26-Jul 07:46 bareos-dir JobId 3823: Fatal error: cats/sql_create.cc:817 Fill File table Query failed: INSERT INTO File (FileIndex, JobId, PathId, Name, LStat, MD5, DeltaSeq, Fhinfo, Fhnode) SELECT batch.FileIndex, batch.JobId, Path.PathId, batch.Name, batch.LStat, batch.MD5, batch.DeltaSeq, batch.Fhinfo, batch.Fhnode FROM batch JOIN Path ON (batch.Path = Path.Path) : ERR=ERROR:  relation "batch" does not exist
LINE 1: ..., batch.DeltaSeq, batch.Fhinfo, batch.Fhnode FROM batch JOIN...


Server director and storage are on version 23.0.2, client file daemon is on 23.0.4~pre113.6ea98eb40.

Help!

-- Peter

Sebastian Sura

unread,
Aug 2, 2024, 2:28:35 AM8/2/24
to bareos...@googlegroups.com

Hi Peter,

the batch table is a temporary table used by bareos during the backup process.  If you see this error, then it means that the director somehow lost connection to the pg database.  Can you make sure that your db is not getting restarted somehow or that the connection does not otherwise drop ?

Kind Regards,
Sebastian Sura

Am 26.07.24 um 23:09 schrieb Peter Kropf:
--
You received this message because you are subscribed to the Google Groups "bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bareos-users/5f0db329-9e3c-4e19-9171-2c198961d335n%40googlegroups.com.
-- 
 Sebastian Sura                  sebasti...@bareos.com
 Bareos GmbH & Co. KG            Phone: +49 221 630693-0
 https://www.bareos.com
 Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
 Komplementär: Bareos Verwaltungs-GmbH
 Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz

Bruno Friedmann (bruno-at-bareos)

unread,
Aug 5, 2024, 4:35:30 AM8/5/24
to bareos-users
Hi Peter,

Like Sebastian already mention it, pg drop the table, and it often happen when postgresql lack free temporary space.
Some operation especially virtual full, need lot of space, our best advise would be to kept 50% free space where you db is located.
Reply all
Reply to author
Forward
0 new messages