[SOLVED] Problem Updating 17.1.3 to 17.1.4

[sashxp]

Hi,

i get the following Error with the Update. Is it the right solution to unset the vital flag?  :o
I'll ask that, because i haven't done this in other updates...

bye
sash

***GOT REQUEST TO UPGRADE: all***
Updating OPNsense repository catalogue...
OPNsense repository is up-to-date.
All repositories are up-to-date.
Updating OPNsense repository catalogue...
OPNsense repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (37 candidates): .......... done
Processing candidates (37 candidates): .......... done
Checking integrity... done (1 conflicting)
  - py27-setuptools-32.1.0_1 conflicts with py27-setuptools27-32.1.0 on /usr/local/bin/easy_install
Cannot solve problem using SAT solver, trying another plan
Checking integrity... done (0 conflicting)
The following 38 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
   py27-sqlite3-2.7.13_7
   opnsense-17.1.3
   py27-setuptools27-32.1.0

New packages to be INSTALLED:
   py27-setuptools: 32.1.0_1

Installed packages to be UPGRADED:
   squid: 3.5.24 -> 3.5.24_2
   png: 1.6.28 -> 1.6.29
   pkgconf: 1.3.0_3 -> 1.3.0,1
   php70-zlib: 7.0.16 -> 7.0.17
   php70-xml: 7.0.16 -> 7.0.17
   php70-sqlite3: 7.0.16 -> 7.0.17
   php70-sockets: 7.0.16 -> 7.0.17
   php70-simplexml: 7.0.16 -> 7.0.17
   php70-session: 7.0.16 -> 7.0.17
   php70-pdo: 7.0.16 -> 7.0.17
   php70-openssl: 7.0.16 -> 7.0.17
   php70-mcrypt: 7.0.16 -> 7.0.17
   php70-ldap: 7.0.16 -> 7.0.17
   php70-json: 7.0.16 -> 7.0.17
   php70-hash: 7.0.16 -> 7.0.17
   php70-gettext: 7.0.16 -> 7.0.17
   php70-filter: 7.0.16 -> 7.0.17
   php70-dom: 7.0.16 -> 7.0.17
   php70-curl: 7.0.16 -> 7.0.17
   php70-ctype: 7.0.16 -> 7.0.17
   php70: 7.0.16 -> 7.0.17
   opnsense-update: 17.1.3 -> 17.1.4
   opnsense-lang: 17.1.3 -> 17.1.4
   ntp: 4.2.8p9_4 -> 4.2.8p10_2
   lzo2: 2.09 -> 2.10_1

Installed packages to be REINSTALLED:
   py27-ujson-1.35 (direct dependency changed: py27-setuptools)
   py27-requests-2.11.1 (direct dependency changed: py27-setuptools)
   py27-pytz-2016.10,1 (direct dependency changed: py27-setuptools)
   py27-netaddr-0.7.18 (direct dependency changed: py27-setuptools)
   py27-MarkupSafe-1.0 (direct dependency changed: py27-setuptools)
   py27-Jinja2-2.8 (direct dependency changed: py27-Babel)
   py27-Babel-2.3.4 (direct dependency changed: py27-setuptools)
   openvpn23-2.3.14_1 (options changed)
   dnsmasq-2.76,1 (options changed)

Number of packages to be removed: 3
Number of packages to be installed: 1
Number of packages to be upgraded: 25
Number of packages to be reinstalled: 9

The operation will free 20 MiB.
pkg-static: Cannot delete vital package: opnsense!
pkg-static: If you are sure you want to remove opnsense,
pkg-static: unset the 'vital' flag with: pkg set -v 0 opnsense
Starting web GUI...done.
Generating RRD graphs...done.
***DONE***

[phoenix]

Don't do it, the upgrade will wipe out your system. :) Have you installed a 'non-standard' test kernel on this server?

[sashxp]

NO!

But i startet with the 17.1 Beta and changed the channel to the stable channel...

[phoenix]

