https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162015-10-07T12:21:08ZpfSense bugtrackerpfSense - Bug #5285: Failsafe modehttps://redmine.pfsense.org/issues/5285?journal_id=214742015-10-07T12:21:08ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li></ul><p>what specifically did you do to break it? that looks like $config is no longer an array and is within the config upgrade code which wouldn't be touched unless an upgrade had just happened and the config needed to be upgraded.</p> pfSense - Bug #5285: Failsafe modehttps://redmine.pfsense.org/issues/5285?journal_id=214832015-10-07T13:20:03ZFernando Munoz
<ul></ul><p>Unfortunately, I don't know for sure, I installed all the available packages and tried to use invalid data in every input fied I see to check for vulnerabilities. The message on the screen seems to be a warning only however it keeps calling the config.lib.inc file all the time and it doesn't continue booting, I had to reinstall.</p> pfSense - Bug #5285: Failsafe modehttps://redmine.pfsense.org/issues/5285?journal_id=214852015-10-07T16:33:49ZChris Buechlercbuechler@gmail.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Not a Bug</i></li></ul><p>if the XML is invalid, and there are backups in the config history, it'll restore from there. So there is a "failsafe" there, which works in normal circumstances. "Installing every package and saving invalid data everywhere" isn't normal circumstances. Granted it shouldn't fail, but will need to know more about what triggers the failure to do anything. There is probably one or more package bugs there, if you find which, please report that as their own issues.</p>