https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162021-03-29T09:03:05ZpfSense bugtrackerpfSense - Bug #11748: Automated corruption recovery from cached ``config.xml`` backup files should check multiple backupshttps://redmine.pfsense.org/issues/11748?journal_id=527462021-03-29T09:03:05ZJim Pingle
<ul><li><strong>Subject</strong> changed from <i>Automatic restore of last backup config.xml failed during startup</i> to <i>Automatic restore of previous backup config.xml when detecting invalid configuration files should check multiple backups</i></li><li><strong>Target version</strong> set to <i>CE-Next</i></li></ul><p>Updating subject.</p>
<p>tl;dr appears to be: config.xml corrupt/missing, and most recent historical backup is also corrupt. It should keep checking older configurations until it finds a valid one.</p>
<p>In the boot log it appeared to keep trying the same old config multiple times rather than looking back further.</p> pfSense - Bug #11748: Automated corruption recovery from cached ``config.xml`` backup files should check multiple backupshttps://redmine.pfsense.org/issues/11748?journal_id=527842021-03-31T06:16:42ZViktor Gurov
<ul></ul><p><a class="external" href="https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/213">https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/213</a></p> pfSense - Bug #11748: Automated corruption recovery from cached ``config.xml`` backup files should check multiple backupshttps://redmine.pfsense.org/issues/11748?journal_id=527902021-03-31T08:06:09ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Pull Request Review</i></li></ul> pfSense - Bug #11748: Automated corruption recovery from cached ``config.xml`` backup files should check multiple backupshttps://redmine.pfsense.org/issues/11748?journal_id=534972021-05-11T15:06:53ZJim Pingle
<ul><li><strong>Plus Target Version</strong> set to <i>21.05</i></li></ul> pfSense - Bug #11748: Automated corruption recovery from cached ``config.xml`` backup files should check multiple backupshttps://redmine.pfsense.org/issues/11748?journal_id=536112021-05-12T07:11:57ZAnonymous
<ul><li><strong>Status</strong> changed from <i>Pull Request Review</i> to <i>Feedback</i></li></ul> pfSense - Bug #11748: Automated corruption recovery from cached ``config.xml`` backup files should check multiple backupshttps://redmine.pfsense.org/issues/11748?journal_id=536272021-05-12T07:20:08ZViktor Gurov
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Checking multiple backups when detecting invalid configuration. Fixes #11748" href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/40159e4f9fc2db7ac8a6a28a5f757e51e7975886">40159e4f9fc2db7ac8a6a28a5f757e51e7975886</a>.</p> pfSense - Bug #11748: Automated corruption recovery from cached ``config.xml`` backup files should check multiple backupshttps://redmine.pfsense.org/issues/11748?journal_id=536662021-05-12T13:58:50ZJim Pingle
<ul><li><strong>Subject</strong> changed from <i>Automatic restore of previous backup config.xml when detecting invalid configuration files should check multiple backups</i> to <i>Automated corruption recovery from cached ``config.xml`` backup files should check multiple backups</i></li></ul><p>Updating subject for release notes.</p> pfSense - Bug #11748: Automated corruption recovery from cached ``config.xml`` backup files should check multiple backupshttps://redmine.pfsense.org/issues/11748?journal_id=541022021-05-27T07:56:07ZJim Pingle
<ul><li><strong>Target version</strong> changed from <i>CE-Next</i> to <i>2.5.2</i></li></ul> pfSense - Bug #11748: Automated corruption recovery from cached ``config.xml`` backup files should check multiple backupshttps://redmine.pfsense.org/issues/11748?journal_id=541572021-05-28T12:22:19ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li><li><strong>Assignee</strong> set to <i>Viktor Gurov</i></li></ul><p>On a fresh VM I made a few changes, booted to single user mode and truncated the last few configs to 0 bytes, and then rebooted again. It successfully went back and found the most recent viable backup and restored that.</p>