OPNsense Forum

Archive => 18.7 Legacy Series => Topic started by: mausy5043 on September 02, 2018, 11:34:26 am

Title: Stuck on 18.1 during upgrade
Post by: mausy5043 on September 02, 2018, 11:34:26 am
I must have clicked the wrong button somewhere, because I seem to have upgraded successully to 18.7 but then accidentally clicked the Update button which took me back to 18.1 and ow I'm stuck.

On the GUI I am at "18.1.13 (installed)"
On the CLI I am at
Code: [Select]
# opnsense-update -v
18.1.11-amd64

When I click the "Unlock this upgrade" button in the CLI and then click the "Upgrade now"
it says that its fetching the 18.7 packages
Then there's an error when fetching the kernel package:
Code: [Select]
pgrep cannot get process list [kvm_getprocs: No such process]
This is followed by extraction of the packages and seemingly succesful installation.
(see attachment)

After the upgrade I'm still on
OPNsense 18.1.13_1-amd64
FreeBSD 11.1-RELEASE-p11


I can SSH into the box.
Any commands I might try to force this?
Title: Re: Stuck on 18.1 during upgrade
Post by: weust on September 02, 2018, 01:59:05 pm
I wouldn't know the commands, but if you're in a hurry or if it's a home setup, I would backup the config file, re-install and restore the config.
Title: Re: Stuck on 18.1 during upgrade
Post by: mausy5043 on September 02, 2018, 06:54:42 pm
fixed it by uninstalling python3
Title: Re: Stuck on 18.1 during upgrade
Post by: weust on September 03, 2018, 12:36:32 pm
How did you figure that one out?
Title: Re: Stuck on 18.1 during upgrade
Post by: franco on September 03, 2018, 03:44:25 pm
If I remember correctly the same happened for 17.7 -> 18.1. I haven't forgotten about it. A ticket was opened with pkg to discuss what this tries to do and how it could be fixed. I especially do not know what "replacements" are and how they are used. Some time during the upgrade it asks for python3 to be replaced by python2 which is already installed and the "all yes" gives the wrong answer because the question is inverted. It's a pretty funky situation.

Here's the feedback I have gotten so far:

https://github.com/freebsd/pkg/issues/1687

;)


Cheers,
Franco