OPNsense Forum

English Forums => 26.1 Series => Topic started by: DiskWizard001 on March 06, 2026, 06:16:53 PM

Title: Upgrade went wrong
Post by: DiskWizard001 on March 06, 2026, 06:16:53 PM
***GOT REQUEST TO UPDATE***
Currently running OPNsense 26.1.3 (amd64) at Fri Mar  6 19:59:05 MSK 2026
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
SunnyValley repository is up to date.
All repositories are up to date.
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
SunnyValley repository is up to date.
All repositories are up to date.
Checking for upgrades (259 candidates): .......... done
Processing candidates (259 candidates): . done
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
   opnsense-26.1.3 [OPNsense] (Vital flag changed: 'true' -> 'false')

Number of packages to be reinstalled: 1

6 MiB to be downloaded.
[1/1] Fetching opnsense-26.1.3: .......... done
Checking integrity... done (0 conflicting)
[1/1] Reinstalling opnsense-26.1.3...
[1/1] Extracting opnsense-26.1.3: .......... done
Stopping configd...done
Resetting root shell
Updating /etc/shells
Unhooking from /etc/rc
Unhooking from /etc/rc.shutdown
Updating /etc/shells
Registering root shell
Hooking into /etc/rc
Hooking into /etc/rc.shutdown
Starting configd.
>>> Invoking update script 'refresh.sh'
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense SunnyValley
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.

Stuck completely ..... while Internet connection still working after reboot.
Title: Re: Upgrade went wrong
Post by: ezhik on March 06, 2026, 06:46:24 PM
Exactly same thing happened to me. I rebooted after that and it was fine.

