Issues after OPNsense upgrade to 26.1.3
Hello,
I get below errors after installing new version of OPNSense.
Any ideas?
Some errors were detected during data retiring for Elasticsearch
Thanks
-
Official comment
Hi Kunalwaghela,
Thanks for reaching out and bringing the issue to our attention.
Could you please provide the logs and configuration by following the steps outlined in the link below? I kindly request that you select all checkboxes.
https://www.zenarmor.com/docs/support/reporting-bug
Best regards,Comment actions -
Might also facing as similar issue, the eastpect binary appears crashing and constantly causing a coredump
Using Elastic 8.18Update, I checked my Elasticsearch instance and it was not "green", freed up space (there was a Elasticsearch notice was a watermark storage limit reached issue in the Elastic logs), seems to be working again.
-
Hi Jonny,
Thanks for reaching out and bringing the issue to our attention.
Could you please provide the logs and configuration by following the steps outlined in the link below? I kindly request that you select all checkboxes.
https://www.zenarmor.com/docs/support/reporting-bug
Best regards, -
Extra notes, after doing a reporting db health check and index check, I then changed the deployment mode to Routed L3 with native netmap driver, I'm using VLANs, and I noticed it say 'emulated' as it created the netmap elements on the engine restart.
The traffic graph is working better than ever (down and up now, instead of just upload - the second graph), and it appears to be running w/out coredump-ing now.
This does mean that it would seem passive mode does not work anymore, and I do not have blocking enabled otherwise in Zenarmor, but I am interested in the reporting. Ideally even though blocking would be enabled, no blocks will happen on account of Zenarmor.
Please sign in to leave a comment.
Comments
5 comments