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

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.

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

garyd9

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

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

@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

@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

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

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

garyd9

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

Thank you

doktornotor

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

Praise the lord!
Alelujah!

doktornotor

@maverick_slo:

Praise the lord!
Alelujah!

Pippin

aroy mak mak ;D