Messages

Yes, audit checked out fine - no issues, so all seems okay.  (I do have the "iperf" plugin installed.)  Thanks!

I received this error during the upgrade from 24.1.5_3 to 24.1.6 - is this something to worry about?

Code Select Expand

...
Configuring system logging...done.
[33/33] Upgrading ruby31-gems from 3.5.7 to 3.5.9...
[33/33] Extracting ruby31-gems-3.5.9: .......... done
pkg-static: Fail to rename /usr/local/bin/.pkgtemp.gem.OHLbdamd6pqs -> /usr/local/bin/gem:No such file or directory
Starting web GUI...done.
...

I ran another update and it seemed to try updating this package again (?)

Code Select Expand

...
OPNsense repository is up to date.
All repositories are up to date.
Checking for upgrades (1 candidates): . done
Processing candidates (1 candidates): . done
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
ruby31-gems: 3.5.7 -> 3.5.9

Number of packages to be upgraded: 1
[1/1] Upgrading ruby31-gems from 3.5.7 to 3.5.9...
[1/1] Extracting ruby31-gems-3.5.9: .......... done
ruby31-gems-3.5.7: missing file /usr/local/share/licenses/ruby31-gems-3.5.7/LICENSE
ruby31-gems-3.5.7: missing file /usr/local/share/licenses/ruby31-gems-3.5.7/MIT
ruby31-gems-3.5.7: missing file /usr/local/share/licenses/ruby31-gems-3.5.7/RUBY
ruby31-gems-3.5.7: missing file /usr/local/share/licenses/ruby31-gems-3.5.7/catalog.mk
Checking integrity... done (0 conflicting)
Nothing to do.

Historically, all previous updates I've done with OPNsense ran without errors or warnings.

Indeed, when I switched from pfSense to OPNsense I was surprised by the huge amount of disk writes that OPNsense makes.  My gateway was averaging ~3.5GB writes/day, which I found to be rather excessive.  I did a bit of digging and with a few small changes I reduced the daily writes significantly (it's averaging 50MB/day now with no loss in functionality or stability).

There are a number of contributors to writes, one of the largest of which is the RRD data for the Reporting + Health dashboard in the OPNsense control panel.  This is actually straightforward to address - you can simply add an entry in your fstab for "/var/db/rrd" as a tmpfs volume (I use a 64MB volume size for this, also a reboot will be necessary to enable this).  Then go  to System + Settings + Miscellaneous in the OPNsense control panel, then in the "Periodic Backups" section, and change the "Periodic RRD Backup" to "Power off" for maximum write savings (or pick a backup time period you would like).

Given that OPNsense supports this backup functionality, it'd be nice if they just supported this as the default when logging to RAM is enabled, but I haven't bothered to file a suggestion for this.

There are other more minor changes one can do, such as disabling continuous OpenBSD entropy generation (one line config change), and stopping OPNsense from continually rewriting /etc/hosts and /etc/resolv.conf when they haven't changed, moving the DHCP lease database to tmpfs and enabling periodic backups for that as well, and so on.

If it is helpful, you can find some good background regarding this subject here:  https://github.com/opnsense/core/issues/6596