EDIT: actually no. check for updates reports a segmentation fault for one of the packages.

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 26.1.3 (amd64) at Fri Mar  6 12:52:54 EST 2026
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching data: ....... done
Processing entries: .......... done
OPNsense repository update completed. 931 packages processed.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
Fetching data: .. done
Processing entries: .. done
SunnyValley repository update completed. 15 packages processed.
All repositories are up to date.
Child process pid=88379 terminated abnormally: Segmentation fault
Upgrading package manager from version '2.5.1' to '2.3.1_1'
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
OPNsense is up to date.
Checking integrity... done (0 conflicting)
Your packages are up to date.
Child process pid=99031 terminated abnormally: Segmentation fault
Checking for upgrades (198 candidates): .......... done
Processing candidates (198 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***
Title: Re: Upgrade went wrong
Post by: franco on March 06, 2026, 06:57:40 PM
You installed the FreeBSD package manager version, which isn't good.

>   opnsense-26.1.3 [OPNsense] (Vital flag changed: 'true' -> 'false')

This looks like a weird database bug. Vital flag is never removed.

Try this first...

# opnsense-revert pkg


Cheers,
Franco
Title: Re: Upgrade went wrong
Post by: ezhik on March 06, 2026, 07:11:56 PM
Quote from: franco on March 06, 2026, 06:57:40 PMYou installed the FreeBSD package manager version, which isn't good.

>   opnsense-26.1.3 [OPNsense] (Vital flag changed: 'true' -> 'false')

This looks like a weird database bug. Vital flag is never removed.

Try this first...

# opnsense-revert pkg


Cheers,
Franco

Did not work.

Had to:
# cd /tmp
# curl "https://pkg.opnsense.org/FreeBSD:14:amd64/26.1/MINT/26.1.3/latest/All/pkg-2.3.1_1.pkg" --output pkg-2.3.1_1.pkg
# pkg install pkg-2.3.1_1.pkg
# opnsense-revert pkg

How do we fix the "Vital" flag now?
Title: Re: Upgrade went wrong
Post by: franco on March 06, 2026, 08:03:29 PM
# opnsense-revert opnsense


Cheers,
Franco
Title: Re: Upgrade went wrong
Post by: DiskWizard001 on March 06, 2026, 10:16:15 PM
Quote from: ezhik on March 06, 2026, 06:46:24 PMExactly same thing happened to me. I rebooted after that and it was fine.

EDIT: actually no. check for updates reports a segmentation fault for one of the packages.

***GOT REQUEST TO CHECK FOR UPDATES***
Currently running OPNsense 26.1.3 (amd64) at Fri Mar  6 12:52:54 EST 2026
Fetching changelog information, please wait... done
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching data: ....... done
Processing entries: .......... done
OPNsense repository update completed. 931 packages processed.
Updating SunnyValley repository catalogue...
Fetching meta.conf: . done
Fetching data: .. done
Processing entries: .. done
SunnyValley repository update completed. 15 packages processed.
All repositories are up to date.
Child process pid=88379 terminated abnormally: Segmentation fault
Upgrading package manager from version '2.5.1' to '2.3.1_1'
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
OPNsense is up to date.
Checking integrity... done (0 conflicting)
Your packages are up to date.
Child process pid=99031 terminated abnormally: Segmentation fault
Checking for upgrades (198 candidates): .......... done
Processing candidates (198 candidates): . done
Checking integrity... done (0 conflicting)
Your packages are up to date.
***DONE***

Yes, this is the real problem, maybe try to update from console ?
Title: Re: Upgrade went wrong
Post by: DiskWizard001 on March 06, 2026, 10:18:39 PM
Quote from: franco on March 06, 2026, 06:57:40 PMYou installed the FreeBSD package manager version, which isn't good.

>   opnsense-26.1.3 [OPNsense] (Vital flag changed: 'true' -> 'false')

This looks like a weird database bug. Vital flag is never removed.

Try this first...

# opnsense-revert pkg


Cheers,
Franco
There was an error about Segmentation Fault first, red popup.
Title: Re: Upgrade went wrong
Post by: ezhik on March 06, 2026, 10:41:15 PM
Quote from: franco on March 06, 2026, 08:03:29 PM# opnsense-revert opnsense


Cheers,
Franco

What is expected here? Doesn't look like it worked as expected either:


root@opnsense:~ # opnsense-revert opnsense
pkg-static: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
pkg-static: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
Fetching meta.conf: 100%    179 B   0.2kB/s    00:01   
SunnyValley repository is up to date.
All repositories are up to date.
pkg-static: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
The following packages will be fetched:

New packages to be FETCHED:
        opnsense: 26.1.3 (6 MiB: 100.00% of the 6 MiB to download)

Number of packages to be fetched: 1

The process will require 6 MiB more space.
6 MiB to be downloaded.
Fetching opnsense-26.1.3.pkg: 100%    6 MiB   6.1MB/s    00:01   
pkg-static: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
opnsense-26.1.3: already unlocked
Updating OPNsense repository catalogue...
OPNsense repository is up to date.
Updating SunnyValley repository catalogue...
Fetching meta.conf: 100%    179 B   0.2kB/s    00:01   
SunnyValley repository is up to date.
All repositories are up to date.
pkg-static: warning: database version 37 is newer than libpkg(3) version 36, but still compatible
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
        opnsense-26.1.3 [OPNsense]

Number of packages to be reinstalled: 1
[1/1] Reinstalling opnsense-26.1.3...
[1/1] Extracting opnsense-26.1.3: 100%
Stopping configd...done
Resetting root shell
Updating /etc/shells
Unhooking from /etc/rc
Unhooking from /etc/rc.shutdown
Updating /etc/shells
Registering root shell
Hooking into /etc/rc
Hooking into /etc/rc.shutdown
Starting configd.
>>> Invoking update script 'refresh.sh'
Flushing all caches...done.
Writing firmware settings: FreeBSD OPNsense SunnyValley
Writing trust files...done.
Scanning /usr/share/certs/untrusted for certificates...
Scanning /usr/share/certs/trusted for certificates...
Scanning /usr/local/share/certs for certificates...
certctl: No changes to trust store were made.
Writing trust bundles...done.
Configuring login behaviour...done.
Configuring cron...done.
Configuring system logging...done.
=====
Message from opnsense-26.1.3:

--
One step ahead, one step behind it, now you gotta run to get even
pkg-static: warning: database version 37 is newer than libpkg(3) version 36, but still compatible