Messages

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.

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?)

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).

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...

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...

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!

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?

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

Hi jelly-ck

Let me know how you go. This is the only thing stopping me from migrating to Opnsense.

So no one else uses Opnsense as an OpenVPN client to a 3rd party VPN provider and has successfully configured this?

I am looking to migrate to Opnsense from another platform and want to replicate my existing setup as much as possible.

On my existing platform, I have it running an OpenVPN client to a VPN provider and use a firewall rule on the LAN interface that says IPv4 * * * * gateway OPT1 client interface.

When I try to this with Opnsense I just get no IPv4 dataflow at all.

I have set the OpenVPN and the OPT1 interfaces to have IPv4 * * * * rules which replicates my existing setup. And yet it's still not working.

Packet captures just show no dataflow. I'm not blocking bogon or private networks.

Is there something I am missing?

Thanks