Don't upgrade the sg-3100

behemyth

OK, I'm not running any packages or anything either, which is weird. I'll copy the error logs for you.

stephenw10

Only issue I have seen is when I had a 3G modem internally. It failed to boot after upgrade but booted fine when I removed it.

You have any additional hardware in your 3100?

Steve

behemyth

Nope, basic sg-3100, and I even reset it to factory defaults before doing the upgrade.

Here's what I get right now after doing an upgrade. I have no idea why it would complain about certs after doing a factory reset:

Stack trace:
#0 /etc/inc/functions.inc(32): require_once()
#1 /etc/inc/notices.inc(24): require_once('/etc/inc/functi...')
#2 /etc/inc/config.gui.inc(37): require_once('/etc/inc/notice...')
#3 /etc/inc/auth.inc(31): require_once('/etc/inc/config...')
#4 /etc/inc/captiveportal.inc(27): require_once('/etc/inc/auth.i...')
#5 /etc/inc/service-utils.inc(23): require_once('/etc/inc/captiv...')
#6 /etc/inc/pkg-utils.inc(24): require_once('/etc/inc/servic...')
#7 /etc/rc.bootup(24): require_once('/etc/inc/pkg-ut...')
#8 {main}
thrown
Fatal error: Uncaught Error: Call to undefined function log_error() in /etc/inc/config.lib.inc:953
Stack trace:
#0 [internal function]: pfSense_clear_globals()
#1 {main}
thrown in /etc/inc/config.lib.inc on line 953
Starting CRON... done.

Fatal error: Uncaught Error: Call to undefined function gettext() in /etc/inc/certs.inc:46
Stack trace:
#0 /etc/inc/functions.inc(32): require_once()
#1 /etc/inc/notices.inc(24): require_once('/etc/inc/functi...')
#2 /etc/inc/config.inc(49): require_once('/etc/inc/notice...')
#3 /etc/rc.start_packages(22): require_once('/etc/inc/config...')
#4 {main}
thrown in /etc/inc/certs.inc on line 46
pfSense 2.5.0-DEVELOPMENT (Patch 2) arm Mon Apr 08 17:15:40 EDT 2019
Bootup complete

FreeBSD/arm (Amnesiac) (ttyu0)

jimp

It's not completely upgraded and missing several functions, which means it must have broken mid-upgrade, similar to what happens with https://redmine.pfsense.org/issues/9431

You can probably work around it like so:

# dhclient mvneta2
# pfSense-upgrade -d

That should let it continue on and finish what it wanted. If you can capture the output from that it may help. Though really what we'd need to see is the console output from the actual upgrade process that failed.

behemyth

I actually had my console program log the entire upgrade, I can upload the file when I get home later today if that’s helpful for you guys.

jimp

That would definitely be helpful to have, thanks!

behemyth

session.7z

Here's the log from the entire upgrade.

jimp

New packages to be INSTALLED:
        aws-sdk-php73: 3.63.1 [pfSense]
        php73-ftp: 7.3.3 [pfSense]
        php73-intl: 7.3.3_1 [pfSense]
        php73-mysqli: 7.3.3 [pfSense]
        php73-pdo_mysql: 7.3.3 [pfSense]
        php73-pecl-ssh2: 1.1.2 [pfSense]
        php73-pgsql: 7.3.3 [pfSense]
        python36: 3.6.8_1 [pfSense]
        py36-ply: 3.11 [pfSense]
        py36-setuptools: 40.8.0 [pfSense]
        pcre2: 10.32 [pfSense]
        icu: 64.1,1 [pfSense]
        libssh2: 1.8.0_1,3 [pfSense]
        postgresql95-client: 9.5.16 [pfSense]

The process will require 185 MiB more space.
13 MiB to be downloaded.
pkg-static: https://firmware.netgate.com/beta/packages/pfSense_factory-master_armv7-pfSense_factory-devel/All/aws-sdk-php73-3.63.1.txz: No address record

Hmm, there is aws-sdk again, just like the linked ticket. Strange.

behemyth

I noticed in the trouble ticket you asked the person what packages they had installed - this is after a factory reset, so there is nothing installed. Its a brand new install.

jimp

There must have been something left on there, a default install wouldn't have had libssh2, the postgres client, or several of the others in that "New packages to be installed" list. Maybe they were remnants from packages you had before the reset.

Though on the 3100 it would have had the AWS VPC wizard package which would have brought in that aws-sdk package as well.

behemyth

Is there anything you want me to do, or that I can do, or just wait for you guys to do more work on this issue. I guess really the issue is that aws package.

jimp

No, it's OK. Seeing that it was attempting to pull in the same package that others hit is good enough for now.

The 3100 does have another issue on 2.5.0, in that the switch isn't being detected, so that's a different reason not to run 2.5.0 on it yet. We have an internal issue setup to track that.

behemyth

Oh ok, yeah its just sitting on my desk, i dont use it daily. I was just seeing how 2.5 might run on it and ran into this. If you want me to re-test code on it just let me know.

jimp

If you have the installer handy, load it with 2.4.4-p2 and then upgrade straight from there.

behemyth

That's actually what I've been doing - I don't know how else to get 2.5.0. I load 2.4.4-p2 and then use the web-gui to upgrade.

gcu_greyarea

I’ve got a SG-2220 and tried out the AWS Wizard. I stopped using the AWS wizard and uninstalled it in Package Manager.
When I needed a bit more CPU/Memory i backed up my SG-2220 and imported the config into a VM running pfSense CE. The AWS wizard is not available on CE.
I then wanted to test 2.5 in the pfSense VM but the upgrade failed due to the “aws-sdk” error ...
Unfortunately i cannot provide any logs as I have rolled back the VM to a snapshot taken prior to the upgrade attempt.
I assume that the config file still refers to AWS wizard components.

jimp

@behemyth said in Don't upgrade the sg-3100:

That's actually what I've been doing - I don't know how else to get 2.5.0. I load 2.4.4-p2 and then use the web-gui to upgrade.

Did you restore your config before or after upgrading? If you restored before upgrading, try not doing that instead.

jimp

@gcu_greyarea said in Don't upgrade the sg-3100:

I’ve got a SG-2220 and tried out the AWS Wizard. I stopped using the AWS wizard and uninstalled it in Package Manager.
When I needed a bit more CPU/Memory i backed up my SG-2220 and imported the config into a VM running pfSense CE. The AWS wizard is not available on CE.
I then wanted to test 2.5 in the pfSense VM but the upgrade failed due to the “aws-sdk” error ...
Unfortunately i cannot provide any logs as I have rolled back the VM to a snapshot taken prior to the upgrade attempt.
I assume that the config file still refers to AWS wizard components.

That wouldn't be related. Since the wizard package isn't available on CE it can't be doing that. It's not clear yet what is, however. We've had some odd quirks with the pkg solver on 12 so far.