Don't upgrade the sg-3100
-
That would definitely be helpful to have, thanks!
-
Here's the log from the entire upgrade.
-
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 recordHmm, there is aws-sdk again, just like the linked ticket. Strange.
-
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.
-
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.
-
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.
-
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.
-
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.
-
If you have the installer handy, load it with 2.4.4-p2 and then upgrade straight from there.
-
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.
-
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. -
@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.
-
@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.
