I had the same thing happen to me but before 2.4 came out. I have quite a few of these in production I don't know what I'll do. It seems like there are quite a few reports of 2.3 to 2.4 failing even on official Hardware.
Does anybody have any insight to what's going on? Ever since pfSense switched over to the new upgrade method it seems like every once in awhile an upgrade problem creeps up even on my end. I've seen quite a few instances of where I go to upgrade via the web GUI and it corrupts the package database. In fact I have one box right now that runs official Hardware that I think is stuck on 2.3 until I get to it physically. Why is the upgrade process so unstable all of a sudden? On Dec 5, 2017 4:48 PM, "Pete Boyd" <[email protected]> wrote: > On 05/12/2017 13:47, Eero Volotinen wrote: > > well. take backup of config and ask operator to reinstall box from usb > > stick & restore backup? > > Yeah. This went from bad to worse today, I eventually lost contact with > it, so this is what I'm going to do. > > Thanks for your help. > > > -- > Pete Boyd > > Open Plan IT - http://openplanit.co.uk > The Golden Ear - http://thegoldenear.org > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold > _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
