Update Clarity
-
I have had a search around but couldn't find the exact answer. Been using pfsense for many years. And updates appeared and rolled out flawlessly.
My dashboard says
And my update area show this.
Question should I be running on 2.7.2? If so how do I go about initiating the upgrade or do I have to update to 2.7.1 first? Some advice would be great thanks. As I sy this has been seemless before and we have this little quirk.
Advice appreciated thanks.
this is community edition. yes it appears outdated I know. But it didn't raise an alarm for being out of date.
Q\ Will running update from console at console pull the latest version automatically?
-
@zoqask If offered there, you can skip versions.
Also see https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#troubleshooting
-
@zoqask re: console, you still need to set the branch. That’s required going forward instead of leaving it at “current.”
-
Thanks for that so selecting 2.7.2 and running a console update should do the trick then by the sounds of it.
I have an identical hardware box sitting in the corner. gave it a wan and it seemed to progress through the updates right up to 2.8 using the command console.
finger crossed for this box although I can export the config over to this other box for test knowing it would actually upgrade is it should helps.
-
Yup you can go straight to 2.7.2. Then you will see 2.8.0 and can upgrade to that. Or wait for 2.8.1 real-soon-now.
-
Thanks all.
I tried it from command line and I get this t then just exits.
*Question* Any ideas what command I can run in the shell to pull the 2.7.2? Really not sure. For some reason I think the update has borked somewhere hence the lack of dashboard notifications.
My gui settings are
-
Run at the command line:
certctl rehash
Then try again. -
Thanks for that. In reality and from my screenshots previous what do you think has happened to cause this?. I know you don't have a crystal ball but identifying why these updates didn't register / notify would be good the know.
-
@zoqask Well per the link I posted above, "Due to changes in pkg, the new version of pkg may not be able to properly locate and use the CA trust store when running on the previous version before upgrading." A lot of (all) people had to run that command to be able to update.
-
Ok understood. I will try it out of hours and see if it gets a result.
Thanks in advance to both of you if t does
.If it doesn't work I will post a screenshot. Hopefully if this is a common issue indeed its tried / tested and a recurring theme is the past (As you say). Having had others wipe the sweat from their brow hopefully I can as well.
-
Yup it was a known bug in 2.7.0. It's fixed in 2.7.2 forward.
-
Ran certctl rehash
I now get update request. So its a case of waiting for the right time out of hours now and trying it out.
Out of interest, when you progress in the command line and is says saving old kernel etc. If the install fails for some reason how do you revert back to the previous version. This may be an incredibly overly simplified question but some sort of command line fu would be helpful for those of us that aren't clocking into these appliances every day.
-
You can choose to boot the old kernel at the bootloader menu. But that's only the kernel, it will still fail to boot if the rest of the system is broken.
In ZFS you can create a snapshot boot environment before upgrading you can roll back to. Plus does that automatically.
