SG1100 to 24.11 issues

SteveITS

FWIW, ran into this with a client's 1100 tonight. Got the "137" error and it also logged, "pid 56451 (pkg-static), jid 0, uid 0, was killed: failed to reclaim memory" to get it into this thread.

The first time the update page showed the 137 error, the second time it didn't "stop" updating, just hung.

System Activity showed this before restart:

Mem: 11M Active, 37M Inact, 231M Wired, 520M Free
ARC: 57M Total, 25M MFU, 29M MRU, 181K Anon, 357K Header, 2701K Other
37M Compressed, 96M Uncompressed, 2.60:1 Ratio

after restart, when the upgrade succeeded (from the command line):

Mem: 125M Active, 73M Inact, 262M Wired, 472M Free
ARC: 82M Total, 25M MFU, 55M MRU, 114K Anon, 554K Header, 2330K Other
61M Compressed, 145M Uncompressed, 2.36:1 Ratio

Another 1100 with a similar config updated fine from the web GUI.

stephenw10

Going forward this should be less of an issue. We reduced the memory requirement for pkg by using a different compression.

elamigosam2

For anyone who finds this thread:
I was having the same issue, nothing installed except 2 packages (zabbix agent and zabbix proxy) I disabled the bsnmpd, dpinger, zabbix agent and zabbix proxy services and it was able to finish the upgrade to 24.11 successfully.
I am thinking that the SG1100 was running out of memory when doing the update (not an expert just a user), is there a way to check if there are memory issues on the device?
I removed this router from production because it was causing issues, it would crash and stop responding. Maybe there is a memory test i can run to check for memory problems? or maybe its just too old to handle the new pfsense versions.

Thank you

marcosm

Indeed the memory can be an issue especially with larger upgrades. The memory usage during ZFS upgrades has been improved in 25.07 (to be released soon) to address the issue. You can check the system log for signs of processes being killed abruptly. If however you're still using UFS it's more likely to have been some other issue.