Cannot Upgrade to 19.1 from 18.7.10_4

[misterj]

Hi all

I am running 18.7.10_4 and for some reason, I cannot get the upggade to 19.1 to work.

I've tried via the GUI and also via the raw console. In both cases I get a few reboots and then it boots back into 18.7.10_4. So I am assuming that the upgrade is failing somewhere.

What information can I provide or logs can I comb through to get some help?

Thanks

[smooney]

You will need to give some kind of error message or the output from the update console

[misterj]

That's just the problem. There is nothing that prints out.

I've watched from the raw console and it downloads the tar, them the txz, then it reboots to install and apply them, then it reboots again and back into 18.7.10_4.

Is there an update.log or something in Opnsense that might have the information?

[cguilford]

When you unlock the upgrade, are you doing Update or Upgrade?  Once you unlock it you have to hit the "Update" I believe it's the upper button and not the "Upgrade".  So I would do the Unlock again if it's still there and then try Update not upgrade.

[misterj]

I'll give that a shot and see what difference it makes.

For what it's worth, I've tried typing in 19.1 from the raw console (not ssh) and I'm still not getting any joy.

I'll see how that goes. Thanks!

[misterj]

Nope, that doesn't work. Using Update Now instead of Upgrade Now after doing the unlock upgrade makes no difference.

I've found /var/log/bsdinstaller/ - is there anything that might have an error message in here?

This is really starting to get frustrating...

[newsense]

Please try the following:

Change the mirror, Save, Check for Updates

[misterj]

Didnt work either.
Changed to the Opnsense Amsterdam mirror from default.

I changed the mirror in settings, did an Check for updates, Update now, reboot, check for updates, unlock upgrade, upgrade now.

Still on 18.7.10_4.

I'm starting to wonder if this is something like hardware, EFI vs BIOS or something...

[newsense]

Unlikely, maybe space related ?

You didn't mention whether is a physical box (and specs) or a VM (which could be snapshoted) but your easiest bet would be grabbing the installer for 19.1 and importing the configuration in the process. Make sure you have a backup just in case.

Also, for a physical box, making sure you have the latest BIOS/Firmware would be generally helpful and highly recommended.

[misterj]

Physical box. It's not space related - the disk is 120Gb in size and logs are being rotated. UI says only 5Gb is being used.

Box is running an Intel 7th Gen Celeron with 4Gb of RAM which is probably overkill for what I need, but that's the specs.

Starting to think that this may be the case... (do an import of config afterwards).

[kuerious]

My turn to chime-in.

I am having exactly this same issue. I started at 18.7.10_4, OpenSSL edition on the Protectli FW4A w/ 8GB:
https://i.imgur.com/GxDdDg2.png

From there, back at the release of 19.1 (not the now-changed 19.1.1), I followed ALL of the steps listed in order. Then I scoured the forums, and tried many different things. And I even took screenshots as I went along.

* Attempted to use the "Update" instead of the "Upgrade" button, makes no difference:
https://i.imgur.com/urtUglm.png

* Sometimes I'd get this message:
https://i.imgur.com/GNpTUU3.png

* Other times, I'd get this one:
https://i.imgur.com/ZsFO86I.png

* The system rebooted after actually showing it downloading the 19.1 images & kernel:
https://i.imgur.com/CE2eHvV.png

* No matter what, trying an upgrade looked like it was going to work, using "Unlock" and "Upgrade":
https://i.imgur.com/Wf5ebgx.png

Steps taken:
- Changed mirror from "default" to "Leaseweb", ran "updates", it DL'ed 18.7.10_4 (again), and rebooted:
**Note: lost this screenshot**

- Considered changing from "default" (currently "OpenSSL") over to "LibreSSL" but wasn't sure if it was HW-specific or just a choice:
https://i.imgur.com/XtyXW9s.png

I looked through all of the logs that made logical sense, looking for "fail"/"failure"/"warning" and all the other ones...; I tried updating from the console/CLI (using both "Y" and "19.1"); I dug through so many forum posts I fell asleep at my keyboard. I still haven't found the "right" or "wrong" thing I'm doing/not-doing so as to make this work.

I'm not really ready to take down the internet for half of a day just to reinstall my whole install. And while I have an ESXi server, it'll still take half of a day to get a new VM up and then re-route the networking.

Does ANYONE know what's going on or causing this problem? :'(  ... HELP! ...

[newsense]

Can you try selecting OpenSSL, Save, check for updates, 12 and confirm with 19.1 ?

Note that a few reboots will happen automatically and you should be on 19.1.1 at the end

[misterj]

No change with changing to OpenSSL either.

In the end, I got tired of pissing about and just did the reinstall and a reupload of my config which... doesnt reinject your plugins yay!

So I am going through that process now.

Pretty disappointed with this upgrade experience to be honest.

I think I have spent more time pissing about trying to get it to work properly than the upgrade took (something like maybe 8 minutes in total including the reupload of the config?)

[newsense]

The worst thing about it is that the devs have no error logs about what went wrong, and while the best assumption right now would likely go towards a regression on the BSD side of things we'll never really know...

As for the upgrade experience overall, I wouldn't pin an opinion on a failed upgrade and for what it's worth given the extent of the changes in 19.1 and the addition of HBSD thanks to the great work put in by lattera and his team I would say that overall it's been quite stellar, with a few minor glitches and regressions that were at the end of the day to be expected given time and resources.

Glad it all worked out for you though.

[misterj]

The worst thing about it is that the devs have no error logs about what went wrong, and while the best assumption right now would likely go towards a regression on the BSD side of things we'll never really know...

I'm thinking I should log a feature request for this, because honestly it's a 100% requirement. I would have been happy to self diagnose if there was a log provided.

The only things that I can think of as to the failure would be one of the messages I saw on the raw console. I could see the message "Install Opnsense 19.1.txz" followed by "Please reboot" and it would reboot... into 18.7. So clearly either the install failed (which failed very quickly as the time between the Install message and reboot was less than 30 seconds) or there was an issue writing to disk or something. Any log would have been fine.

As for the upgrade experience overall, I wouldn't pin an opinion on a failed upgrade

The upgrade from 18.1 to 18.7 was really smooth. I barely noticed it. The point updates have always been really good. I really like Opnsense's development model and that the team develops regularly. That's half of why I moved to Opnsense - because of the pace of development and delivery of bug fixes and the like.

And this is where the disappointment is born from. I'm sure 19.7 will be a lot smoother, but right now I am just annoyed, mostly, at the lack of logs rather than the upgrade failing.