Technical Tip: Understanding the log message 'Failed to perform system configuration backup'

[kwcheng__FTNT]

Description	This article describes the typical circumstances behind the 'Failed to perform system configuration backup'.
Scope	FortiAuthenticator.
Solution	Event ID 10502 describes that the Fortiauthenticator failed to perform a system configuration backup. The sample system event message(s) will be looked like below: date=2025-03-03 time=21:09:52+0000 oid=53344 logid=10502 cat="Event" subcat="Admin Configuration" level="error" nas="" action="" status="" msg="Failed to perform system configuration backup: pg_dump: [archiver (db)] query failed: ERROR: cache lookup failed for function 55555#012pg_dump: [archiver (db)] query was: SELECT t.tgname, t.tgfoid::pg_catalog.regproc AS tgfname, pg_catalog.pg_get_triggerdef(t.oid, false) AS tgdef, t.tgenabled, t.tableoid, t.oid, t.tgisinternal FROM pg_catalog.pg_trigger t LEFT JOIN pg_catalog.pg_depend AS d ON d.classid = 'pg_catalog.pg_trigger'::pg_catalog.regclass AND d.refclassid = 'pg_catalog.pg_trigger'::pg_catalog.regclass AND d.objid = t.oid LEFT JOIN pg_catalog.pg_trigger AS pt ON pt.oid = refobjid WHERE t.tgrelid = '11111'::pg_catalog.oid AND (NOT t.tgisinternal)" user="admin" date=2025-03-03 time=22:43:52+0000 oid=177766 logid=10502 cat="Event" subcat="Admin Configuration" level="error" nas="" action="" status="" msg="Failed to perform system configuration backup: pg_dump: [archiver (db)] query failed: ERROR: cache lookup failed for function #6666#012pg_dump: [archiver (db)] query was: SELECT t.tgname, t.tgfoid::pg_catalog.regproc AS tgfname, pg_catalog.pg_get_triggerdef(t.oid, false) AS tgdef, t.tgenabled, t.tableoid, t.oid, t.tgisinternal FROM pg_catalog.pg_trigger t LEFT JOIN pg_catalog.pg_depend AS d ON d.classid = 'pg_catalog.pg_trigger'::pg_catalog.regclass AND d.refclassid = 'pg_catalog.pg_trigger'::pg_catalog.regclass AND d.objid = t.oid LEFT JOIN pg_catalog.pg_trigger AS pt ON pt.oid = refobjid WHERE t.tgrelid = '22222'::pg_catalog.oid AND (NOT t.tgisinternal)" user="admin" Workaround: This event log can be possibly related to a database error which can cause the HA cluster to be out of sync. To quickly resolve this error, a factory reset is suggested. Just restore the backup configuration or pull the configuration again from the primary unit after a factory reset.