Upgraded from 2.4.5 to 2.5.2 and having problems with config file restore on every reboot.

bjurkovski

I recently re-installed pfSense 2.5.2 using my config file from from 2.4.5 and other than an issue with Unbound failing to start until disabling python seemed to complete successfully.

Now I'm having an issue where my changes are being lost on reboot and I'm getting the following message upon restart: "pfSense is restoring the configuration /tmp/mnt/cf/config.xml @ 2021-07-14 14:08:45"

I can't seem to find any reason why the config would be reverting and this even happens when rebooting without making any changes to the config.

Any ideas on what might be causing this issue?

Thanks!

Gertjan

First thing to test :
Reboot from the console, and choose the option : 'Reboot and run a filesystem check'.

After that, during booting, check that it says it boots from a "clean file system".

@bjurkovski said in Upgraded from 2.4.5 to 2.5.2 and having problems with config file restore on every reboot.:

Unbound failing to start with Python

pfBlockerNG make sit's own file system, which is mounted on /var/unbound/

Check /var/unbound/var/log/pfblockerng/ - if the log files are to big, they eat up all the space and pythin (unbond) can't log any more, it 'explodes'.

Typical is :

-rw-------  1 unbound  unbound  21162361 Jul 15 10:59 dns_reply.log
-rw-------  1 unbound  unbound   2680217 Jul 15 10:46 dnsbl.log
-rw-r--r--  1 root     wheel           0 Dec  9  2020 dnsbl_error.log
-rw-------  1 root     wheel       61587 Jul 15 06:00 dnsbl_parsed_error.log
-rw-------  1 root     wheel       20642 Jul 15 06:00 extras.log
-rw-------  1 root     wheel     3322237 Jul 15 09:28 ip_block.log
-rw-r--r--  1 root     wheel         120 Jul  8 03:00 maxmind_ver
-rw-------  1 root     wheel     1986670 Jul 15 06:00 pfblockerng.log
-rw-r--r--  1 unbound  unbound         0 Jul  9 15:42 py_error.log
-rw-------  1 unbound  unbound  19249167 Jul 15 10:59 unified.log

bjurkovski

Thanks, I'll try the filesystem check.

I don't think is was a log file issue since is was a fresh reinstall using a previous config. I believe it was a missing dependency and that I wouldn't have had this problem if I had just disabled Python mode in my config before reinstalling. I was was able to change Unbound back to Python mode after installing pfBlockerNG.

fireodo

@bjurkovski said in Upgraded from 2.4.5 to 2.5.2 and having problems with config file restore on every reboot.:

I wouldn't have had this problem if I had just disabled Python mode in my config before reinstalling

I think this should get pinned because I run in this trouble too: If in the config, before reinstalling, the pfblockerng was in python mode then unbound is not working (he is missing the python module) and no packages can be installed because Url's cannot be resolved. So switching pfblockerng in unbound mode before save the config is the best way to workaround this issue.

Regards,
fireodo