I'm not really experienced enough to tell you what to do in these circumstances so I'll have to leave it to someone else to give you the correct answer. I have a recollection that there was a post on the forums earlier that covered a failed update, unfortunately I'm a bit busy at the moment but I'd suggest you have in the forums for a similar problem.

[franco]

FreeBSD changed something with python setup tools handling, it's weird.

In another thread we solved it like this:

# opnsense-bootstrap

Your configuration will be kept, but it will reinstall all packages and the kernel and base system.


Cheers,
Franco

[stormy]

Seeing the same thing, the upgrade via GUI does not auto-reboot the box, it says it will, confirm, but output as in initial post. It sounds like opnsense python package cannot update itself :)

Running opnsense-bootstrap,  that sounds like it does a wipe-clean install, so i may lose other small things I've added (like lsof or what not)?

this is fresh 17.1 and updated via gui over last few weeks.. always it auto-rebooted, but now, it does not auto-reboot... any further link/doc/readme about this? 

I guess I'll wait with update till next week when this issue is more understood.

[franco]

I think this is due to having built something on the box that is not compatible anymore with a full prebuilt environment. In FreeBSD, it's either ports or packages, never both, at least as long as there aren't any problems. ;)

Yes, opnsense-bootstrap will delete all unneeded packages. That's needed to restore a clean environment. One that can indeed upgrade again...

Otherwise this may restore the upgrade capabilities. Make sure it doesn't want to deinstall "opnsense" package.

# pkg delete -f py27-setuptools27

Maybe this helps... I will look into this next week, "py27-setuptools27" looks a bit weird. Maybe this will unbreak in 17.1.5 again. It happened once or twice over the years.


Cheers,
Franco

[sashxp]

thank you, i've just updatet with the bootstrap variant - without a problem!

[stormy]

Too scared to do wipe/install.. curious to know WHAT is conflicting, if there's a logfile, or something, really prefer not brute-force in such cases.

Maybe in attempts to get wifi working w/Broadcom card :)   Regarding the py27, this was there before did anything:

Code Select Expand

root@OPNsense:~ # pkg list | grep py27-setuptools27
/usr/local/share/licenses/py27-setuptools27-32.1.0/LICENSE
/usr/local/share/licenses/py27-setuptools27-32.1.0/PSFL
/usr/local/share/licenses/py27-setuptools27-32.1.0/catalog.mk

removed it:

Code Select Expand

Proceed with deinstalling packages? [y/N]: y
[1/1] Deinstalling py27-setuptools27-32.1.0...
[1/1] Deleting files for py27-setuptools27-32.1.0: 100%

and, sure enough, updated went through, and rebooted nicely!!

Now running 17.1.4, curious if this will help my other issue: https://forum.opnsense.org/index.php?topic=4813.0, since saw IPSEC changes, maybe that is somehow related.

Thanks Franco!!

[eugenmayer]

Just in case, i had quiet some trouble finding this issue, so i add some google related stuff for other people to find this:

thats the error you get when you run

Code Select Expand


pkg upgrade


Code Select Expand


pkg: Cannot delete vital package: opnsense!
pkg: If you are sure you want to remove opnsense,
pkg: unset the 'vital' flag with: pkg set -v 0 opnsense


If you trigger this upgrade in the UI, you get the same error in the logs.

For me, fixing this upgrade was only possible by

Code Select Expand


pkg delete -f py27-setuptools27


and then run this again

Code Select Expand


pkg upgrade


In case that is interesting, i was upgrading form 17.1.2 to 17.1.6.

I ended up on 17.1.3 after that, running the next upgrade, i guess those are sequencial - then i had 17.1.6.

So i had to update 2 times. That instance was offline for a while, that why it was way outdated
This post is basically the same as stormy/franco were suggesting, just as a sequence. Nothing really new

*UPDATE
This was an issue on all my 5 opnsense boxen. What they have in common:
- installed tinc
- installed activated haproxy + letsencrypt

Since this seem to happen regulary and is not just some borken box, maybe this should be investigated

*UPDATE2:
Tried my 7th box, the one at home which had everything except tinc - and it worked. So it must be tinc related