SG-1100 Enter full pathname of shell or RETURN for /bin/sh:
-
@LostInIgnorance said in SG-1100 Enter full pathname of shell or RETURN for /bin/sh::
[6/88] Extracting python311-3.11.4: ..pid 530 (pkg-static), jid 0, uid 0, was killed: failed to reclaim memory
Child process pid=530 terminated abnormally: KilledHmm, that's not good.
Ok first check the available space on the drive. If it's close to full try removing any old ZFS snapshots and try again.
Steve
-
@stephenw10 Nope, plenty of space and was able to replicate the issue twice now with the exact same results
-
Does it fail at the same step each time?
-
@stephenw10 Yep, this is from the 27th snapshot log
The process will require 388 MiB more space. [1/88] Upgrading libxml2 from 2.10.3_1 to 2.10.4... [1/88] Extracting libxml2-2.10.4: .......... done [2/88] Upgrading php82 from 8.2.4 to 8.2.11... [2/88] Extracting php82-8.2.11: .......... done [3/88] Upgrading gettext-runtime from 0.21.1 to 0.22_1... [3/88] Extracting gettext-runtime-0.22_1: .......... done [4/88] Upgrading php82-zlib from 8.2.4 to 8.2.11... [4/88] Extracting php82-zlib-8.2.11: ........ done [5/88] Upgrading python39 from 3.9.16_2 to 3.9.17... [5/88] Extracting python39-3.9.17: .......... done [6/88] Upgrading python311 from 3.11.2_2 to 3.11.4... [6/88] Extracting python311-3.11.4: ..pid 530 (pkg-static), jid 0, uid 0, was killed: failed to reclaim memory Child process pid=530 terminated abnormally: Killed -
Hmm, I can't replicate that:
The process will require 398 MiB more space. [1/88] Upgrading libxml2 from 2.10.3_1 to 2.10.4... [1/88] Extracting libxml2-2.10.4: .......... done [2/88] Upgrading php82 from 8.2.4 to 8.2.11... [2/88] Extracting php82-8.2.11: .......... done [3/88] Upgrading gettext-runtime from 0.21.1 to 0.22_1... [3/88] Extracting gettext-runtime-0.22_1: .......... done [4/88] Upgrading php82-zlib from 8.2.4 to 8.2.11... [4/88] Extracting php82-zlib-8.2.11: ........ done [5/88] Upgrading python39 from 3.9.16_2 to 3.9.17... [5/88] Extracting python39-3.9.17: .......... done [6/88] Upgrading python311 from 3.11.2_2 to 3.11.4... [6/88] Extracting python311-3.11.4: .......... done [7/88] Upgrading php82-xml from 8.2.4 to 8.2.11... [7/88] Extracting php82-xml-8.2.11: ......... doneWhat packages do you have installed?
-
@stephenw10 Just FTP proxy and nmap
-
I'm still unable to replicate it.
Are you able to try reinstalling and upgrading from a clean 23.05.1 install? -
@stephenw10 I can try this later today and let you know of the outcome, though I was on 23.05.1 before the upgrade.
-
@stephenw10 I reloaded the SG-1100 with the latest factory image and proceeded to do the upgrade with no error this time.
-
Hmm, OK. Odd. I haven't seen any other reports of that. Let us know if you see it again.
Steve
-
The first SG-1100 seemed to upgrade just fine.
On the second SG-1100, I ran an upgrade from 23.01 to 23.05.1 that seemed uneventful. Then I tried to upgrade to 23.09, and ended up with this:
Starting CRON... done.
Starting package AWS VPC Wizard...done.
Starting package IPsec Profile Wizard...done.
.: cannot open /etc/rc.be_functions.sh: No such file or directory
Enter full pathname of shell or RETURN for /bin/sh:As far as I can tell, this SG-1100 was re-imaged with pfSense-plus-compat-recovery-23.01-RELEASE-aarch64.img.gz after a failed attempted upgrade to 23.01 and hasn't been touched since. (At this point, I basically used the SG-1100's to test the water before updating the production SG-3100.)
FYI.
Regards,
Ken
-
Do you have an upgrade log from that?
Is it running an packages? We have seen some upgrades fail due to ram exhaustion that present as you see after rebooting.
Steve
