Squid: segmentation fault

[schnipp]

I plan to upgrade Opnsense from version 24.7.12_2 to 25.1.1. In the earlier version, there are issues with the squid web proxy causing segmentation faults (link). But manually starting the web proxy after booting the firewall works (even if segmentation faults are logged).

Can anybody confirm that the squid web proxy works properly in Opnsense 25.1.1 (even if segmentation faults occur)?

[newsense]

No such reports either here or on Github about 25.1.x

You can play it safe, take a snapshot. If not on ZFS and on bare metal this is a perfect opportunity to do a fresh install importing the config on the fly. (Have a copy of the config file nevertheless)

[schnipp]

No such reports either here or on Github about 25.1.x

Thanks.

You can play it safe, take a snapshot. If not on ZFS and on bare metal this is a perfect opportunity to do a fresh install importing the config on the fly. (Have a copy of the config file nevertheless)

This is the point I've been thinking about for a while. The installation dates back to 2018 and therefore still uses UFS. Snapshots are the most important aspect for me in order to switch to ZFS soon. Before reinstalling, however, I need to list and save the manually created configuration files, otherwise they will be lost.

I'm not that familiar with ZFS. I suspect 8 GB RAM (non ECC) and 120 GB SSD shouldn't be a problem, or?

[Patrick M. Hausen]

I'm not that familiar with ZFS. I suspect 8 GB RAM (non ECC) and 120 GB SSD shouldn't be a problem, or?

Actually that's pretty good. I have run APU or Protectli devices with 4 G of memory with ZFS without problems. I even have a netbook with 2 G running FreeBSD with ZFS.

As long as the pool is small - and 120 G is ridiculously small by ZFS standards, memory size is not as critical as for a NAS or a hosting server.

[schnipp]

Thanks. Presumably, the upcoming system upgrade will be a clean install with ZFS. Hopefully, this will increase system availability in case there are any problems with future updates.