Finally on 2.3.1: My experience (config file seemed to be corrupt)



  • Hi all.

    Finally I took the dive and spent several hours upgrading from 2.2.6 to 2.3.1 over the past weekend.

    The one thing that screwed me up badly, is that, after the upgrade, every boot would pause for 10-15 minutes with the message
    'Updating configuration' (or something to that effect) and my changes were NOT being saved (can we add an error/message when the system
    is not able to update the config file OR when changes cannot be saved to the config file?).

    This was obviously not going to get me anywhere, so I ended installing 2.3.1 from scratch and then importing only a few sections (ip aliases and fw rules) from my config file and then opened the config file in an editor and started to extract the sections for squid, suricata, etc. and pasting them to the new 2.3 config file.

    I could not find a glaring error in the config file and even checked the xml file against xml sanity checkers, but nothing. There seemed to be a couple of xml properties that were duplicated, which should not be a problem, but even then, how could the config file gotten corrupt (why did it work fine under 2.2.6?)?

    So I am now running 2.3.1_1 and everything is good, but I did notice some OS differences compared to my old 2.2.6 install:
    Difference in the fstab, it looks like now they are using labels to mount filesystems. I also noticed some 'journal' messages when doing a file system check, which bring us to my last point and suggestion:

    A new install would be recommended to all the old-timers like me that have had their pfsense running for the last 4-5 years and would NOT update the OS if you just do a regular update.

    FYI. My setup has been running under VMware ESXi (v. 6.0 currently) for years now, with both, pfsense, as the Internet facing fw and Untangle, as a 2nd fw (like the boot speed, their ad-blocker and IPS). All the people that 'automatically' put down a virtualized setup, really don't have an idea of what they are talking about. My guess is that they are simply afraid to try something 'crazy' (crazy is to stick with old beliefs and experiences and just believe what 'others' say).

    Thanks again to the pfsense team!



  • This seems to be happening to me when going from 2.3.0 to 2.3.1. I'm unable to save any of my settings with no error messages.

    Edit: This was unrelated and had to do with the new "Deny Config Write" privilege being automatically added to my existing LDAP based groups.



  • @naex:

    Edit: This was unrelated and had to do with the new "Deny Config Write" privilege being automatically added to my existing LDAP based groups.

    It was always there, config wasn't modified. It's just now being obeyed in that circumstance where it wasn't before.



  • @pppfsense:

    …..
    Difference in the fstab, it looks like now they are using labels to mount filesystems.
    ....

    Even when you skip a boat load of updates and upgrades, read all release info ;)


Log in to reply