[Solved] OPNsense 27 upgrade – warnings and ZFS feature notice

[(MARLOO)]

Hello,

After upgrading to OPNsense 27, I initially saw repeated warnings in Firewall > System > Firmware > Reporter, including PHP startup messages about mongodb.so and some other log entries.

However, after letting the system settle and checking again, the firewall is now no longer showing those errors. WAN connectivity, PPPoE, DNS, and the rest of the system are working normally.

At this point, it looks like the issue may have been related to Zenarmor rather than the firewall core itself. Zenarmor is installed on this system and uses a local reporting backend, so it is possible that the reporting database or backend state needed to be updated or reinitialized after the upgrade.

Since the errors have disappeared, I'm not sure whether this was just a transient post-upgrade state, or whether Zenarmor automatically corrected the backend/database on its own.

I also noticed a ZFS pool warning after the firmware upgrade indicating that some supported pool features are not enabled yet. The pool is still online and healthy, and SMART for the SSD is passing, so this appears to be only an informational warning rather than an actual storage problem.

If anyone has seen a similar situation after upgrading to OPNsense 27, I'd be interested in hearing whether this is expected behavior or whether there is something that should still be checked manually.

The Services widget on the dashboard appears greyed out, but all listed services are running normally.

Thanks in advance.

[nero355]

After upgrading to OPNsense 27, I initially saw repeated warnings in Firewall > System > Firmware > Reporter, including PHP startup messages about mongodb.so and some other log entries.

At this point, it looks like the issue may have been related to Zenarmor rather than the firewall core itself. Zenarmor is installed on this system and uses a local reporting backend, so it is possible that the reporting database or backend state needed to be updated or reinitialized after the upgrade.

This is mentioned in another topic : It's something that got left behind after ZenArmor dumped MongoDB _{(As eveyone should IMHO !!!)} and moved to SQLite and Elasti<something> version 8 instead of version 5 so you need to do some cleaning up now...
_{(I dont use ZenArmor so don't know every detail...)}

I also noticed a ZFS pool warning after the firmware upgrade indicating that some supported pool features are not enabled yet.
The pool is still online and healthy

I am betting on OpenZFS getting upgraded and now telling you there is newer stuff to use.

Feel free to post the output here together with :

SMART for the SSD is passing

To double check everything :)

so this appears to be only an informational warning rather than an actual storage problem.

I think so too.

[(MARLOO)]

Hello nero355,

Thanks for the reply.

The mongodb.so warnings fit exactly with Zenarmor dropping MongoDB in favor of SQLite / newer Elasticsearch. I'll clean up the leftover php83-pecl-mongodb package and run pkg autoremove, then check if the warnings disappear permanently.

About the ZFS warning: I agree it's likely just OpenZFS being updated and reporting newer available features on my existing pool. The pool is online and healthy, and SMART on the SSD is clean, so I'm treating it as informational.

The greyed‑out Services widget seems to be a UI glitch; all services are actually running fine.

If you've seen this combo on other 27 upgrades, any specific cleanup steps beyond removing the mongodb package?

Thanks,

[nero355]

If you've seen this combo on other 27 upgrades, any specific cleanup steps beyond removing the mongodb package?

Just the MongoDB stuff here : https://forum.opnsense.org/index.php?topic=52393.msg270385#msg270385

The OpenZFS stuff is a well known story for both Linux and *BSD so not really OPNsense specific IMHO.

And since Storage has always been one of my favorite topics I don't mind double checking S.M.A.R.T. data for other people as much as I can :)

[cookiemonster]

@(MARLOO)if you do

Code Select Expand

#zpool status you should get a message like:

Code Select Expand

  pool: zroot
 state: ONLINE
status: Some supported and requested features are not enabled on the pool.
        The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(7) for details.If so, then it would match what dmesg spits out. It's meant to say that as a ZFS pool there are features available but not used until a zpool upgrade is made. Just as the messages say, they are but are up to de administrator to upgrade the pool if they want to use them.
Please please do NOT blindly do a zpool upgrade unless you know what you are doing and NEED those features. Just like the message says.
It can require the booloader to be upgraded as well or you have a non-bootable machine.
See the zpool-features(7) for those details.
To read them: $man zpool-features.

[(MARLOO)]

Thanks for the confirmation.

zpool status shows exactly that message:

pool: zroot
state: ONLINE
status: Some supported and requested features are not enabled on the pool.
errors: No known data errors


I have no need for the new features, so I will leave the pool as-is and not run zpool upgrade

[cookiemonster]

All good