[solved] failing to upgrade to 2.3.3.r.20170213.1559 (and r.20170214.1441)

garyd9 · Feb 15, 2017, 6:16 PM

When trying to upgrade from 2.3.3.r.20170213.0512 to 2.3.3.r.20170213.1559, it's not working. (Wow, that's an incredibly useless report… perhaps a bit more info would be useful...)

Tried with both the web UI and via option 13 in shell. In both cases, things appear to be working, but after the reboot the pfsense installation is still at 2.3.3.r.20170213.0512.

My pfsense box is headless (accessed via IPMI) and the upgrade process after the reboot scrolls very quickly, but I don't see any obvious error.

If someone can point me to a log file (full path) that contains any information in regards to the upgrade, I'd be happy to find/extract more information and post here.

Take care
Gary

grandrivers · Feb 14, 2017, 4:35 AM

heres what i get hint: look in status.php

Updating repositories metadata…
Updating pfSense-core repository catalogue...
Repository pfSense-core has a wrong packagesite, need to re-create database
Fetching meta.txz: . done
Fetching packagesite.txz: . done
Processing entries: . done
pfSense-core repository update completed. 8 packages processed.
Updating pfSense repository catalogue...
Repository pfSense has a wrong packagesite, need to re-create database
Fetching meta.txz: . done
Fetching packagesite.txz: .......... done
Processing entries: .......... done
pfSense repository update completed. 438 packages processed.
Unlocking package pfSense-kernel-pfSense... done.
The following 5 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
openvpn23: 2.3.14 [pfSense]
easy-rsa: 3.0.1_1 [pfSense]

Installed packages to be UPGRADED:
pfSense-default-config: 2.3.3.a.20170210.0735 -> 2.3.3.r.20170213.1559 [pfSense-core]
pfSense-base: 2.3.3.a.20170210.0735 -> 2.3.3.r.20170213.1559 [pfSense-core]
pfSense: 2.3.3.a.20170209.0720 -> 2.3.3.r.20170213.1530 [pfSense]

Number of packages to be installed: 2
Number of packages to be upgraded: 3

25 MiB to be downloaded.

**** WARNING ****
Reboot will be required!!
Proceed with upgrade? (y/N) >>> Downloading upgrade packages…
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (7 candidates): ....... done
Processing candidates (7 candidates): .... done
The following 5 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
openvpn23: 2.3.14 [pfSense]
easy-rsa: 3.0.1_1 [pfSense]

Installed packages to be UPGRADED:
pfSense-default-config: 2.3.3.a.20170210.0735 -> 2.3.3.r.20170213.1559 [pfSense-core]
pfSense-base: 2.3.3.a.20170210.0735 -> 2.3.3.r.20170213.1559 [pfSense-core]
pfSense: 2.3.3.a.20170209.0720 -> 2.3.3.r.20170213.1530 [pfSense]

Number of packages to be installed: 2
Number of packages to be upgraded: 3

25 MiB to be downloaded.
Fetching pfSense-default-config-2.3.3.r.20170213.1559.txz: . done
Fetching pfSense-base-2.3.3.r.20170213.1559.txz: …....... done
Fetching pfSense-2.3.3.r.20170213.1530.txz: . done
Fetching openvpn23-2.3.14.txz: .......... done
Fetching easy-rsa-3.0.1_1.txz: ... done
Checking integrity... done (1 conflicting)
- openvpn23-2.3.14 [pfSense] conflicts with openvpn-2.4.0 [installed] on /usr/local/include/openvpn-plugin.h
Checking integrity… done (0 conflicting)
Conflicts with the existing packages have been found.
One more solver iteration is needed to resolve them.
The following 6 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
openvpn-2.4.0

New packages to be INSTALLED:
easy-rsa: 3.0.1_1 [pfSense]
openvpn23: 2.3.14 [pfSense]

Installed packages to be UPGRADED:
pfSense-default-config: 2.3.3.a.20170210.0735 -> 2.3.3.r.20170213.1559 [pfSense-core]
pfSense-base: 2.3.3.a.20170210.0735 -> 2.3.3.r.20170213.1559 [pfSense-core]
pfSense: 2.3.3.a.20170209.0720 -> 2.3.3.r.20170213.1530 [pfSense]

Number of packages to be removed: 1
Number of packages to be installed: 2
Number of packages to be upgraded: 3
Upgrade is complete. Rebooting in 10 seconds.

Locking package pfSense-kernel-pfSense… done.
Locking package pfSense-pkg-arping... done.
Locking package pfSense-pkg-nmap... done.
Locking package pfSense-pkg-ntopng... done.
Locking package pfSense-pkg-nut... done.
Locking package pfSense-pkg-openvpn-client-export... done.
Locking package pfSense-pkg-pfBlockerNG... done.
Locking package pfSense-pkg-snort... done.
Upgrading necessary packages...
Checking for upgrades (7 candidates): ....

pfSense-kernel-pfSense-2.3.4.a.20170213.1557 is locked and may not be modified
Checking for upgrades (7 candidates)..... done
Processing candidates (7 candidates): ...

pfSense-pkg-pfBlockerNG-2.1.1_6 is locked and may not be modified

pfSense-pkg-snort-3.2.9.2_16 is locked and may not be modified

pfSense-pkg-nut-2.7.4_4 is locked and may not be modified

pfSense-pkg-ntopng-0.8.6 is locked and may not be modified

pfSense-pkg-pfBlockerNG-2.1.1_6 is locked and may not be modified

pfSense-pkg-ntopng-0.8.6 is locked and may not be modified

