pfSense is restoring the configuration
-
Hello,
yesterday i found the following message on my pfsense. Nobody has done a restore so the question is what has happened?
this is a virtualized pfsense 2.3.5-RELEASE-p2 (i386)thank you
-
I don't know why, sorry, but I know you'll get slammed for running a version that's been EOL for 2 years... Doesn't your hardware support x64? Easy enough to reinstall the latest and restore your config.
-
ok, other thoughts? :)
-
Nope..
-
ok thanks.
it will be a mystery :D
-
Why would anyone care about some odd event you saw on over 2 years EOL version.. Really!
-
It's not a mystery. That happens when you do something which causes invalid XML to be formed. Usually that means you put an international character in a field that doesn't support it. On a version that old, it's much more likely to happen.
-
@jimp ok i see, but is this normal that this happens without even touching this pfsense? because nobody has touched it.
-
No, only when a configuration change has been made which causes the problem.
There is another explanation, though, which is that your storage is failing and the config.xml file cannot be fully read from the disk.
If the OS is years out of date, odds are the hardware is aging as well.
-
@johnpoz said in pfSense is restoring the configuration:
Why would anyone care about some odd event you saw on over 2 years EOL version.. Really!
because maybe this is something that could happen on the new version as well?! who knows...
-
@jimp this is a VM machine. Other 30 or more machines are running on this server and we did not notice any disruption or other issues on the services. I don't think it is the hardware but will check the logs of the storage array and other stuff.
Regarding config changes, they are all done through the web gui. Anyway i will try to replace this VM with the latest version of pfSense.thank you
-
Check the contents of
/conf/config.xmland compare it with the rejected config in/conf/config.xml.badand see what the difference is. -
@jimp seems there is no config.xml.bad
-
Back then it might have been wiped out automatically. The error was from two days ago in your screenshot, though. I'd still say it was a failed attempt to change a setting to something with an international character.
No matter what, though, the best path forward is to upgrade.
