Setup: OPNsense [version], Zenarmor 2.7.2, local Elasticsearch reporting database.
What happened:
After upgrading Zenarmor from 2.7.1 to 2.7.2, restarting the packet engine caused OPNsense to kernel panic and reboot. After the reboot, every Zenarmor page in the OPNsense GUI showed only a grey page with a loading spinner.
What was fine:
pkg info showed os-sensei 2.7.2 installed, and pkg check -s os-sensei passed.
The eastpect engine and Elasticsearch were both running, and the cluster health was green.
The configd Zenarmor jobs were all returning OK.
Actual cause:
The browser console showed the Zenarmor entry JS and CSS files being blocked with a MIME type mismatch (text/html). The page was requesting index-CLn7932s.js and index-QZ9Oy0WF.css, but those files no longer exist. The 2.7.2 assets on disk are index-C_wF72l1.js and index-BdAypUN-.css, so the server was returning HTML instead.
The loader reads the entry filenames from two small pointer files:
/usr/local/opnsense/www/zenarmor/assets/js-file
/usr/local/opnsense/www/zenarmor/assets/css-file
Both still had their 2.7.1 dates and contents. They aren't owned by the package (pkg which returns "not found in the database"), which is why pkg check didn't catch them. It looks like the post-install step that rewrites them didn't complete, probably because the panic interrupted it.
Fix:
pkg install -f os-sensei
This regenerated both pointer files with the correct names, and the UI loaded normally afterwards.
Notes for anyone else:
If you see the spinner, open the browser devtools (F12) and check the Console for blocked index-*.js/.css files. Then compare the contents of js-file and css-file with the actual index-* files in that assets directory.
The panic on engine restart looks similar to the netmap generic adapter teardown race reported with earlier Zenarmor versions on 26.7. I'd avoid "Restart packet engine" until that's confirmed fixed.
Zenarmor's automatic bug report failed with a 500 from their server, so I've raised it separately.