1100 upgrade, 22.05->23.01, high mem usage

[beerguzzle]

Checking my system this morning after applying patch ff715efce5e6c65b3d49dc2da7e1bdc437ecbf12 and rebooting yesterday... Bliss! Nothing happened at 3 AM and my wired mem usage remains at about 35%. I consider this problem solved.

[rpsmith]

Patch "ff715efce5e6c65b3d49dc2da7e1bdc437ecbf12" has completely resolved my SG-1100 memory problems!

[FSC830]

@rpsmith said in 1100 upgrade, 22.05->23.01, high mem usage:

Patch "ff715efce5e6c65b3d49dc2da7e1bdc437ecbf12" has completely resolved my SG-1100 memory problems!

+1

Applied patch and rebootet yesterday at 8:00pm

Regards

[mcury]

@fsc830 Applied this patch in my SG-3100, everything OK, memory usage didn't change at night.
Thanks

[JMV43 0]

@machasachaira How do we apply the patch?

JMV

[SteveITS]

@jmv43-0 Install the System Patches package and use the patch ID.
https://docs.netgate.com/pfsense/en/latest/development/system-patches.html

[MachasaChaira]

@steveits I didn't know that way, I used the fetch command on the CLI to bring the file and replace the original.

Thanks.

[SteveITS]

@machasachaira :) System Patches is relatively new (1-2 years), and a wonderful idea. Netgate publishes a list of Recommended patches for the version you're on. Updating that package updates the list of patches. Any patch with a commit ID can also be pulled in.

[JMV43 0]

@steveits Thanks

[mr.castoro]

Applied this patch 2 days ago. Absolutely solved the 3am memory leak. However, dns broke on my sg 1100 the past two days. I had to restart the dns resolver service to restore dns. Anyone else experiencing this?

[SteveITS]

@mr-castoro There are a bunch of DNS threads lately.
If you have Resolver set to forward, ensure DNSSEC is unchecked.

[MachasaChaira]

@mr-castoro Have you restarted your SG after the patch update? I have not experienced any problems after rebooting.

[mr.castoro]

@machasachaira yes, several times

[rpsmith]

@mr-castoro -- No problems with my SG-1100 and DNS but I use the "Forwarder" and not the "Resolver" and I point the Forwarder to my two Pi-hole IPs. Works great that way!

Also, instead of pointing it to a Pi-hole, you could just use: 9.9.9.9, 1.1.1.1 or 8.8.8.8 or some other external DNS.