pfSense-pkg-pfBlockerNG-2.1.1_6 is locked and may not be modified

pfSense-pkg-ntopng-0.8.6 is locked and may not be modified

pfSense-pkg-nmap-1.4.4_1 is locked and may not be modified
Processing candidates (7 candidates)... done
Checking integrity... done (1 conflicting)
- openvpn23-2.3.14 [pfSense] conflicts with openvpn-2.4.0 [installed] on /usr/local/include/openvpn-plugin.h
Checking integrity… done (0 conflicting)
The following 7 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
openvpn-2.4.0

New packages to be INSTALLED:
openvpn23: 2.3.14 [pfSense]
easy-rsa: 3.0.1_1 [pfSense]

Installed packages to be UPGRADED:
pfSense-default-config: 2.3.3.a.20170210.0735 -> 2.3.3.r.20170213.1559 [pfSense-core]
pfSense-base: 2.3.3.a.20170210.0735 -> 2.3.3.r.20170213.1559 [pfSense-core]
pfSense: 2.3.3.a.20170209.0720 -> 2.3.3.r.20170213.1530 [pfSense]

Installed packages to be REINSTALLED:
pkg-1.9.4_1 [pfSense]

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

2 MiB to be downloaded.
pkg: https://beta.pfsense.org/packages/pfSense_v2_3_3_amd64-pfSense_v2_3_3/All/pkg-1.9.4_1.txz: No address record

Unlocking package pfSense-pkg-arping… done.
Unlocking package pfSense-pkg-nmap... done.
Unlocking package pfSense-pkg-ntopng... done.
Unlocking package pfSense-pkg-nut... done.
Unlocking package pfSense-pkg-openvpn-client-export... done.
Unlocking package pfSense-pkg-pfBlockerNG... done.
Unlocking package pfSense-pkg-snort... done.

jimp · Feb 14, 2017, 2:02 PM

It should be working around that on its own. You can try forcing it with something like

pkg delete -f openvpn*

And then re-run the upgrade.

On the system I've got that has been tracking 2.3.3, it had no problems upgrading.

garyd9 · Feb 14, 2017, 2:12 PM

Is it failing because of openvpn (which it seems to understand that it needs to remove first), or because of this line:


pkg: https://beta.pfsense.org/packages/pfSense_v2_3_3_amd64-pfSense_v2_3_3/All/pkg-1.9.4_1.txz: No address record

jimp · Feb 14, 2017, 2:18 PM

It's possible, though that would suggest you didn't have any external connectivity at the time, because the that hostname does have an address.

garyd9 · Feb 14, 2017, 2:39 PM

@jimp:

It's possible, though that would suggest you didn't have any external connectivity at the time, because the that hostname does have an address.

Would something in the pfsense startup cause it to have connectivity (as it does fetch other packages previous to this one) and then lose that connectivity before trying to retrieve the "pkg" package?

Is there a way to pre-fetch the package?

garyd9 · Feb 14, 2017, 5:40 PM

@jimp:

It should be working around that on its own. You can try forcing it with something like

pkg delete -f openvpn*

And then re-run the upgrade.

Has anyone who has experienced the upgrade error been able to resolve it by running the above command and then re-running the upgrade? I'm remote to the router right now, so I can't recover if I try that and it causes something that prevents the router from coming back up and routing packets. (I'm forced to use ipsec to access the router until tomorrow night… )

garyd9 · Feb 15, 2017, 3:29 AM

Still having the same issue with going from 2.3.3.r.20170213.0512 to 2.3.3.r.20170214.1441. I have about 30 minutes physically with the pfsense box, so was going to try the suggestion of nuking the openvpn package, but I wanted to have a way to reinstall things if that screws up pfsense. However, I can't find the rc builds on the normal website location (https://snapshots.pfsense.org/amd64/pfSense_RELENG_2_3/installer/?C=M;O=D)

So, with no confirmation that manually deleting that package won't screw things up, and no way to get back to a build >= to what my current config.xml has, I guess I'm stuck. :(

By the way, before my most recent (failed) attempt, I changed "System"->"General Setup"->"DNS Servers" to 8.8.8.8, and ensured that "Disable DNS Forwarder" was checked. After doing that, I verified that /etc/resolve.conf only had a single nameserver: 8.8.8.8. Still getting the same "no address found" error when pkg tries to get …itself.

grandrivers · Feb 15, 2017, 4:45 PM

i just deleted then upgraded went ok needed to go in and resave openvpn setting though

garyd9 · Feb 15, 2017, 6:16 PM

confirmed… it appears that deleting openvpn removed the necessity of reinstalling "pkg", so that message went away as well. :)

Thank you

doktornotor · Feb 18, 2017, 2:12 PM

Even deleting openvpn packages fixes nothing here. https://redmine.pfsense.org/issues/7276

EDIT: Miracle, after another two attempts and reboots following the openvpn forced uninstall, it (probably) upgraded!!!

$ cat /etc/version*
2.3.3-RC
Wed Feb 15 00:27:19 CST 2017
7b85c9aea79bb210daba645b31fffeae7aa91970
0

This pkg is next generation masterpiece, I tell ya!!! I think any other machines will be upgraded by reinstalling and restoring config.xml, that will be a whole LOT faster and more reliable.

:( >:( >:(

maverick_slo · Feb 18, 2017, 4:21 PM

Praise the lord!
Alelujah!

doktornotor · Feb 18, 2017, 6:27 PM

@maverick_slo:

Praise the lord!
Alelujah!

Pippin · Feb 18, 2017, 8:40 PM

aroy mak mak ;D